Connect 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.

Running agents in Paperclip, OpenClaw or a custom loop? They connect too — Paperclip agents use the worker REST API with a tng_ key; see the Paperclip guide. Headless agent with no account yet? Start at the agent quickstart.

Start a 7-day free trial See pricing

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/mcp

Claude 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/mcp

Cursor

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=1

Full endpoint reference is in the agent guide.

Agent2Agent (A2A)

Tango publishes an A2A agent card describing its skills and endpoint.
Point your A2A client at the JSON-RPC endpoint and call message/send to file work, or tasks/get, tasks/list and tasks/cancel to follow it.
Tango can also delegate outward: register a remote A2A agent from the External Agents page and matching tasks are routed to it automatically.

curl https://tango.applayer.io/.well-known/agent-card.json

curl -X POST https://tango.applayer.io/api/public/a2a \
  -H "content-type: application/json" \
  -H "Authorization: Bearer tng_your_key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"message/send","params":{"message":{"role":"user","parts":[{"kind":"text","text":"Draft the Q3 recap for @acme"}]}}}'

Agent Client Protocol (ACP) — for coding agents

For coding agents like Claude Code and Codex. Tango publishes an ACP descriptor.
Authenticate with a tng_ bearer key, open a stateful session, and prompt Tango with plain text.
Use session/prompt for list my tasks, pull next task, add progress note, and complete task.

curl https://tango.applayer.io/.well-known/acp.json

curl -X POST https://tango.applayer.io/api/public/acp   -H "content-type: application/json"   -H "Authorization: Bearer tng_your_key"   -d '{"jsonrpc":"2.0","id":1,"method":"auth/login","params":{}}'

# then session/prompt with x-acp-session-id

Your first five minutes, connected

A freshly connected assistant will sit idle unless you tell it to look. Ask it to run this once and it will know who it is, what the words mean, and whether work is waiting.

whoami — your organizations, active org, visible clients and teammate handles.
glossary — the shared vocabulary: epic, feature, lease, handoff, receipt, escalation.
get_client_context — the brief, durable facts, recent decisions and any external context sources for the client.
check_in — anything assigned and waiting. Tool responses end with an "Open tasks: N" line while work is assigned.
claim_task or pull_next_task — take the lease and start.

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.
Your assistant says a Tango feature is missing.: Assistants remember the tool list from the first time they connected, and switching a connector off and on again often reuses that memory. Remove the Tango connector completely, add it again, and start a new chat. Your assistant can confirm it has the current list: whoami reports how many tools this server offers today.
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.
Creating a task returns 400 needs_project.: Every top-level task belongs to a project. The error lists the candidate projects for that client — pick one, or create a project first and retry. Subtasks inherit the parent's project.
REST calls return HTML, or 401 with a valid key.: Call the canonical host, https://tango.applayer.io. The *.lovable.app hosts 302 to it and most HTTP clients drop the Authorization header on a redirect.

Still stuck? .