Anchor MCP server and Claude connector: what it does, access, how to connect

Anchor runs one hosted MCP server (OAuth) that reads billing data and writes contacts, proposal drafts, live agreements and templates. It can't move money. Verified 21 Oct 2026.

Official remote MCP · read & write

Hosting: Remote HTTP only, hosted by Anchor (https://mcp.app.sayanchor.com/mcp). No local server or public repo.
Auth: OAuth 2.0 sign-in with your Anchor login; you pick a business if you can access more than one. Claude never sees your Anchor password, per Anchor.
Read / write: Read and write. Reads contacts, proposals, agreements, invoices and payouts. Creates contacts and drafts, publishes proposals, changes live agreements, and edits Terms of Service and service templates.
Works with: Claude.ai and Claude Desktop (documented); any MCP client, per Anchor's integrations page.
Plan requirement: An active Anchor Service Provider account. On Claude.ai, a Pro, Team or Enterprise plan; Free users use Claude Desktop, per Anchor.
Last changed: 2026-05-19: Claude connector help article published
Verification: Verified 21 Oct 2026 by theFinanceStack · confidence: high

What can an agent do with Anchor through MCP?

It reads your Anchor contacts, proposals, agreements, invoices and payouts. It can also create drafts, publish proposals and change live agreements. It cannot charge clients or add credit.

Anchor runs one hosted server. Each user's connection is separate, and Anchor says an agent can query across every client in it. There's no published tool count.

What happens when it writes

Action	What happens
Create a contact or draft	Takes effect when the tool runs. Drafts stay internal until published.
Edit Terms of Service or templates	Takes effect when the tool runs.
Publish a proposal	Sends the proposal to the client. Anchor flags it as significant, so Claude describes the action and waits for you to confirm.
Withdraw	Anchor flags it as significant, so Claude describes the action and waits for you to confirm.
Terminate a service	Anchor flags it as significant, so Claude describes the action and waits for you to confirm.
Add or update services on a live agreement, or change agreement settings such as payment terms	Anchor doesn't document whether these apply at once or go through client approval under the agreement's amendment approval policy. It says amendments to signed agreements use a different flow from editing pending proposals.

Good to know

Anchor doesn't say whether Claude asks before the other writes.

Can

Read contacts, pending and expired proposals, and signed agreements
Read invoices with their accounting sync state, and payouts with fee breakdowns
Read service templates, proposal templates and Terms of Service; export contacts, proposals, drafts and service templates as CSV
Create client contacts
Create and edit proposal drafts: payment and agreement terms, services and packages
Publish, withdraw and republish proposals (flagged for confirmation)
Add or update services on live agreements, terminate a service (flagged), and change agreement settings
Create or update Terms of Service and service templates

Cannot

Move money: charging clients or adding credit must be done in the Anchor app, per Anchor
Connect more than one business per connection (you choose one at sign-in, per Anchor)
Act outside the signed-in user's own Anchor account, per Anchor

What access does it get?

Account-level OAuth access to one Anchor business for the person who signs in; Anchor doesn't publish named scopes, and the server's OAuth metadata advertises a single scope called mcp.

Where	Scopes and permissions (as documented)	Admin requirement
Anchor MCP (remote, OAuth)	Not documented by the vendor as named scopes. Anchor's integrations page says scopes are set per connection and can be narrowed or removed; its help article says access is limited to your own account. Sign-in shows an Anchor login, a business picker and an Allow button. The server's OAuth metadata lists one scope: mcp.	Anchor doesn't document an admin approval step. Each team member connects their own Claude account to their own Anchor login, per Anchor. Claude Team/Enterprise: an Owner adds custom connectors for the organisation.

How do I connect it?

Add https://mcp.app.sayanchor.com/mcp as a custom connector in Claude, sign in to Anchor and click Allow; Anchor documents Claude Desktop and Claude.ai only.

Claude Desktop: open Settings › Connectors, click Add Connector and paste https://mcp.app.sayanchor.com/mcp, then click Add and Connect.
Claude.ai: in a new chat open the + menu › Connectors, search for Anchor or choose Add custom connector with the same URL, then click Connect.
Sign in to Anchor, choose the business if you can access more than one, and click Allow.
In Claude's connector settings, keep write tools set to Needs Approval, as Anchor advises for sensitive tools. Team/Enterprise: an Owner adds the custom connector first.

Anchor says Claude.ai connectors need a Pro, Team or Enterprise plan; Free users can use Claude Desktop. To disconnect in Claude Desktop, per Anchor: Settings › Connectors › Anchor › Disconnect. Removing the connector in Claude may not revoke the OAuth grant on Anchor's side; Anchor doesn't document an Anchor-side revocation page.

What should a finance team watch for?

Contacts, drafts, Terms of Service and templates change straight away, Anchor doesn't say whether live-agreement amendments need client approval, and it documents a confirmation step for only three actions.

Changes to live agreements (adding or updating services, payment terms, the amendment approval policy) can change what clients are billed under. Anchor doesn't say whether the client must approve an amendment, and it flags only publishing, withdrawing and terminating for confirmation.
No tool charges a client or adds credit, per Anchor, but a published proposal or an amended agreement can lead to billing once it takes effect. Review a draft first (Anchor suggests asking to see it) before publishing.
Anchor's integrations page says permissions are scoped per connection and can be narrowed, but neither Anchor page explains how to narrow them or switch off write tools; sign-in shows no scope choice, and the server's OAuth metadata advertises a single scope (mcp). In practice, Claude's per-tool Needs Approval setting is the control you can set; removing the connector revokes access.
Contact details, proposal text and Terms of Service come back as free text. An injected instruction in one of them could push the agent to publish, amend or terminate, so keep human approval on.
One business per connection, and each team member connects separately, per Anchor. Anchor publishes no rate limits or usage caps for the connector.
Anchor says traffic between Claude and the connector is encrypted and advises using a business AI subscription with training on your data turned off. Check Anchor's and your AI provider's terms.

How could finance teams and accounting firms use it?

Reads suit questions about clients, proposals and payouts; writes suit drafting proposals and templates that a person reviews before anything is published or a live agreement changes.

Inside a company

Ask which proposals are pending or expired and which invoices have not synced to the accounting system.
Summarise recent payouts with their fee breakdowns for the month-end cash review.
Export contacts or proposals as CSV for a reconciliation or a pricing review.
Draft a proposal from a service template for a person to review in Anchor before publishing.

At an accounting firm

List clients whose proposals expired without a signature and draft follow-up notes for a partner to send.
Draft a fee change across a package in a proposal draft, and have a partner review it before publishing; create service templates only with Needs Approval on.
Check invoice sync state across every client in the connection before a month-end review.
Have each staff member connect with their own Anchor login, so actions run as that person.

Whatever the use, keep a person approving anything that is published to a client, changes a live agreement or touches billing.

Want Anchor connected to Claude for your team?

We set up scoped connections and a review step before anything changes your books, for a fixed fee.

Book a 30-minute setup call

Change log

Date	Change	Source
2026-10-21	Re-verified: remote URL, OAuth sign-in, read/write tool families, confirmation for publish/withdraw/terminate, no money movement; OAuth metadata advertises one scope (mcp)	help.sayanchor.com/en/articles/15002538-claude-connector
2026-05-19	Anchor publishes its Claude connector help article with the remote URL https://mcp.app.sayanchor.com/mcp	help.sayanchor.com/en/articles/15002538-claude-connector

FAQ

Is this official?

Yes. Anchor hosts the server at mcp.app.sayanchor.com and documents it in its own help centre and integrations page. We found no public Claude directory page for Anchor as of 21 Oct 2026; Anchor's steps cover both searching for it in Claude.ai and adding it as a custom connector.

Is it free?

Anchor doesn't publish a separate MCP charge. You need an active Anchor Service Provider account, and on Claude.ai a Pro, Team or Enterprise plan, per Anchor.

Does it change data in Anchor?

Yes. It can create contacts and drafts, publish proposals, change live agreements and edit Terms of Service and templates. It cannot charge clients or add credit, per Anchor.

Is my data used to train models?

Anchor advises using a business AI subscription and disabling training on your data. Check Anchor's privacy terms and your AI provider's terms before connecting.

Can my accountant use it on my behalf?

Anchor doesn't document access for outside accountants. Each person connects their own Claude account to their own Anchor login, so your accountant would need their own access to your Anchor business.

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.