Tabs

Name: Tabs MCP Server
Availability: InStock
Author: Tabs

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Finance27 tools

Query billing, revenue, contract, invoice and payment data from your AI assistant. 27 listed tools, OAuth sign-in, an existing Tabs subscription required.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 18 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Tabs via MCP

https://integrators.prod.api.tabsplatform.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect Tabs once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Tabs Tools & Capabilities (27)

commitments_get

commitments_list

contracts_billing_term_groups_get

contracts_get

contracts_list

contracts_performance_obligations_get

contracts_usage_get

credit_memos_by_invoice

credit_memos_get

credit_memos_list

customers_contacts_list

customers_get

customers_list

invoices_get

invoices_list

items_get

items_list

list_merchants

merchants_info_get

payments_get

payments_list

products_get

products_list

renewals_list

reports_arr_get

reports_cash_forecasting_get

revenue_list

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

It is not self-serve. Tabs requires an existing platform account with access to at least one Tabs instance. Every published plan routes through a demo or sales conversation, and the entry plan lists at $2,000 per month.
We could not verify the read-only claim on the wire. The endpoint returned HTTP 401 to an anonymous 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.
The listing and the vendor guide disagree by one tool. 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.
The OAuth scopes cannot narrow what it does. The authorization server advertises only openid, profile, email and offline_access. There is nothing product-shaped to decline at consent time; authorisation comes from your Tabs instance access instead.
The resource descriptor publishes no scope vocabulary. Its scopes_supported key is absent entirely, so a client reading only RFC 9728 sees no scopes on this resource.
The same host also serves a write-capable REST API. Tabs documents 131 endpoints there, 54 write-shaped, including invoice 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.
Single-record reads need parent identifiers. 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.
Rate limits are per Tabs instance and shared. The REST API documents 10 requests per second per merchant. A fan-out agent competes with every other integration on the same instance.
The cash forecast is directional. Tabs states it assumes on-time sending and on-time payment, and that the assumptions break down under late invoicing, late payment or usage-based billing.
ARR and recognised revenue are different measures. Tabs states ARR tracks contractual obligations while revenue recognition follows ASC 606. An assistant asked about "revenue" can answer from either.
Terms restrict use to your own internal purposes. Tabs' terms bar third-party benefit, crawling or scraping by automated means, and storing any significant portion of the content.
Contact details differ between sources. Anthropic's directory publishes support@tabs.com while Tabs' own guide names support@tabsplatform.com. Use the vendor's.
This is data access, not advice. Nothing here is accounting, tax, audit or financial guidance.

Frequently asked questions

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.