Connect a client¶
Use Streamable HTTP at https://fillfolio.com/api/mcp. Your host handles OAuth sign-in, consent, token refresh, and reconnection. Keep passwords, codes, and tokens in that interface.
Connection requirements¶
- Use an eligible paid Fillfolio account. Spending and budgets need active ULTRA/HYPER eligibility, bank-spending consent, and independent per-client read permissions.
- Let the host read the protected-resource metadata and authorization-server metadata.
- Request OAuth scope
mcp:read, use PKCES256, and bind authorization to resourcehttps://fillfolio.com/api/mcp. - Use an accepted registered client identity and exact callback. Fillfolio accepts specific Client ID Metadata Documents and disables Dynamic Client Registration. An arbitrary metadata URL or callback fails.
Keep a native host's accepted identity. The legacy Clerk client ID belongs to existing legacy configurations; it is not a universal client ID for new hosts. Internal permissions such as spending:read are application grants, not extra OAuth scopes to request from the current issuer.
Compatibility at this snapshot¶
| Host | Status and next step |
|---|---|
| ChatGPT Work desktop | Existing setup passed live acceptance. Use the plugin/connector flow available on your supported surface. Native plugin 0.1.1 remains In review. |
| Codex | Existing setup passed live acceptance. Use the remote server entry and browser login below. |
| Claude Code | Registered identity. Use its published identity and accepted callback; this snapshot adds no live acceptance result. |
| Claude web | Registered identity. Use its custom-connector flow with an accepted identity; this snapshot adds no live acceptance result. |
| Cursor, VS Code, and other hosts | Require an accepted client identity and callback before compatibility can be claimed. Read the conditional examples in the source guide. |
Codex¶
If your setup does not already expose Fillfolio, add this to your personal ~/.codex/config.toml:
[mcp_servers.fillfolio]
url = "https://fillfolio.com/api/mcp"
Then run:
codex mcp login fillfolio
Complete consent using Codex's accepted native identity. Reuse an existing working connection instead of adding a duplicate. Codex MCP guide
Claude Code¶
Add the endpoint, then open /mcp in an interactive session to sign in:
claude mcp add --transport http --scope user fillfolio https://fillfolio.com/api/mcp
The command configures the endpoint. Successful OAuth still depends on the registered identity and callback. Claude Code MCP guide
ChatGPT and Claude chat¶
Use the host's supported plugin or custom-connector installation flow, then complete OAuth. ChatGPT web does not read local Codex settings. An ordinary chat attachment does not install a skill or tool connection. Follow the detailed client setup guide for installation paths and evidence limits.
Confirm a read¶
Ask “Show my Fillfolio portfolio summary with its reporting currency and data limits.” On a host that renders MCP Apps, open_fillfolio with {} opens a read-only dashboard. Other accepted hosts can use the nine financial read tools without rendering it.
A 401 needs host refresh or reconnection. Resolve a 403 by checking eligibility and client permissions in Fillfolio Settings. Reconnecting will not enable a disabled read permission. Respect Retry-After on 429; treat temporary service failure as an error.