Connect AnythingMCP to Claude: One URL for All Your Business APIs

What you get

One connector, https://cloud.anythingmcp.com/mcp, that gives Claude the tools of every API you have set up in AnythingMCP Cloud — ready-made connectors from the marketplace (weclapp, DATEV, Etsy, Shopware, Billbee, Sendcloud, Telegram, Deutsche Bahn, Bundesbank and 180 more) or any REST, SOAP, GraphQL or SQL API you import yourself.

You sign in once. During sign-in you choose which of your MCP servers Claude may use, and you can change that choice any time without reconnecting.

This guide covers Claude on the web, Claude Desktop, Claude Mobile and Claude Code. If you prefer to expose a single server under its own URL, see the per-server URL at the end.

Before you start

• An AnythingMCP Cloud account — start a free 7-day trial. Self-hosters: your own base URL replaces cloud.anythingmcp.com everywhere below.
• At least one connector in your workspace. New connectors are attached to your workspace's default MCP server automatically; you can move them between servers under MCP Servers.
• Any Claude plan. Free accounts can add one custom connector; on Team and Enterprise only Owners can add one, and members then connect to it.

Step 1: Add the connector in Claude

Option A: from the Claude Directory (fastest)

AnythingMCP is listed in Anthropic's official connector directory, so there is no URL to type.

1. Open AnythingMCP in the Claude Directory. Or, in Claude, open Customize → Connectors, click Browse connectors and search for AnythingMCP.
2. Click Connect. Claude opens the AnythingMCP sign-in described in Step 2.

Option B: as a custom connector (Claude web and Desktop)

Use this for a self-hosted AnythingMCP: the directory listing connects AnythingMCP Cloud, not your own address.

1. Open Customize → Connectors.
2. Click +, then Add custom connector.
3. Name: AnythingMCP. Remote MCP server URL: https://cloud.anythingmcp.com/mcp (or your own base URL followed by /mcp).
4. Click Add, then Connect.

Claude Code

claude mcp add --transport http anythingmcp https://cloud.anythingmcp.com/mcp

Then, inside a session, run /mcp and choose Authenticate next to anythingmcp.

Claude Mobile picks up connectors you added on the web; there is nothing to configure on the phone.

Step 2: Sign in and choose what Claude may reach

Claude opens cloud.anythingmcp.com in your browser.

1. Sign in with your AnythingMCP e-mail and password. On a self-hosted install, where Claude opens your own AnythingMCP address, the sign-in can also go through your company's SSO if an admin has set it up.
2. Review the request. The page names the application asking for access (Claude) and where it will be sent back to. Approve it.
3. Pick your MCP servers. If you belong to one workspace with one server, this step is skipped — that server is granted and you are done. Otherwise you see every workspace you are a member of, and under each one its MCP servers. Tick the servers Claude may use, or tick a whole workspace to include connectors that are not attached to any server.

You are returned to Claude. The connector shows as connected and its tools appear in the tools menu of every new chat.

Claude only ever sees the tools of the servers you granted. Other workspaces, other tenants, other users' connectors are not reachable through this connector — the grant is checked against your current membership on every single request.

Step 3: Ask

Some prompts that work out of the box with marketplace connectors:

• "When is the next train from Freiburg to Basel, and is it on time?" — Deutsche Bahn
• "Is this EU VAT number valid, and which company is it registered to?" — VIES
• "What was the EUR/USD reference rate on the first of each month this year?" — Bundesbank
• "Show my open weclapp quotations older than two weeks." — weclapp
• "Which Etsy listings sold last week, and what was the total?" — Etsy
• "Where is DHL parcel 0034… right now?" — DHL

Claude asks before running a tool that writes or deletes; read-only tools run without a prompt.

Changing your mind

Open Settings → Connections in AnythingMCP Cloud. Every AI client you have connected is listed with the servers it may reach. You can:

• change the servers — takes effect on the client's very next request, no reconnect needed;
• revoke the connection — the client keeps its token but reaches nothing until you grant again.

Why this exists: Claude keeps the token it was given for a day, and the refresh token for thirty, and reuses them without asking. "Disconnect and reconnect" in Claude therefore does not reliably bring the server picker back. The Connections page does.

For IT administrators

• Endpoint: https://cloud.anythingmcp.com/mcp (Streamable HTTP). Authorization-server metadata at /.well-known/oauth-authorization-server, protected-resource metadata at /.well-known/oauth-protected-resource/mcp.
• Authorization: OAuth 2.1 with PKCE (S256) and dynamic client registration. Access tokens live one day, refresh tokens thirty. Tokens are bound to a user; what they reach is the grant recorded for that user and client, re-validated on each request.
• Tenant isolation: connectors, credentials and tools belong to a workspace. A user can grant only servers of workspaces they are a member of; leaving a workspace ends access on the next request.
• Credentials: API keys and OAuth tokens for your systems are stored encrypted in your workspace and are never shown to Claude. Claude receives tool results, not credentials.
• Audit: every tool call is logged per workspace with caller, tool, duration and outcome (Analytics). Grants, changes and revocations are security events.
• Hosting: Frankfurt, Germany. Or self-host under AGPL and keep everything on your own infrastructure.
• SSO/SCIM (self-hosted only): single sign-on with Entra ID, Google, Okta, Auth0, GitHub or any OIDC provider, and SCIM provisioning with Entra ID, come with the self-hosted Business edition, which an admin can try for 30 days under Settings → License. They are not available on AnythingMCP Cloud. See the SSO guide and SCIM with Entra ID.

One server, one URL

Every MCP server also has its own address: https://cloud.anythingmcp.com/mcp/<server-id>, shown under MCP Servers → Quick Connect. Adding that URL as a custom connector connects exactly that server, with no picker. Use it when you want separate Claude connectors for separate systems — one for finance, one for logistics — each with its own name in the tools menu.

Troubleshooting

Claude connected but shows no tools. Open Settings → Connections in AnythingMCP and check what this connection is allowed to reach; a revoked grant or a server with no enabled tools both look like this from Claude's side.

Claude did not ask me to sign in. It already held a valid token from an earlier connection, so it reused it. The servers granted then still apply; change them on the Connections page.

A tool fails with "cannot reach host". The API behind the connector rejected the call or is not reachable from the cloud. Open the connector in AnythingMCP and use Test on that tool — the error there names the cause.

I'm on the free Claude plan. Free accounts can add one custom connector. If you already have one, remove it or upgrade to add AnythingMCP. Claude Code works on any plan that includes it.