Skip to main content
Finta MCP uses OAuth for authentication. On first use, your client opens a Finta sign-in window — approve access and the connection is remembered. Server URL (all clients):
https://mcp.finta.io/mcp

Cursor

Add Finta to ~/.cursor/mcp.json:
{
  "mcpServers": {
    "finta": {
      "url": "https://mcp.finta.io/mcp"
    }
  }
}
Restart Cursor or reload MCP servers. Cursor prompts for OAuth the first time you use Finta — sign in to Finta and approve access. Some Cursor versions also accept an HTTP transport with an explicit type:
{
  "mcpServers": {
    "finta": {
      "type": "http",
      "url": "https://mcp.finta.io/mcp"
    }
  }
}

Claude Desktop

In Claude Desktop, open Settings → Connectors → Add custom connector and add a remote (HTTP) server with this URL:
https://mcp.finta.io/mcp
Claude opens the Finta OAuth flow automatically on first connection. The same custom-connector flow works in Claude on the web.

Claude Code

Add Finta as an HTTP MCP server from your terminal:
claude mcp add --transport http finta https://mcp.finta.io/mcp
The first time you use a Finta tool, Claude Code prompts you to authenticate — sign in to Finta and approve access.

VS Code Copilot

Add Finta to .vscode/mcp.json in your workspace (or your user settings):
{
  "servers": {
    "finta": {
      "type": "http",
      "url": "https://mcp.finta.io/mcp"
    }
  }
}
Reload MCP servers, then approve the Finta OAuth sign-in when prompted.

Other clients

Any client that supports remote MCP over HTTP can connect with the same URL (https://mcp.finta.io/mcp), including OpenAI Codex and other MCP-compatible assistants. Point the client at the URL and complete the Finta sign-in when prompted.

Manage your connections

You can connect more than one AI client at the same time — each sign-in is its own connection. Manage them all from the MCP page in the Finta dashboard (app.finta.io/mcp):
  • Switch between connected clients — every connected tool appears in the list; select one to see its details.
  • Choose which accounts each client can read — leave Share all accounts on to grant access to every account (including ones you add later), or turn it off to pick specific accounts. Changes are saved when you click Save and take effect immediately — there’s no need to disconnect and re-run the OAuth flow.
  • Disconnect a tool — revokes its access right away.
During the initial sign-in you can also choose which accounts a client may access on the consent screen; the MCP page lets you change that selection at any time afterward.