Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Query consolidated actuals, budgets, forecasts and KPIs.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Datarails FinanceOS MCP server connects a company's consolidated financial data — actuals, budgets, forecasts and finance-defined KPIs — to Claude, ChatGPT and any MCP-compatible agent. All 24 published tools read. Each person signs in as themselves over OAuth, and the connector returns only what that person's own Datarails permissions already allow them to see.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
scopes_supported: ["datarails"]. No scope names read and none names write, so no consent screen can offer a narrower grant, and no issued token can be audited afterwards for the absence of write access.x-ratelimit-limit: 120 on 2026-09-09; Datarails does not publish the window that number applies to, so treat it as observed rather than as a documented quota.readOnlyHint / destructiveHint annotations were not observable. Every access claim on this page is documentary — Anthropic's directory listing plus Datarails' own documentation — not our observation of the running server.Not with the current tool inventory. Datarails documents all 24 published tools as read-only and states none creates, updates or deletes anything, including fileboxes, formulas, models, permissions or users. Datarails is explicit that this is a property of the tools published today rather than an enforced permission scope, and that write-capable tools are on its roadmap.
Yes, and it cannot exceed them. Datarails states every tool call is authorized against the calling user's role and permission groups exactly as in the Datarails web application. Two colleagues connecting the same organization can therefore see different tables. Datarails also notes there is no narrower MCP-only scope that restricts access below a user's existing role.
Yes. Datarails documents the connector as a paid feature requiring an active FinanceOS AI connector subscription for your organization. A Super Admin must also enable it under AI Center then Manage AI Connectors, which is a per-organization action rather than a per-user one. Datarails directs new setups to a Customer Success Manager or its support address.
The connector is most likely not enabled for your organization. Datarails documents get_connector_status as always available for exactly this check, and it reports whether the connector is switched on. If it is off, a Super Admin enables the platform under AI Center then Manage AI Connectors. Datarails also advises confirming the organization holds an active connector subscription.
Only the result of each individual tool call, already filtered by the calling user's permissions. Datarails states there is no bulk export, dataset copy, sync job or background transfer, and that the MCP layer persists no financial records beyond the request. Row-level reads are paginated at 100 rows per page by default, and aggregation responses are capped by a response-size limit.
In the United States, as of Datarails' documentation updated 2026-08-26. Datarails states the MCP service is stateless and stores no customer data, and that your financial data continues to live at rest only in your existing Datarails environment and its region. Region-aware routing behind the same global URL is under evaluation with no committed delivery date.
Only at session level today. Datarails documents a Super Admin audit log in AI Center covering session ID, member, AI platform, timing, duration and status, plus a per-session event timeline. Datarails states that tool-call-level audit events emitted by the MCP server itself, giving per-query attribution, are still in development and should not be assumed available.
support.datarails.com/robots.txt (HTTP 200) permits /hc/en-us/articles/ and disallows only /stats/view under the Help Center API, so the article was retrieved at HTTP 200 from the public Zendesk Help Center API route /api/v2/help_center/en-us/articles/25849710214556.json. No Content-Signal directive is published on that host. · retrieved 2026-08-26https://mcp.datarails.com/mcp — anonymous initialize returnedhttps://mcp.datarails.com/.well-known/oauth-protected-resource/mcp (HTTP 200, 2026-09-09). An invented server name at the same prefix returned HTTP 404, so the descriptor discriminates. · retrieved 2026-09-09https://mcp.datarails.com/.well-known/oauth-authorization-server (HTTP 200, 2026-09-09): scopes_supported: ["datarails"], PKCE S256, authorization-code and refresh-token grants. · retrieved 2026-09-09mcp.datarails.com — eight paths (/mcp/write, /mcp/readonly, /mcp/admin, /mcp/finance, /mcp/v2, /mcp/full, /sse, /api/mcp) returned HTTP 404; mcp-write.datarails.com and mcp-readonly.datarails.com failed to resolve (2026-09-09). mcp.datarails.com/robots.txt returned HTTP 404, so the standing robots control was inconclusive here; the route-aware 404s and the discriminating descriptor established the negative instead. · retrieved 2026-09-09www.datarails.com/robots.txt (HTTP 200) allows crawling and explicitly grants Allow: / to GPTBot, OAI-SearchBot, OAI-AdsBot and ChatGPT-User. · retrieved 2026-09-09Connect Datarails FinanceOS once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.