Use BankSync with Notion

Notion publishes its own MCP server that gives AI assistants access to your Notion workspace. By configuring both the Notion MCP server and BankSync MCP server in the same AI client (Claude Desktop, Cursor, etc.), you can build workflows that bridge your finances and your Notion workspace — for example, automatically syncing bank transactions into a Notion database.

Prerequisites

A BankSync account with at least one connected bank
An API key with all permission scopes (created from Workspace menu → Developers)

How it works: Notion acts as an MCP server — you connect it to your AI client (Claude Desktop, Cursor, etc.) alongside BankSync. The AI client can then read and write Notion pages while also querying your bank data through BankSync.

Step 1: Get a Notion Integration Token

Go to notion.so/profile/integrations and create a new internal integration to get your NOTION_TOKEN.

Step 2: Configure Both MCP Servers in Claude Desktop

Add both the Notion MCP server and BankSync to your claude_desktop_config.json:

claude_desktop_config.json

{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": ["-y", "@notionhq/notion-mcp-server"],
      "env": {
        "NOTION_TOKEN": "ntn_your_notion_token_here"
      }
    },
    "banksync": {
      "type": "http",
      "url": "https://mcp.banksync.io",
      "headers": {
        "X-API-Key": "bsk_your_api_key_here"
      }
    }
  }
}

The same pattern works in Cursor (.cursor/mcp.json), Zed (context_servers), and any other MCP client that supports multiple servers.

Verify Your Connection

After configuring your client, restart it and try these prompts to verify the connection is working:

“List my workspaces”

“What banks do I have connected?”

“What’s my checking account balance?”

Troubleshooting

“No tools available” or MCP server not listed

Make sure you restarted your AI client after editing the configuration file.
Verify the JSON is valid (no trailing commas, correct brackets).
Check that the URL is exactly https://mcp.banksync.io.

“Authentication failed” or “Invalid API key”

Confirm the key starts with bsk_ and has not been revoked.
Ensure the key is in the headers object under X-API-Key.
Check for accidental whitespace or newlines around the key value.

Tools are listed but return errors

Verify your API key has the required scopes. For full access, select all scopes when creating the key.
Make sure you have at least one bank connected in the BankSync app.
Check that you are passing the correct workspace ID when prompted.

Connection timeout or network errors

The MCP server uses Streamable HTTP transport. Ensure your network or proxy allows outbound HTTPS connections.
If using a VPN or firewall, allow connections to mcp.banksync.io.
Try the connection from a different network to rule out local issues.
If your client does not support remote HTTP servers, use the npm package instead: npx -y @banksync/mcp

Debugging with MCP Inspector

Use the MCP Inspector to test the connection independently of your AI client.
Run: npx @modelcontextprotocol/inspector --url https://mcp.banksync.io --header "X-API-Key: bsk_your_key"
If the Inspector connects successfully but your client does not, the issue is with your client configuration.