For teams using Claude, Cursor and Codex

Your team's private MCP server. Built by your agent.

Connect Claude to any API in minutes. Your agent writes and tests the tools, your whole team uses them in Claude, Cursor or Codex, and you see the code, every call and who made it. Not a public connector: a backend you control. Free for up to 3 people.

See every call · Read every tool's code · Choose who has access · Keys encrypted and write-only · Security

Terminal · Claude Code
$ claude mcp add --transport http acme-admin https://rapid-mcp.com/mcp/…/stream
Added HTTP MCP server acme-admin
$ claude
/mcp → acme-admin → Authenticate … signed in with RapidMCP ✓
> Build tools on our admin API (api.acme.com) so the team can look up a customer and their invoices.
● rapidmcp_get_server()
● rapidmcp_set_server_info(name: "Acme Admin")
● rapidmcp_upsert_tool(get_customer)
● rapidmcp_request_secret(ADMIN_API_TOKEN) → link for you
✓ rapidmcp_test_tool(get_customer) → Globex Ltd, Pro plan
● rapidmcp_upsert_tool(list_invoices)
✓ rapidmcp_test_tool(list_invoices) → 3 invoices, 1 overdue
Both tools are live. Invite your team from the Connect tab.
5 teammates joined · each signed in as themselves
RapidMCP
Acme Admin
Live
get_customer
Look up a customer by email or ID: plan, status and owner.
async function code(inputs) { … }
list_invoices
A customer's recent invoices, with amounts and what's overdue.
async function code(inputs) { … }
People using it
6
Tool calls today
16
ADMIN_API_TOKEN · encrypted, nobody can read it back

The tools no connector covers

Official connectors cover the big apps. Your admin API, your reports and the niche tools your team lives in need their own, shared safely with everyone who needs them.

Support

Look up any customer

Plan, status, invoices and recent errors from your admin API, without giving every agent a production token.

Sales & RevOps

Your niche CRM and billing tools

The systems no official connector covers, usable by the whole team from Claude in plain English.

Engineering

Internal services, safely

Feature flags, deploy status and reporting queries, with drafts, publishing and rollback when the tools change.

Agencies

One MCP per client

Each client's API as its own MCP, with only that client's team on it and the keys kept out of everyone's laptops.

How it works

1

Build the tools once

Add one URL to your agent and ask for tools on your internal or niche APIs. Your agent writes and tests them; your keys go into RapidMCP, never into a chat.

2

Invite your team

Send a join link. Teammates add the MCP to Claude, Cursor, Codex or VS Code and sign in once. They get the tools, never the keys.

3

Stay in control

Choose who can use each MCP, see every call and change, publish when you're ready and roll back in seconds.

Your teammates don't need to be technical

One person sets the tools up. Everyone else just adds them to the agent they already use: Claude on the web, desktop or phone works as well as Claude Code.

  1. 1
    Open the invite link
    They create a free account, or sign in.
  2. 2
    Add the MCP to their agent
    One command in Claude Code, or paste the URL into Claude, Cursor or VS Code.
  3. 3
    Sign in once and ask
    The tools just work. No keys, no config files.

Built to hold your production keys

Share the tools, never the keys. Need it inside your own network? Self-host it.

  • Keys encrypted at rest and write-only: nobody can read them back
  • Only the tools that need a key ever get it
  • Every teammate signs in as themselves (OAuth 2.1)
  • Revoke anyone in one click; every call and change is logged

How we protect your keys

Questions team leads ask

Do my teammates need the API keys?

No. Keys are stored in RapidMCP, encrypted and write-only, and only the tools that need a key get it while they run. Teammates add one URL to their agent and sign in with their own RapidMCP account; they never see or handle the keys.

Which agents does my team need?

Any MCP client: Claude (web, desktop and mobile), Claude Code, Codex, Cursor and VS Code. Everyone uses the same MCP URL in whichever agent they already use.

What happens when someone leaves the team?

Remove them from the project, or revoke their access to the MCP. Their sign-in stops working straight away, and because they never had the keys there's nothing to rotate.

Does my API have to be on the public internet?

On RapidMCP cloud, tools call your API from our servers, so it needs to be reachable over the internet (protected by its own key or token, which stays in RapidMCP). For APIs that only exist inside your network, run RapidMCP self-hosted.

Can I see who used what?

Yes. Every tool call and every change (who saved, published or rolled back a tool, who added a secret) shows up in the MCP's live activity log.

What does it cost, and what counts as a person?

Free for up to 3 people, then Team at $49 a month for up to 25 people. Tool calls are included (10,000 a month on Free, 250,000 on Team). A person is anyone who can use your MCPs, including you.

More questions

Give your team its tools this week

Build the first tool on your API in minutes, then invite your team with one link. Free for up to 3 people; Team is $49 a month for up to 25.