Tipalti MCP server for Claude: what it reads, access and how to connect

Tipalti hosts a read-only MCP server in beta for Claude Enterprise, covering bills, payees, payments, accounts and cards. No local server. Verified 21 Oct 2026.

In beta and rolling out gradually, for Claude Enterprise only. Tipalti says to contact your Tipalti representative to check eligibility and enrol.

Official remote MCP · read-only (beta)

Hosting: Remote, hosted by Tipalti at https://mcp.tipalti.com/mcp. No local or open-source server.
Auth: Browser sign-in with your Tipalti login through a public OAuth client (client ID mcp-public, no client secret), per Tipalti's setup docs.
Read / write: Read-only. Tipalti says it cannot create, change or delete data, or initiate, approve, modify or cancel payments.
Works with: Claude Enterprise only during the beta (Claude.ai, Claude Desktop, Claude Code). Tipalti says other platforms are planned; ChatGPT is not mentioned.
Plan requirement: Tipalti production account, beta enrolment through your Tipalti representative, and Claude Enterprise. Governed by Tipalti's MCP Services Schedule; no separate price published.
Last changed: 2026-10-14 (MCP Services Schedule updated)
Verification: Verified 21 Oct 2026 by theFinanceStack · confidence: medium

What can an agent do with Tipalti through MCP?

It answers questions about 5 Tipalti data areas: bills, payees, payments, accounts and cards. Access is read-only, so it cannot pay, approve or change anything in Tipalti.

Tipalti says the server uses the same underlying data and permissions as Tipalti AI.

What it can read

Per Tipalti's setup page:

Bill details, statuses and aging
Payee details
Payment details and statuses
Virtual account balances and funding requirements
Card details and card transactions

Who sees what

What a user sees depends on the scopes a Payer administrator enables and that user's Tipalti roles.

Good to know

Tipalti does not publish tool names or a tool count.
Its MCP Services Schedule says it may add, change or remove tools at any time.
Tipalti documents no tool that posts, drafts, approves or moves money.

Can

Look up bill details, statuses and aging
Read payee details
Check payment details and payment statuses
Report virtual account balances and funding requirements
Read card details and card transaction details

Cannot

Create, change or delete anything in Tipalti, per Tipalti
Initiate, approve, modify or cancel any payment, per Tipalti's MCP Services Schedule
Show data beyond the user's existing Tipalti role, permissions and enabled scopes, per Tipalti
Connect from ChatGPT or other AI platforms during the beta; Tipalti supports Claude Enterprise only

What access does it get?

Read-only. The signed-in user sees only what they can already see in Tipalti, narrowed further by the scopes a Payer administrator enables. Tipalti does not publish the scope names.

Where	Scopes and permissions (as documented)	Admin requirement
Tipalti MCP (remote, mcp.tipalti.com)	Scope names not documented by the vendor. Tipalti says each request is checked against the user's role and permissions, the scopes the Payer administrator enabled, and the account; it may also mask or withhold sensitive financial data from responses. Tipalti's developer docs link to a help-centre article on turning on AI Integration; it isn't publicly readable (login may be required), so whether it lists scope names couldn't be checked.	A Payer administrator must turn on AI Integration in Tipalti Administration. For Claude.ai, an Owner, Primary Owner or someone with a custom role that includes Manage access to Libraries adds the custom connector; each member then connects with their own Tipalti sign-in.

How do I connect it?

Enrol in the beta and have a Payer administrator turn on AI Integration, then add https://mcp.tipalti.com/mcp in Claude with the OAuth client ID mcp-public.

In Tipalti, a Payer administrator turns on AI Integration under Administration (see Tipalti's help article https://help.tipalti.com/hc/en-us/articles/44061816631319-Turn-on-AI-Integration).
A Claude Enterprise Owner adds a custom connector in Organization settings › Connectors with the URL https://mcp.tipalti.com/mcp, authentication "Sign in when needed", OAuth client "Use your own OAuth client", client ID mcp-public and the client secret left blank, per Tipalti.
Each user goes to Customize › Connectors, clicks Connect and signs in to Tipalti.
In a chat, open the + menu, choose Connectors and switch Tipalti on for that conversation.
Claude Desktop alternative documented by Tipalti: add the block below to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json) and restart. It runs the mcp-remote npm package through npx as a local bridge.

{
  "mcpServers": {
    "tipalti": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.tipalti.com/mcp",
        "--static-oauth-client-info",
        "{\"client_id\":\"mcp-public\"}"
      ]
    }
  }
}

No Claude directory listing as of 21 Oct 2026, so there is no Add to Claude button.

What should a finance team watch for?

Beta status, Claude Enterprise only, undocumented scope names and tool list, and payee and card data flowing into your AI platform.

Beta and gradual rollout: access is by eligibility, and Tipalti may change tools at any time or discontinue the service with at least 30 days' written notice (less for security or legal reasons).
Tipalti may apply rate limits and may mask or withhold sensitive financial data from responses; it doesn't publish the limits or what is masked. Masked or withheld fields (for example payee bank details or card numbers) mean answers may be incomplete, so reconcile any totals used in close work back to Tipalti reports. Tipalti's schedule also says it "does not guarantee compatibility with all AI Platforms".
The server returns payee details and card data. Enable only the scopes the use case needs and confirm with Tipalti what the scopes cover before your security review.
Data handling: Tipalti says it stores tool-call queries, parameters and responses at the MCP server layer, and that once data reaches your AI platform it is governed by your agreement with that provider. Review both sets of terms.
The customer is responsible for securing credentials and tokens under Tipalti's schedule. The Desktop path relies on the third-party mcp-remote package, and Tipalti's config block doesn't pin a version, so npx can pull whatever version is current on npm. Check your IT policy on running it and consider pinning a reviewed version.
Bill descriptions, payee names and memo fields are untrusted text. Tipalti's server is read-only, so an injected instruction can't make it write anything. Other connected tools could. Keep a person approving anything that writes or pays elsewhere.
Firm and multi-client access isn't documented by Tipalti. Each user needs a Tipalti login and Claude Enterprise during the beta.

How could finance teams and accounting firms use it?

The server is read-only, so it suits questions and reporting on payables, payments and funding. Any action still happens in Tipalti.

Inside a company

Ask which bills are overdue or stuck in a status before a payment run, using bill aging and status data.
Check virtual account balances against funding requirements before a scheduled payment batch.
Answer supplier "where is my payment?" queries from payment status without opening Tipalti.
Summarise card transactions by card for a month-end spend review, then tie totals back to Tipalti.

At an accounting firm

Prepare an AP aging summary for a client meeting from bill data in the client's Tipalti account.
Review payment statuses during a month-end close checklist and list exceptions for the client to resolve.
Compare virtual account balances with funding requirements before upcoming payment runs and flag shortfalls to the client.
Pull payee and payment details to answer a client's vendor-payment queries during month-end.

A person approves anything that changes the ledger or Tipalti. Payments and approvals stay in Tipalti.

Want Tipalti connected to Claude for your team?

We configure scoped connections and a review step before anything changes your books. Fixed fee.

Book a 30-minute setup call

Change log

Date	Change	Source
2026-10-14	Tipalti updates its MCP Services Schedule: Tipalti-hosted, read-only, rate limits, masking, 30-day discontinuation notice	tipalti.com/legal/mcp-services-schedule/
2026-10-11	Tipalti MCP setup page last updated: server URL, client ID mcp-public, Claude Enterprise-only beta, 5 data areas	documentation.tipalti.com/docs/tipalti-mcp

FAQ

Is this official?

Yes. Tipalti hosts the MCP server itself and documents it on its own developer site and in its MCP Services Schedule. It is in beta.

Is it free?

Tipalti doesn't publish a price. The MCP Services Schedule sits under your Tipalti services agreement. You also need a Tipalti production account and Claude Enterprise.

Does it change data in Tipalti?

No. Tipalti says "it can't create or change anything in your account" in this release, and cannot initiate, approve or cancel payments.

Is my data used to train models?

Tipalti's schedule doesn't address training. It says Tipalti stores tool-call data to run and improve the service, and data sent to your AI platform falls under that provider's terms. Check both.

Can my accountant use it on my behalf?

Tipalti doesn't document this. Each request runs under the signed-in user's Tipalti role and permissions. Ask Tipalti how an outside accountant would be given a user. The beta also requires Claude Enterprise.

Something wrong or out of date? Tell us and we'll email you when it's fixed.

Sources

Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.