Your assistant. Finney’s team behind the work.
Choose the supported assistant or workspace you already use. Connect an existing Finney account and organization, or discuss the setup your work needs.
Use Finney where you already work.
Connect your existing Finney account through a supported AI assistant, or work in your Finney workspace. Your selected Finney runtime performs the work. Connecting an assistant does not create an account, organization, or agent team.
Where you work
Claude web/Desktop, Claude Code, ChatGPT web, or the Finney workspace. Client eligibility, administrator settings, and limits apply.
- Claude web/Desktop
- Claude Code
- ChatGPT web
Where Finney runs
Desktop, a dedicated computer, Finney Cloud, or customer infrastructure. Confirm connection reachability and authentication for your selected deployment with its operator.
Before you connect
You need an existing Finney account, access to the intended organization and agents, and a reachable Finney environment. Your operator must confirm how your selected deployment connects. This address does not provision an organization or connect every local host automatically.
Finney’s remote MCP endpoint uses Streamable HTTP with Finney-account OAuth. Clients that can set headers may use an organization API key instead; agree its scoped, revocable access with your administrator and never paste a key into a conversation. Work runs on Finney agents using the signed-in person’s permissions for the account-authenticated route.
Finney remote MCP endpoint
https://app.finney.finance/mcpClaude web and Claude Desktop
Custom remote connectors are available on Free, Pro, Max, Team, and Enterprise. Free allows one custom connector. For Team and Enterprise, an administrator adds the connector before each person connects.
- Open Claude’s connectors area and add a custom connector, or ask your administrator to add it.
- Name it Finney and enter the MCP endpoint above. Review the authentication settings and sign in to your Finney account.
- Check the organization and permitted tools. Start with a scoped task and review the output before authorizing further work.
Remote connections originate from Anthropic infrastructure, including when using Claude Desktop.
Official Claude connector instructionsClaude Code
With Claude Code installed and available to your account, add the remote HTTP server from your terminal:
claude mcp add --transport http finney https://app.finney.finance/mcpThen run /mcp in Claude Code and follow the browser sign-in flow for Finney. Confirm the selected organization and tools before using them. This is separate from Claude web/Desktop connector setup.
ChatGPT web
Use the developer/app route on eligible Plus, Pro, Business, Enterprise, and Education accounts. Availability depends on account eligibility and workspace administrator settings.
- Follow OpenAI’s current developer-mode instructions to enable the feature where permitted.
- Create a remote MCP app using the endpoint above and OAuth. Sign in to the intended Finney account and review access.
- Select the app in a conversation, inspect the available tools, and test only a scoped task you are authorized to perform.
Review before enabling write access. Full read/write MCP access carries elevated risk, including unintended actions and data exposure. Confirm tool permissions and approval controls with your administrator.
Official ChatGPT developer-mode instructionsFinney workspace
Use your existing Finney environment directly. Open the workspace address provided by your organization’s operator, or open your configured Finney Desktop app. Sign in as required and confirm your organization and access.
There is no new workspace created by this page. If you do not have an environment, discuss setup, or explore the separate Desktop download and trial-key steps.
OpenAI and ChatGPT names and marks belong to OpenAI. Claude names and marks belong to Anthropic. These labels identify client options and do not imply endorsement or partnership.
Other compatible MCP clients
Confirm support for remote Streamable HTTP MCP and the required Finney authentication before relying on another client. Client limits and administrator policies apply.
Ask about compatible MCP clientsAgree access, review, and hosting
Your professionals retain judgment and approval. Configure and verify executor identity, tool permissions, sending controls, and review requirements. Hosting describes where the app and stored working data run; model requests, connected tools, licensing, and remote assistants may involve external services. A third-party subscription does not include universal Finney model access or hosting.
The endpoint is implemented in Finney. Client instructions describe documented compatibility, not proof that every client and deployment has passed production end-to-end testing.