Yomio MCP server

Hosted endpoint

Add the hosted Yomio server to an MCP-compatible client that supports Streamable HTTP. Use this endpoint:

https://mcp.yomio.app/mcp

Send a Yomio Cognito access token in the Authorization header as Bearer YOUR_ACCESS_TOKEN. The server checks the token and uses its account identity for every tool call.

Use an access token, not an ID token or refresh token. The MCP server does not accept a developer API key. Replace the access token when it expires.

Example client configuration

Client configuration fields vary. For a client that accepts a remote MCP URL and custom headers, use this pattern:

{
  "url": "https://mcp.yomio.app/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_ACCESS_TOKEN"
  }
}

Keep the access token in the client's secret store. Do not add it to a shared prompt, source file, or public configuration.

Available tools

The public MCP server provides read-only tools for expenses, income, accounts, budgets, categories, recurring payments, and spending statistics. It uses the signed-in account and resolves Family Group membership on the server.

• List expenses, search merchants and items, and view expense details.
• View income summaries and income records.
• Read account, budget, category, and recurring payment data.
• Review spending summaries, trends, balances, top merchants, and top products.

MCP does not scan a new document. Use the REST API scan guide to upload a receipt or invoice.

Use Yomio in your own AI chat infrastructure

Configure your chat application to connect to the hosted endpoint above over HTTPS. Forward the signed-in user's access token in the authorization header. Your chat application does not need a direct database connection.

Store each user's token in your server-side secret store. Do not use one user's token for another user's requests.

The current setup requires a Yomio Cognito access token. Yomio does not yet provide self-service OAuth client registration or separate API keys for this integration.