Financial Cents launches MCP server for accounting workflows

Financial Cents launched a Model Context Protocol server on Oct. 20, giving supported AI clients a way to read and change records in its accounting practice-management platform. The company says the remote server is now available to firms on its Scale plan.

Its live integration guide lists 37 tools: 22 for reading data and 15 for writing it. The catalog covers clients, projects, team tasks, time entries, invoices, payments, credit memos, proposals, files, service items, tax codes and client chat. A connected assistant can retrieve records and perform specified actions without requiring the user to move the work into a separate interface.

Model Context Protocol, or MCP, is a standard for AI clients to call tools and access external data. Financial Cents describes its implementation as a remote server that uses Streamable HTTP and OAuth 2.1 with PKCE. Users sign in on the Financial Cents domain instead of pasting an API key into the AI client.

During consent, the user selects one company account. Financial Cents says the resulting token remains bound to that account, while every request is checked against the user’s existing permissions. The connection can be revoked in the API section of Financial Cents settings; reconnecting then requires fresh consent.

Those controls apply at the Financial Cents account and user-permission level. A separate ServiceNow runtime credential for scoping agent permissions and supporting revocation applies related controls at an agent-runtime layer.

The write tools can create or update records, upload files, and send or edit client-chat messages. The catalog offers no delete operations. Several update tools preserve values omitted from a request or use an archival state where the underlying record supports one.

The published catalog sets additional boundaries around financial actions. The invoice tool can create drafts or templates and update invoices, but it cannot send, charge, void or delete them. Credit-memo tools can apply credit to invoices and may cause Financial Cents to email a client when an invoice becomes fully settled.

Financial Cents says the connected AI client asks the user to confirm a change before carrying it out. The company adds a separate confirmation when a file upload would notify contacts in a client portal. It also says every MCP call is recorded with the caller, action and duration, and that requests are rate limited.

The descriptions of authorization, confirmation, auditing and rate limits come from Financial Cents’ documentation. The opened evidence did not include an independent security test or an inspection of the feature inside an authenticated firm account. The company does not disclose audit-log retention, administrator visibility, rate-limit thresholds or token lifetime in the opened sources. Confirmation behavior inside an AI client may vary with that client’s interface.

The product page warns that client-authored chat content is marked as untrusted for the assistant and tells users to verify summaries and review actions, particularly financial ones. The detailed guide documents connections for Claude, Claude Code, Cursor, VS Code, ChatGPT, Notion and other remote-MCP clients, subject to each client’s plan, administrator, mode and version requirements. Creating a client-chat message emails the topic’s client contacts and cannot be undone through the tool, so the catalog directs the assistant to confirm the wording before creation.