Folio.
Tools for your agent.
A typed client, MCP server and CLI for Folio. Accounts, transactions, events, receipt bytes, categories and payment drafts.
Local setup
On a laptop, prefer stdio. Cursor can load vendor credentials from a gitignored envFile. Do not put secrets in mcp.json.
npx -y @bruchris/folio-mcpLocal Streamable HTTP for transport tests: npm run http:folio on 127.0.0.1:3000. Path B&B breaks npm .bin; use node …/tsx or dist.
Use your own Folio credential in the client or host environment. The model reads receipts; this adapter does not parse merchant layouts or guess VAT.
Hosted setup
This origin serves three routes:
Private-beta access to /mcp uses a host token named MCP_AUTH_TOKEN. That token authenticates the MCP client to this host. It is not a Folio credential. Put the token in the OS or shell environment and send it as an Authorization header. Remote Cursor HTTP does not support envFile.
This host then calls Folio with a separate vendor credential. Do not mix those layers. Cursor Authenticate / ChatGPT Sign in (MCP OAuth against this host) is not enabled on this release.
claude mcp add --transport http folio https://folio.bruchris.me/mcp --header "Authorization: <MCP_AUTH_TOKEN>"Freddy imports the TypeScript client. It does not call this URL as RPC. MCP writes preview until confirmed; that confirm flag is not Freddy ApprovalService.
Privacy and security
This page never publishes keys. Hosted HTTP disables local filesystem attachment tools. Browser Origin values must match an exact allowlist; there is no wildcard. See SECURITY.md and the hosted setup notes.