Connect with browser sign-in
Add the server URL to an AI client that supports remote Streamable HTTP and OAuth. The client opens Yomio sign-in in your browser, then keeps its access tokens for you.
https://mcp.yomio.app/mcp- 1. Add YomioPaste the server URL into your client's remote MCP settings.
- 2. Sign inSign in to your Yomio account in the browser window.
- 3. Approve accessCheck the AI client name and approve its read-only access.
Connect from a local AI client
If your AI client starts local stdio servers, add this entry to its MCP configuration:
{
"mcpServers": {
"yomio": {
"command": "npx",
"args": [
"-y",
"yomio-mcp-stdio"
]
}
}
}On first use, the connector opens Yomio sign-in in your browser. Approve read-only access, then return to your AI client. It stores and refreshes your session in the operating system credential store, so you do not need to copy an access token.
The connector runs on the same computer as your AI client and calls the hosted Yomio MCP server. Keep a browser available on that computer for sign-in. For a headless AI server, use the remote OAuth connection below instead.
On Linux, GNOME Keyring or KWallet keeps the session across restarts. See the connector setup and credential-storage notes for more details.
Use Yomio in your own AI chat infrastructure
Connect from your MCP client or server over HTTPS. Each user signs in to their own Yomio account, and the MCP client handles the OAuth token exchange and refresh. Do not ask users to copy or share access tokens.
- Transport
- Streamable HTTP
- Authorization
- OAuth authorization code with PKCE (S256)
- OAuth issuer
- https://mcp.yomio.app
- Resource scope
mcp:read
Current MCP clients can discover Yomio's authorization endpoints automatically. A custom client must support Client ID Metadata Documents (CIMD), publish its client metadata at a public HTTPS URL, and use the same URL as its OAuth client_id. Yomio checks the registered redirect URI before sign-in and shows the client name and return address before access is granted.
Publish a metadata document like this one, with your own client and callback URLs:
{
"client_id": "https://chat.example.com/oauth/client-metadata.json",
"client_name": "Example AI Chat",
"application_type": "web",
"redirect_uris": [
"https://chat.example.com/oauth/callback"
],
"response_types": [
"code"
],
"grant_types": [
"authorization_code",
"refresh_token"
],
"token_endpoint_auth_method": "none"
}The document must be public, return application/json, and use HTTPS. Clients that only support OAuth Dynamic Client Registration cannot connect yet.
Access tokens expire after one hour. The MCP client can refresh them for up to 30 days, and can revoke its connection when the user disconnects. Tokens are scoped to this MCP endpoint and cannot be used as REST API credentials.
Server-to-server requests do not need an Origin header. If your client makes requests from a browser, Yomio must allow its exact origin.
What your AI client can read
Expenses
Search expenses, inspect a record, and find merchants or purchased items.
Income and accounts
Read income records, account balances, and budget status.
Categories and recurring payments
Review your categories and recurring payment schedules.
Spending statistics
Explore spending summaries, trends, balances, merchants, and products.
MCP does not scan a new receipt or invoice. Use the REST API scan quickstart for document uploads.
Find Yomio in MCP directories
Yomio is preparing its hosted server metadata for the official MCP Registry. Registry publication needs ownership verification for the app.yomio namespace and a live OAuth deployment.
Yomio also provides a domain AI Catalog and a server card. These crawler discovery formats are experimental, so client support can vary.
Review the Registry metadata file while publication is pending.