MCP

The Formance MCP server exposes selected Formance capabilities to MCP-compatible clients such as coding assistants and local agent runtimes. It lets an agent inspect financial data and validate Numscript without giving it write access to the stack.

Enable MCP on a stack#

Check your local fctl version before enabling MCP:

fctl version

Enable the MCP module on the target stack with fctl:

fctl stack module enable mcp

Run this command from an authenticated fctl context that targets the organization and stack where MCP should be enabled.

Run MCP over stdio#

MCP clients typically start the server as a local process and communicate with it over standard input and output. With Formance, fctl can serve as the MCP process:

fctl stack mcp serve --transport=stdio

Your MCP client configuration should pass the target organization and stack to fctl. The exact configuration format depends on the client:

{
  "mcpServers": {
    "formance": {
      "command": "fctl",
      "args": [
        "--organization=YOUR_ORGANIZATION_ID",
        "--stack=YOUR_STACK_ID",
        "stack",
        "mcp",
        "serve",
        "--transport=stdio"
      ]
    }
  }
}

Replace the --organization and --stack values with your own environment.

Available capabilities#

The MCP server is read-only for Formance data. It is intended for exploration, diagnostics, and assisted development workflows.

Typical workflow#

1. Enable the mcp module on a Stack v3.2 or later stack.
2. Configure your MCP client to start fctl stack mcp serve --transport=stdio.
3. Ask the client to inspect Ledger, Payments, or Reconciliation state.
4. Use Numscript validation before promoting a script into an operational workflow.