MCP for agents
Connect any Twotic API to Claude, ChatGPT, Cursor or another MCP client — with a one-click OAuth sign-in, or an API key if you prefer.
Every published API on Twotic is also a hosted Model Context Protocol server. Point an MCP client at it and the API's endpoints appear as callable tools — no integration code.
The endpoint
One server carries the whole catalogue. Connect it once and every API's endpoints are available as tools, including any added later.
https://www.twotic.dev/api/mcpPrefer a single API? Each one also has its own server, which is the better choice when an agent should have exactly one capability and nothing else:
https://www.twotic.dev/api/mcp/<api-slug>You can connect it two ways.
Sign in with Twotic (recommended)
Paste the URL into your client and it walks you through a normal sign-in page — the same flow as connecting any app to Google or GitHub. No key to find, copy, or keep safe.
This is the better option even if you are comfortable with API keys:
- Access expires after an hour and renews itself quietly while the app is connected. A pasted key stays valid until someone notices it leaked.
- You can revoke one app from your dashboard without touching your key or breaking anything else.
- The key never ends up sitting in a config file on disk.
Your client registers itself automatically the first time it connects. There is nothing to set up here first.
Or use an API key
Some clients do not support sign-in yet. For those, send your key as a header:
{
"mcpServers": {
"web-extract": {
"type": "http",
"url": "https://www.twotic.dev/api/mcp/web-extract",
"headers": { "Authorization": "Bearer tk_live_your_key" }
}
}
}Create a key at your keys.
Connecting specific clients
Pick your client. Every step, URL and config block below changes to match it.
In claude.ai and the Claude desktop app
- 1Open Settings, then Connectors.
- 2Choose Add custom connector.
- 3Paste the server URL below and confirm.
- 4A Twotic sign-in page opens. Approve the connection.
- 5Start a new conversation. The tools are available there.
Server URL
https://www.twotic.dev/api/mcpSigns you in through Twotic. Access expires hourly and renews itself, and you can revoke this one app without touching your API keys.
Once connected, the tools are named <api>_<endpoint>. One connection exposes every API in the catalogue. Calls are metered exactly like an HTTP request, against the same allowance and balance.
Every published API has its own server, and its own copy of these instructions with the real slug already filled in. You will find it in the Connect an AI agent panel on any API page.
What it costs
MCP calls run through the same gateway as HTTP requests. Same free monthly allowance, same per-request price, same entry in your usage log, same automatic refund when a call fails on our side. There is no agent tier and no markup.
Your prepaid balance is also the ceiling. An agent cannot spend credit you have not added — once it runs out, calls stop rather than accruing a bill.
Managing connections
Connected apps are listed in your dashboard, with what each one has access to and when it was last used. Revoking takes effect immediately and does not affect your API keys or any other app.
Tool names
Tools are named <api-slug>_<endpoint-slug>. The prefix is deliberate: agents often have several servers connected at once, and a bare search or get_user colliding across two of them turns the ambiguity into the model's problem.