Firmary
Firmary · Practice Management
Firmary connects remote MCP clients to an accounting firm's client records, tasks, documents and billing. Agents can act as connected staff or as named firm agents, with permissions and approval rules configured in Firmary. Operations staff and accounting teams within advisory firms would use it to coordinate client work and document requests.
Provides one system's data and actions. Reads and writes inside a single product of record; it can act, but only within its own walls. More on System servers → All seven roles →
Caveats
- Vendor-reported registry listing, client compatibility and permission enforcement have not been independently verified.
- This is not read-only: the vendor demonstrates task creation through MCP. The page does not provide a complete MCP action inventory or describe securities order placement.
- Agents access firm records through a remote service. The supplied material does not specify data residency, retention or how connected AI clients handle retrieved client information.
- Firmary is presented as accounting-firm practice management, not a portfolio, custody or financial-planning system. Books-and-tax relevance is workflow coordination rather than demonstrated ledger reconciliation or return preparation.
- The task-creation demonstration is explicitly labeled a product preview with fictional client data; it does not establish production reliability.
- Start with read-only scopes and keep client-side approval prompts on until the connection is proven.
How to connect Firmary
Step 1
Remote server: paste a URL
Firmary publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.
Endpoint
https://os.firmary.app/api/mcp
Client config snippet
{
"mcpServers": {
"c2678dc1-785a-47bc-a667-246e41355b32": {
"url": "https://os.firmary.app/api/mcp"
}
}
}Step 2
Authenticate with OAuth
Your client opens a browser sign-in with the vendor. Approve only the scopes you need, and use a read-only account first when the platform offers one.
Step 3
Verify, then widen access
Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.