Model Context Protocol (MCP)

The Fintoc Model Context Protocol (MCP) server provides tools that AI agents can use to interact with the Fintoc API. Agents can also search Fintoc’s knowledge base, including the documentation. Before you connect, you need an active Fintoc account with live mode access. You also need a supported client: Claude, ChatGPT, Cursor, VS Code, or Claude Code.

Connect to Fintoc’s MCP server

Claude supports custom connectors on the web, desktop, mobile, and Cowork. Custom connectors are available on the Free, Pro, Max, Team, and Enterprise plans. For configuration options, see the Claude documentation.Team / Enterprise:

An Owner must first add the connector in Organization settings → Connectors (Add → Custom → Web).
Go to Customize → Connectors.
Find the Fintoc custom connector your Owner added and click Connect.

Pro / Max / Free:

Go to Customize → Connectors.
Click ”+” then Add custom connector.
Enter the server URL https://mcp.fintoc.com.
Click Add, then connect and authenticate via OAuth.

Enable the connector for each conversation from the ”+” button in chat → Connectors.

You can enable MCP servers on ChatGPT with a Pro, Plus, Business, Enterprise, or Education account. Follow the OpenAI documentation for instructions. Use the following parameters when setting up your custom connector:

The server URL is https://mcp.fintoc.com.
Use OAuth as the connection mechanism.

Fintoc’s MCP server also works with OpenAI’s Responses API when you build autonomous agents.

Add the following to your ~/.cursor/mcp.json file. For configuration options, see the Cursor documentation.

{
  "mcpServers": {
    "fintoc": {
      "url": "https://mcp.fintoc.com"
    }
  }
}

Add the following to your ~/.vscode/mcp.json. For configuration options, see the VS Code documentation.

{
  "servers": {
    "fintoc": {
      "type": "http",
      "url": "https://mcp.fintoc.com"
    }
  }
}

Run the following command:

claude mcp add --transport http fintoc https://mcp.fintoc.com

MCP is an open protocol supported by many clients. See your client’s documentation for connection instructions. Use the server URL https://mcp.fintoc.com and OAuth as the connection mechanism if possible.

{
  "fintoc": {
    "url": "https://mcp.fintoc.com"
  }
}

When the client opens the connection, Fintoc shows a consent screen. Authorize the connection and select the scopes to grant to your MCP session. A token operates only in live mode. The consent screen only lists scopes that meet both of these conditions:

You have the matching resource permission in the dashboard. Each scope corresponds to a resource and access level from your dashboard role. For example, movement:view requires Read access to Movements.
Your organization has the product that the resource belongs to. For example, movement:view only appears if your organization has the Movements product.

If a scope is missing from the consent screen, Fintoc can’t grant it to your MCP session. An existing connection keeps the scopes you authorized for that connection. To use operations that need a scope added after authorization, reconnect the client. Then grant the required scope, such as Team for managing your organization’s users, on the consent screen.

Read-only sessions

Each scope has an access level: view for reading, or manage for creating and changing data. A manage scope includes the matching view scope. To give an agent read-only access, grant only view scopes on the consent screen. Operations that need a manage scope then fail, so the agent can’t create payments, transfers, or other records.

Tools

We recommend enabling human confirmation before tools run. Use caution when you run the Fintoc MCP server with other servers to avoid prompt injection attacks. To request more tools or share feedback, ask your agent to use the submit_feedback tool, or contact Fintoc support at soporte@fintoc.com. The server exposes the following MCP tools:

Category	Tool	Description
Operations	`fintoc_tool_search`	Search the operations available through Fintoc MCP.
Operations	`fintoc_tool_details`	Get the parameters and permissions for an operation.
Operations	`fintoc_tool_read`	Read data from Fintoc.
Operations	`fintoc_tool_write`	Write data in Fintoc. Some operations can move money.
Resources	`fetch_resource`	Retrieve a Fintoc resource by its `id`.
Other	`submit_feedback`	Report blockers or unexpected behavior to Fintoc.

The operation tools make supported Fintoc actions available through MCP without exposing one tool per action. This keeps the tool set compact as Fintoc adds more capabilities.

Supported operations

The Fintoc MCP server currently supports:

Payments: list and create customers; list payment intents, checkout sessions, and payment methods; list, create, and cancel refunds
Billing: create, finalize, and void invoices; list, create, and update subscriptions
Your Fintoc invoices: list the invoices Fintoc issues to your organization
Movements: list links, linked bank accounts, and movements
Payouts: list payouts and payout resources
Business Accounts: list accounts, account statements, entities, account numbers, and transfers; create account numbers
Webhooks: list, create, and update webhook endpoints
IP restrictions: add an allowed IP range (Classless Inter-Domain Routing (CIDR) block) to your organization
Team: list organization users and assignable roles; invite users with a predefined role

The operations available in a session depend on your Fintoc products and the scopes granted during authorization.

Required scopes

Each operation requires one scope. Use fintoc_tool_details to see the scope for a specific operation.

Operations	Required scope
List customers, list payment methods	`customer:view`
Create customers	`customer:manage`
List payment intents and checkout sessions	`payment:view`
List refunds	`refund:view`
Create and cancel refunds	`refund:manage`
Create, finalize, and void invoices	`invoicing_invoice:manage`
List subscriptions	`invoicing_subscription:view`
Create and update subscriptions	`invoicing_subscription:manage`
List your Fintoc invoices	`billing:view`
List links	`link:view`
List linked bank accounts and movements (Movements product)	`movement:view`
List payouts and payout resources	`payout:view`
List accounts and account statements for Business Accounts	`account:view`
List entities	`entity:view`
List account numbers	`account_number:view`
Create account numbers	`account_number:manage`
List transfers	`transfer:view`
List webhook endpoints	`webhook_endpoint:view`
Create and update webhook endpoints	`webhook_endpoint:manage`
Add an allowed IP range	`allowed_cidr_block:manage`
List organization users and assignable roles	`organization_user:view`
Invite users	`organization_user:manage`

If an operation fails because a scope is missing, check whether the scope appears on the consent screen. If it does not, your dashboard user lacks the matching permission or your organization lacks the product. For example, list_links works but list_movements fails with a missing movement:view scope.

Ask an Admin of your organization to grant you the required access level for the resource in the dashboard. For movement:view, that’s Read access to Movements under Reconciliation. See Permission roles.
If the resource isn’t available in your organization, contact Fintoc support to enable the product.
Reconnect your MCP client and grant the scope on the consent screen.

Actions the server does not expose Some actions have no tool on purpose, so an agent cannot take them on your behalf:

Paying an invoice. Use Pay an invoice.
Canceling a subscription. Use Cancel a subscription.
Detaching the payment method of a subscription. Use Detach the payment method from a subscription.
Changing a user’s role or removing a user from your organization. Use the dashboard.

Refunds are the exception. A refund returns money to the customer who paid, and you can cancel it while it is still pending.

Connect to the Fintoc Docs MCP server

The docs server lets an agent answer questions about the Fintoc API by querying the documentation. Use it when you want code samples, endpoint lookups, or explanations without leaving your editor.

Cursor
VS Code
Claude Code
ChatGPT
Other

Add the following to your ~/.cursor/mcp.json file. For configuration options, see the Cursor documentation.

{
  "mcpServers": {
    "fintoc-docs": {
      "url": "https://docs.fintoc.com/mcp"
    }
  }
}

Add the following to your ~/.vscode/mcp.json. For configuration options, see the VS Code documentation.

{
  "servers": {
    "fintoc-docs": {
      "type": "http",
      "url": "https://docs.fintoc.com/mcp"
    }
  }
}

Run the following command:

claude mcp add --transport http fintoc-docs https://docs.fintoc.com/mcp

The server URL is https://docs.fintoc.com/mcp.
Use OAuth as the connection mechanism.

The Fintoc Docs MCP server also works with OpenAI’s Responses API when you build autonomous agents.

MCP is an open protocol supported by many clients. See your client’s documentation for connection instructions. Use the server URL https://docs.fintoc.com/mcp.

{
  "fintoc-docs": {
    "url": "https://docs.fintoc.com/mcp"
  }
}

Home

Resources

Payments

Business Accounts

Movements

Skeleton group medium 9

Model Context Protocol (MCP)

Connect to Fintoc’s MCP server

Read-only sessions

Tools

Supported operations

Required scopes

Connect to the Fintoc Docs MCP server

Home

Resources

Payments

Business Accounts

Movements

Skeleton group medium 9

​Connect to Fintoc’s MCP server

​Read-only sessions

​Tools

​Supported operations

​Required scopes

​Troubleshooting: a required scope isn’t on the consent screen

​Connect to the Fintoc Docs MCP server

Connect to Fintoc’s MCP server

Read-only sessions

Tools

Supported operations

Required scopes

Troubleshooting: a required scope isn’t on the consent screen

Connect to the Fintoc Docs MCP server