Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Query billing, revenue, contract, invoice and payment data from your AI assistant.
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 Tabs MCP server connects a finance team's billing and revenue records to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 27 tools covering customers, contracts, invoices, payments, credit memos, revenue, commitments and renewals. Sign-in is OAuth through Tabs' own login host, and an existing Tabs platform account is required.
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.
initialize, so we never reached tools/list and read no annotations. Tabs asserts read-only in three documents; Anthropic publishes no permissions field for this server at all. Treat the posture as a well-corroborated vendor claim, not as an independently verified fact.reports_arr_get appears in Anthropic's 27 and not in Tabs' 26-tool table. Tabs states new tools ship continuously, so treat any count as a floor rather than a ceiling.openid, profile, email and offline_access. There is nothing product-shaped to decline at consent time; authorisation comes from your Tabs instance access instead.scopes_supported key is absent entirely, so a client reading only RFC 9728 sees no scopes on this resource.SEND, invoice voiding, payment creation and customer deletion. Those are gated by an API key rather than by the connector's OAuth token — which is a reason to keep Tabs API keys away from agents.invoices_get needs a customer ID and payments_get needs both a customer and an invoice ID, so an agent must walk the hierarchy rather than fetch a record directly.support@tabs.com while Tabs' own guide names support@tabsplatform.com. Use the vendor's.No. Tabs documents the connector as OAuth 2.0 only, and states that no API keys or manual token management are needed because compatible clients handle RFC 8414 and RFC 9728 discovery automatically. That differs from the Tabs REST API on the same host, which Tabs documents as authenticating with a long-lived API key placed in the Authorization header.
Tabs says no. Its setup guide states all tools are read-only and carry a readOnlyHint annotation, and its launch post says no data can be modified through the MCP server. We could not confirm this on the wire, because the endpoint requires authentication and we did not sign in. The underlying Tabs REST API does support writes.
Your account has access to more than one. Tabs scopes every tool except list_merchants to a single Tabs instance, so Claude calls list_merchants first to see the options. With access to only one instance, Tabs selects it automatically. With several, name the one you want in plain language and Claude passes the matching instance identifier.
Sign in again through your MCP client. Tabs documents two token faults with the same fix: a missing or invalid authorization header, and an expired OAuth token. Both are resolved by letting the client re-trigger the OAuth flow. If the error says your account has no access instead, Tabs directs you to your Tabs admin to have the account provisioned.
The operator is not one Tabs recognises. Tabs accepts nine rules only, in a property:rule:value string: eq, neq, gt, gte, lt, lte, like, in, nin and between. Anything else returns an invalid filter rule error. A rejected property name is a separate error, and each tool's own description lists the filter properties it supports.
The server returns HTTP 429 naming the current limit and reset window. Tabs rate-limits per Tabs instance and returns X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers on every response. Tabs documents the general API limit as 10 requests per second per merchant, and says AI clients typically back off and retry automatically.
Tabs publishes no separate charge for MCP. Its pricing page lists four plans starting at $2,000 per month for Launch and states AI is included on every tier at no extra cost. Tabs does not name MCP in that table, so we cannot confirm which plans include the connector. Tabs also gates access on an existing platform account.
help.tabs.com/robots.txt is a bot allowlist that names ClaudeBot, GPTBot and CCBot before a blanket disallow for unlisted agents, and carries no Content-Signal header on any axis. · retrieved 2026-08-18SEND, SEND_REMINDER_EMAIL and MARK_INVOICE_AS_VOID enum values and the statement that SEND emails the customer (retrieved 2026-08-18) · retrieved 2026-08-18https://integrators.prod.api.tabsplatform.com/mcp — an anonymous initialize returned HTTP 401 with www-authenticate: Bearer resource_metadata=... and a missing-authorization-header body, while an invalid control path returned HTTP 404 with a different generic body. /.well-known/oauth-protected-resource returned HTTP 200 naming authorization_servers: ["https://login.tabs.com"] with no scopes_supported key; /.well-known/oauth-authorization-server returned HTTP 200 advertising scopes_supported of openid, profile, email and offline_access, PKCE S256, a registration_endpoint, and an issuer of https://login.tabs.com. The RFC path-insert and path-append forms of both descriptors returned HTTP 404; only the bare-root form resolves (all 2026-08-18) · retrieved 2026-08-18login.tabs.com resolves via CNAME to cname.workos-dns.com, and serves a matching OpenID Connect discovery document at /.well-known/openid-configuration — our own DNS and HTTP checks, 2026-08-18, corroborating the vendor's WorkOS statement · retrieved 2026-08-18docs.tabs.com/robots.txt allows all agents except /api/fern-docs/ and names a sitemap; www.tabs.com/robots.txt allows all. Neither carries a Content-Signal header on any axis. docs.tabs.com/llms.txt returns HTTP 200 indexing 52 documentation pages and invites .md suffix fetching; the sitemap contains no MCP page, so the connector documentation lives only on help.tabs.com (all checked 2026-08-18) · retrieved 2026-08-18financial-services category, the empty prompt_names array and the absence of any permissions field (snapshot 2026-08-16) · retrieved 2026-08-16support@tabsplatform.com per the vendor's guide, support@tabs.com per Anthropic's directory · PrivacyConnect Tabs once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.