// MCP INTEGRATION

FINTECH_MCP_SETUP

Add the FINTECH_MCP remote server to your AI assistant in minutes. Clients that support OAuth 2.1 will prompt you to log in automatically — no manual token copying required.

The Model Context Protocol (MCP) is an open standard that lets AI assistants call external tools and data sources. FINTECH_MCP exposes a remote MCP endpoint at:

https://www.fintechmcp.app/mcp

Add this URL to any MCP-compatible client and your AI assistant will gain six new tools: fintech_accounts_list, fintech_transactions_list, fintech_spending_by_category, fintech_transactions_by_category, fintech_investment_holdings_list, and fintech_investment_transactions_list.

// OAUTH CLIENTS
Claude Code, Claude Desktop, Cursor, Windsurf, ChatGPT, and Gemini all support OAuth 2.1. When you first use the MCP tool they'll redirect you to log in — no manual setup beyond adding the URL.
// TOKEN CLIENTS
Continue.dev and Zed don't support OAuth yet. For those, create an API key in your dashboard and paste it directly into the config.

CLAUDE_CODE (CLI)

OAUTH_2.1 — logs in automatically
Claude Code is the official Anthropic CLI. Add the MCP server with a single command. The first time a tool is invoked, Claude Code will open a browser to complete the OAuth login.
Add to your user account (available in all projects)
bash
claude mcp add --transport http FINTECH_MCP https://www.fintechmcp.app/mcp
Or scope it to the current project only
bash
claude mcp add --transport http --scope project FINTECH_MCP https://www.fintechmcp.app/mcp
Verify it was added
bash
claude mcp list
Remove it later
bash
claude mcp remove FINTECH_MCP
// TIP: User-scoped servers are stored in ~/.claude.json. Project-scoped servers are stored in .mcp.json at the root of your project — safe to commit to version control.

CLAUDE_DESKTOP

OAUTH_2.1 — logs in automatically
Claude Desktop manages remote MCP servers through its UI. The OAuth flow runs in a pop-up window the first time you trigger a FINTECH_MCP tool.
1
Open Claude Desktop and go to Settings (gear icon, top-right).
2
Select the Connectors tab.
3
Click Add connector → Add custom connector.
4
Enter the MCP URL: https://www.fintechmcp.app/mcp
5
Save and restart Claude Desktop.
6
In any conversation, ask about your finances — Claude will prompt you to authenticate via the FINTECH_MCP login page.
// NOTE: Remote MCP servers are configured through the UI, not the claude_desktop_config.json file (which is for local stdio servers only).

CURSOR

OAUTH_2.1 — logs in automatically
Cursor reads MCP configuration from a JSON file. You can configure it globally (all projects) or per-project. OAuth runs on first use.
Global config — create or edit ~/.cursor/mcp.json
json
{
  "mcpServers": {
    "FINTECH_MCP": {
      "url": "https://www.fintechmcp.app/mcp"
    }
  }
}
Project config — create or edit .cursor/mcp.json at your project root
json
{
  "mcpServers": {
    "FINTECH_MCP": {
      "url": "https://www.fintechmcp.app/mcp"
    }
  }
}
1
Create or edit the config file shown above.
2
Restart Cursor (or reload the window with Cmd/Ctrl+Shift+P → Reload Window).
3
Open Cursor Settings → MCP tab to confirm FINTECH_MCP appears as connected.
4
Ask Cursor Agent about your finances — it will trigger the OAuth login on first use.

WINDSURF

OAUTH_2.1 — logs in automatically
Windsurf uses a single global MCP config file. Add the server entry below, then reload Windsurf. OAuth login is triggered the first time Cascade invokes a FINTECH_MCP tool.
Edit ~/.codeium/windsurf/mcp_config.json
json
{
  "mcpServers": {
    "FINTECH_MCP": {
      "serverUrl": "https://www.fintechmcp.app/mcp"
    }
  }
}
1
Open or create ~/.codeium/windsurf/mcp_config.json.
2
Add the FINTECH_MCP entry shown above (merge with any existing servers).
3
Restart Windsurf.
4
Open the Cascade panel and ask about your accounts or transactions.
// TIP: Windsurf supports ${env:MY_VAR} interpolation in header values if you ever need to pass a static API key instead of using OAuth.

CHATGPT

OAUTH_2.1 — logs in automatically
ChatGPT supports remote MCP servers via its Connectors UI (available to Plus and Pro subscribers). The full OAuth 2.1 flow is handled automatically.
1
Open chatgpt.com and click your profile icon → Settings.
2
Go to Connectors → enable Developer Mode if not already on.
3
Click Add connector and choose MCP Server.
4
Enter the URL: https://www.fintechmcp.app/mcp
5
Click Connect. ChatGPT will open the FINTECH_MCP login page for OAuth authorization.
6
Once authorized, FINTECH_MCP tools will appear automatically in your conversations.
// NOTE: MCP Connectors require a ChatGPT Plus or Pro subscription. The feature may be labeled Actions or Connectors depending on your account tier.

GEMINI_CLI

OAUTH_2.1 — logs in automatically
The Gemini CLI reads MCP server configuration from ~/.gemini/settings.json. It supports OAuth via dynamic discovery — Gemini will auto-discover the FINTECH_MCP auth server and handle the login.
Edit ~/.gemini/settings.json
json
{
  "mcpServers": {
    "FINTECH_MCP": {
      "httpUrl": "https://www.fintechmcp.app/mcp"
    }
  }
}
1
Install the Gemini CLI if you haven't: npm install -g @google/gemini-cli
2
Open or create ~/.gemini/settings.json and add the entry above.
3
Run gemini to start an interactive session.
4
Ask about your accounts — Gemini will initiate the OAuth login on first use.
// TIP: Gemini also supports a static Bearer token via "headers": {"Authorization": "Bearer ftm_..."} if you prefer not to use OAuth.

CONTINUE.DEV

API KEY required — create one in your dashboard
Continue.dev supports Streamable HTTP MCP servers but does not yet implement OAuth — authentication is via a static API key in the config. Create a key in your dashboard first.
// GET YOUR API KEY — Log into your dashboard, open the API Keys section, and create a new key. It will be prefixed with ftm_.
Add to ~/.continue/config.yaml (or .continue/config.yaml in your project)
yaml
mcpServers:
  - name: FINTECH_MCP
    type: streamable-http
    url: https://www.fintechmcp.app/mcp
    requestOptions:
      headers:
        Authorization: Bearer ftm_your_api_key_here
Or using config.json format
json
{
  "mcpServers": [
    {
      "name": "FINTECH_MCP",
      "transport": {
        "type": "streamable-http",
        "url": "https://www.fintechmcp.app/mcp",
        "requestOptions": {
          "headers": {
            "Authorization": "Bearer ftm_your_api_key_here"
          }
        }
      }
    }
  ]
}
1
Create an API key in your dashboard.
2
Edit your Continue config file and paste in the YAML or JSON block above.
3
Replace ftm_your_api_key_here with your actual key.
4
Reload the Continue extension in VS Code / JetBrains.
5
Open the Continue chat panel and ask about your finances.

ZED

API KEY required — create one in your dashboard
Zed does not yet have native Streamable HTTP MCP support. The workaround is the mcp-remote bridge, which runs as a local stdio proxy and forwards requests to the remote server using your API key.
// GET YOUR API KEY — Log into your dashboard, open the API Keys section, and create a new key. It will be prefixed with ftm_.
Edit ~/.config/zed/settings.json
json
{
  "context_servers": {
    "FINTECH_MCP": {
      "source": "custom",
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-remote",
          "https://www.fintechmcp.app/mcp",
          "--header",
          "Authorization:Bearer ftm_your_api_key_here"
        ]
      }
    }
  }
}
1
Create an API key in your dashboard.
2
Open Zed settings: Cmd+, → click Open JSON settings.
3
Add the context_servers block above, replacing the placeholder key.
4
Save the file. Zed will install mcp-remote via npx on first run.
5
Open the AI assistant panel and ask about your accounts.
// NOTE: Native HTTP MCP support (including OAuth) is in active development for Zed. Once released, you'll be able to use the same URL-only config as Cursor and Windsurf.