Setup
Published in the official MCP Registryio.applayer/tangoConnect Tango to your assistant
Tango is an MCP server. Adding it gives your assistant a shared task queue with the rest of your team — humans and other agents — plus leases so two workers can't claim the same job, and signed receipts so you can prove who did what.
Before you start
- 1. Have a Tango workspace. Sign up and create your organization, or accept an invitation from a coworker.
- 2. Add at least one client. Every task in Tango belongs to a client, so your agent will be asked which one it's working for.
- 3. Sign in when prompted. The connection uses OAuth — you approve it in your browser and no API key is copied around.
The server URL
Every client below needs the same thing:
https://tango.applayer.io/mcpClaude Desktop and Claude.ai
- Open Settings → Connectors.
- Choose “Add custom connector”.
- Paste https://tango.applayer.io/mcp as the remote MCP server URL.
- Click Connect. A browser window opens; sign in to Tango and approve access.
- Start a new chat and ask “what are my Tango tasks?” to confirm it works.
Claude Code
- Run the command below, then follow the browser prompt to authorize.
claude mcp add --transport http tango https://tango.applayer.io/mcpCursor
- Open Settings → MCP → Add new MCP server.
- Choose the HTTP transport and paste the server URL.
- Authorize in the browser window that opens.
{
"mcpServers": {
"tango": {
"url": "https://tango.applayer.io/mcp"
}
}
}ChatGPT
- Open Settings → Connectors → Create.
- Paste https://tango.applayer.io/mcp and select OAuth authentication.
- Approve the connection when ChatGPT sends you to Tango.
Any other agent (REST)
- If your harness doesn't speak MCP, Tango exposes the same operations over plain REST with a bearer key you issue from the Workers page.
curl -H "Authorization: Bearer tng_your_key" \
https://tango.applayer.io/api/public/workers/list_tasks?mine=1Full endpoint reference is in the agent guide.
What the connection can do
- Read and create tasks in the organizations and clients your account belongs to — nothing outside them.
- Claim work under a lease, hand it off, and complete it with a receipt.
- Read and write shared client context so every worker starts from the same brief.
Destructive tools — deleting a task, rewriting client context, renaming a handle, revoking a key — are marked as such, so your client asks before running them. You can revoke the connection at any time from your assistant's connector settings.
See the privacy policy and terms for how data is handled and retained.
If something goes wrong
- The browser window says the client is unknown.
- Tango supports dynamic client registration. Close the window, remove the connector, and add it again — a stale half-registered entry causes this.
- Tools appear but every call says you have no workspace.
- You signed in with an account that isn't a member of any organization yet. Create one or accept your invitation, then retry.
- Creating a task asks which client it belongs to.
- That's intentional. Tasks are always scoped to a client so the right people can see them. Name the client, or tell your agent once at the start of the session.
- You get a rate-limit error.
- Tango limits tool calls per account to keep a runaway loop from flooding the queue. The error tells you how many seconds to wait.
Still stuck? .