Claude Integration
Overview
AI Integration lets you connect AI tools like Claude to 3Min API, so you can run your endpoints with the same kind of casual chat you already use. Behind the scenes it speaks MCP (Model Context Protocol), an open standard. Once the AI is connected to the 3Min API server, it picks the right tool from the ones we expose and answers your question.
The benefit is concrete. No code is needed to create a new endpoint, search yesterday's call logs, invite a collaborator, or check this month's usage. Skip the dashboard clicks — "Summarize the 5 failed calls from last week" is enough.
3Min API supports two authentication styles. ChatGPT and Claude use OAuth (sign in with your 3Min API account), so there's no API key to manage. CLI/IDE tools like Claude Code or Cursor use API keys that you store locally. This page walks you through connecting from Claude's Connectors directory.
What you can do
The 3Min API MCP server exposes the tools below. The AI looks at your request and picks the right one. Every action is scoped to your own account — other users' resources are never accessible.
Read tools
| Tool | Description | Scope |
|---|---|---|
help |
Returns the 3Min API service guide by topic | Public |
endpoint_list |
List endpoints | Your own |
endpoint_get |
View one endpoint's details | Your own |
logs (lookup / search) |
Single-record lookup, full-text search | Your own |
stats |
Monthly / daily API usage statistics | Your own |
subscription |
Current plan, usage, and billing info | Your account |
collaboration_key_list |
List collaboration keys | Your own |
collaborator_invite_list |
List collaborator invitations | Your own |
record_get |
View one stored record | Your own |
record_list |
List recent records (newest first) | Your own |
record_search |
Search records by text (last 30 days) | Your own |
record_poll |
Fetch records that arrived since a point (oldest first) | Your own |
Create / Update / Deploy tools
| Tool | Description | Scope |
|---|---|---|
endpoint_create |
Create a new endpoint | Your account |
endpoint_update |
Update field definitions and webhooks | Your own |
endpoint_deploy |
Deploy sandbox config to production | Your own |
collaboration_key_create |
Create a new collaboration key | Your own |
collaboration_key_set_permissions |
Update CRUD permissions for a collaboration key | Your own |
collaborator_invite |
Send a collaborator invitation email | Your own |
Execution tools
| Tool | Description | Scope |
|---|---|---|
record_create |
Store a new record in your endpoint (via the gateway) | Your own |
record_update |
Replace a stored record as a whole | Your own |
record_delete |
Delete a stored record | Your own |
record_deleteremoves one stored record and cannot be undone. It does not delete the endpoint itself — that is dashboard-only.
Task tools
| Tool | Description | Scope |
|---|---|---|
worker_list |
Names, descriptions and kind (public · local) of your workers (no URLs or secrets) |
Your own |
task_create |
Creates a task from a worker name and input (JSON object, up to 100 KB). repeat runs it on an interval (local workers only) |
Your own |
task_list |
Recent tasks (without result bodies) | Your own |
task_get |
One task's status, message, delivery, and result or error |
Your own |
task_cancel |
Cancels running tasks (up to 100) | Your own |
task_result_describe |
Structure of a result saved on your PC — paths, types and ranges | Your own |
task_result_query |
Read-only SQL over results saved on your PC; only the answer comes back | Your own |
task_result_read |
A raw slice of a result saved on your PC | Your own |
A worker must exist first: a public worker is registered in the dashboard (Tasks), a local worker is a file on your PC run by the CLI (Local workers (CLI)).
Safety: actions intentionally not exposed to AI
The actions below are deliberately excluded from MCP. We don't want an AI mistake or accidental call to wipe data or trigger billing surprises. When you need to do these, sign in to https://3minapi.com directly.
| Excluded action | Where to perform it |
|---|---|
| Delete endpoint | Dashboard → APIs → Endpoint detail |
| Delete / deactivate collaboration key, regenerate API key | Dashboard → APIs → Endpoint detail → Collaboration keys |
| Revoke collaborator invitation | Dashboard → APIs → Endpoint detail → Collaborators |
| Change / cancel plan | Dashboard → Settings → Subscription |
| Regenerate / delete MCP API key | Dashboard → Settings → AI Integration → CLI / IDE |
| Delete account | Dashboard → Settings → Profile |
| Register / edit / delete a public task worker, view or rotate its secrets | Dashboard → Tasks → Workers |
| Add a host for the local CLI, rotate its token, delete it | Dashboard → Tasks → Local (Local workers (CLI)) |
How to connect
3Min API is listed in the Claude Connectors directory, so you search for it and click Connect — there's no server URL to type in. Authentication uses the OAuth flow: sign in with your 3Min API account and you're done. No API key to enter manually.
In a hurry? Open the 3Min API listing in Claude and click
Connect.
Step 1 — Open Claude Connectors
Open Claude at https://claude.ai, then go to Settings > Connectors.
Step 2 — Search for 3minapi
Type 3minapi in the search box and select 3Min API from the results.
The connector page carries a Community label, with a note that community connectors have been reviewed automatically and may not yet meet the quality tier of verified connectors. That label applies to every third-party connector in the directory.
Step 3 — Click Connect, then sign in via OAuth
When you click Connect, the 3Min API login page opens in a new window. Sign in with your usual 3Min API account and permissions are granted automatically. No API key is entered manually.
Step 4 — Use it in a new chat
Open a new chat and start using it.
Directory connectors are available on every Claude plan, including Free. Once connected on the web, 3Min API also works in the Claude desktop and mobile apps.
Example prompts
These plain-language prompts work well:
- "Show me my API endpoint list."
- "Create an endpoint for customer inquiries with name, email, and message fields."
- "Summarize the 5 failed calls from yesterday."
- "How much have I used this month, through yesterday?"
- "Invite chris@example.com as a collaborator on the user-signup endpoint."
For requests that create, update, or deploy something, the AI confirms with you before going through. Read the response carefully so unintended changes don't slip in.
Common pitfalls
I clicked Connect but no tools showed up
Claude's connector cache occasionally takes a moment to refresh. Go to Settings > Connectors, disconnect 3Min API and reconnect — the tool list should appear cleanly in a new chat.
Claude warns that the connector hasn't been reviewed in depth
That's the Community label, and it's expected. Anthropic verifies directory connectors at two levels: connectors it has reviewed in depth get a checkmark, and connectors that pass its automated checks are labeled Community. 3Min API is in the second group. Once connected, a community connector works exactly like a verified one.
What if someone else's data gets mixed in?
It can't. Every tool only touches resources owned by the OAuth-signed-in account — other users' endpoints and logs are never visible.
The AI deleted my endpoint!
It can't. Destructive actions are excluded from MCP, so no matter how the AI tries, your data stays put. To actually delete something, sign in to https://3minapi.com.
Does Claude Code (terminal) connect the same way?
No. Claude web / desktop / mobile connects through the OAuth-based directory connector, while Claude Code (CLI) and Cursor and similar local tools use the API key flow. For those, see the MCP integration (CLI / IDE) guide.