MCP Setup | Bank Statement Conversion - Bank-Statement-Conversion
Remote MCP server

Set up Bank Statement Conversion MCP.

Connect Claude, Codex, Cursor, ChatGPT-compatible clients, and custom agents to live conversion tools with a scoped dashboard token.

Start setup View agent options
Remote endpointhttps://bank-statement-conversion.com/mcp/bank-statement-conversionToken environment variableBSC_API_TOKEN

Four setup steps.

Use the hosted endpoint, store one token locally in your agent client, and keep actions confirmable.

1

Create a dedicated token

Use the dashboard API Tokens page to create a token for this agent, separate from personal or production app tokens.

2

Enable scoped abilities

Grant only account status, upload, status read, and download abilities needed by the MCP tools.

3

Add the remote endpoint

Point your MCP-capable client at the hosted Bank Statement Conversion endpoint.

4

Confirm sensitive actions

Have the agent ask before uploading financial documents or preparing converted file downloads.

Endpoint

Add the remote MCP server.

Use Streamable HTTP when your client asks for the transport. Some clients accept a bearer token environment variable, while others use an Authorization header.

Codex config
[mcp_servers.bank_statement_conversion]
url = "https://bank-statement-conversion.com/mcp/bank-statement-conversion"
bearer_token_env_var = "BSC_API_TOKEN"
Generic Streamable HTTP config
{
    "mcpServers": {
        "bank-statement-conversion": {
            "type": "streamable-http",
            "url": "https://bank-statement-conversion.com/mcp/bank-statement-conversion",
            "headers": {
                "Authorization": "Bearer ${BSC_API_TOKEN}"
            }
        }
    }
}
Authentication

Keep the token out of prompts.

Create a dashboard token, store it as an environment variable, and never paste the token into chat, source code, docs, screenshots, or logs.

Create API token
Environment variable
BSC_API_TOKEN=your_dashboard_token
account:status conversion:read conversion:upload conversion:download

Claude and Anthropic setup.

Use the same hosted MCP endpoint with Claude connectors or the Anthropic Messages API.

Claude

Claude app and Claude Desktop

  1. Create a Bank Statement Conversion dashboard token from API Tokens.
  2. Open Claude settings, then go to Connectors and choose Add custom connector.
  3. Enter https://bank-statement-conversion.com/mcp/bank-statement-conversion as the remote MCP server URL.
  4. Use the dashboard token for bearer authentication when Claude asks to connect.
  5. Enable the connector in chat and run an account status check before uploading files.
Anthropic API

Messages API MCP connector

Keep BSC_API_TOKEN server-side and pass it as the MCP server authorization token. The request also needs an MCP toolset that references the same server name.

Anthropic MCP request shape
{
    "model": "claude-sonnet-4-5",
    "max_tokens": 1024,
    "messages": [
        {
            "role": "user",
            "content": "Check whether my Bank Statement Conversion account can run a conversion."
        }
    ],
    "mcp_servers": [
        {
            "type": "url",
            "url": "https://bank-statement-conversion.com/mcp/bank-statement-conversion",
            "name": "bank-statement-conversion",
            "authorization_token": "${BSC_API_TOKEN}"
        }
    ],
    "tools": [
        {
            "type": "mcp_toolset",
            "mcp_server_name": "bank-statement-conversion"
        }
    ],
    "betas": [
        "mcp-client-2025-11-20"
    ]
}

Available MCP workflow.

The tools map to the same public conversion workflow used by the REST API.

Account status

Check credits, page allowance, plan, and whether conversion can run.

Upload conversion files

Send confirmed bank statements, invoices, receipts, or structured statement files.

Read conversion status

Poll job progress until a completed response includes a download token.

Download output

Retrieve the completed conversion using the returned download token.

GET /api/user-statusPOST /api/uploadGET /api/conversion-status/{jobId}GET /api/download/{downloadToken}
Safety scope

Financial documents need explicit control.

MCP makes conversion available inside chat, so the workflow should stay narrow, auditable, and easy to revoke.

Use a dedicated API token for every agent workspace.
Enable only the four conversion abilities shown on this page.
Confirm before uploading statements, invoices, receipts, or accounting files.
Confirm before preparing download links for converted output.
Use returned download tokens. Do not construct file URLs.
Revoke the dashboard token when agent access should stop.

Ready to connect an MCP client?

Set BSC_API_TOKEN, add the remote endpoint, and have the agent run a status check first.

Manage API tokens API reference