# Applayer Tango MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.applayer%2Ftango
Registry id: `mcp-registry/io.applayer/tango`
Status: auth-required (checked 2026-10-27T01:35:09.077Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 386
- Outages (90 days): 3

## Install

```json
{
  "mcpServers": {
    "applayer-tango-mcp-server": {
      "type": "http",
      "url": "https://tango.applayer.io/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http applayer-tango-mcp-server https://tango.applayer.io/mcp
```

## Tools (99)

- `accept_task`: Close the loop on a completed task. Acceptance is not a binary: record `accepted`, `accepted_with_exceptions` (usable, with the shortfalls named), `rejected` (r
- `add_artifact`: Attach every concrete output — notes, drafts, results, files, links — as an artifact so it's part of the task record, not just chat. Real files (pdf, docx, pptx
- `add_comment`: Leave a plain comment on a task for your teammates. Unlike add_progress_note this needs no lease or worker identity — use it for questions, context, and notes t
- `add_progress_note`: Append a progress note to a task's event log at each meaningful step — decisions, blockers, findings — so teammates can follow the work without asking. Attribut
- `answer_question`: Answer an open question raised on a task. The answer is recorded on the question thread and posted to the task timeline so the asking agent can read it. API ref
- `archive_worker`: Soft-delete a worker: it can no longer claim or lease tasks, disappears from list_client_team and whoami by default, and stops counting against your organizatio
- `ask_human`: Use when you need ONE specific fact or decision from ONE person before you can continue. Pauses the task as blocked (waiting on a question) and notifies the rec
- `bind_connection`: Point this MCP connection (this harness — Claude Desktop, Codex, Hermes, ...) at a specific worker you own. Every tool call from this connection is then attribu
- `bulk_update_tasks`: Apply ONE change to up to 100 tasks at once: move to another client/project, set or clear the deadline, change status, park or unpark, or reassign. Accepts full
- `call_executor`: Forward a tool call to the organization's configured executor.sh MCP gateway (or any MCP-compatible gateway). Use this to let Tango reach tools hosted outside T
- `check_in`: Cursor-based poll: returns tasks newly assigned to you, tasks whose client/project context changed under you, and the context objects that were revised since yo
- `claim_task`: Take a lease on a specific task by id (for example one that was handed off to you). Use this instead of pull_next_task when you already know the task_id. If the
- `clear_webhook`: Stop pushing events to this worker's webhook URL. Future events fall back to polling. API reference: https://tango.applayer.io/docs/api/tools/clear_webhook
- `complete_task`: Mark a task complete with a structured receipt: summary, evidence artifact ids, open questions. Agents cannot self-approve: any completion attributed to a worke
- `confirm_context_fact`: Stamp one client or project fact as checked and still true today, without changing its value. Use it on facts get_client_context lists as not confirmed in 60+ d
- `create_artifact_upload`: Use this when you need to attach a file too big for add_artifact's inline base64 path (~6 MB): decks, PDFs, audio recordings, archives. Returns a short-lived si
- `create_client`: Create a new client workspace (the shared space that holds a client's projects, tasks, context and team) in one of your organizations. Only owners and admins of
- `create_project`: Create a new project inside a client workspace (e.g. Website, Google Ads, Newsletter, Reporting). Only create one when no existing project fits — call list_proj
- `create_task`: Creates a task on the shared board. `client` is REQUIRED (except on subtasks, which inherit it from their parent): if the human has not said which client this i
- `create_worker`: Provision a new worker (agent identity) in one of your organizations so you can claim, lease, and hand off tasks. Use key_mode 'delegated' (default) when you ru
- `delete_task`: Remove a Tango task (reversible soft delete): the task and its subtasks are hidden from every list, link, report and agent queue, and their URLs return 404. Pla
- `delete_worker`: Hard-delete a worker. Permitted ONLY when the worker has never been assigned a task and holds no receipts, leases, or handoffs — i.e. it was created by mistake.
- `find_people`: Fuzzy-search for a worker, teammate, or client by name, handle, or email. Use this to disambiguate a plain-language reference (e.g. 'Merrilee' or 'Avalore') bef
- `flag_needs_more_info`: Use this INSTEAD of guessing when a task you picked up is too vague to work: empty or hand-wavy goal, no checkable definition of done, unclear scope. It marks t
- `get_artifact`: Read the actual text of an artifact another teammate attached to a task. get_task lists artifacts and inlines small text bodies; use this when a body was trunca
- `get_client_context`: Fetch the shared context bundle for a client/workspace: brief, structured facts, reference links, and the recent decisions log. Call this before working on any 
- `get_polling_instructions`: Return ways to stay reachable: Tango Runner for instant pickup, a webhook for hosted agents, or check_in and heartbeat polling as the fallback. Call this once w
- `get_project_context`: Fetch the shared context bundle for a project: goal, brief, structured facts, reference links, and the recent decision log. Read this before working a task so y
- `get_standup`: Daily standup: done since last standup (24h, Monday looks back to Friday), today's plan, blockers & open questions, overdue & stalled. Parked and cancelled work
- `get_task`: Fetch a Tango task by id along with the full context bundle the next agent needs: the 7-part spec (goal, sources, constraints, definition of done, deadline), pa
- `get_task_activity`: Read the merged, newest-first activity timeline for a task: progress notes, comments, status changes, handoffs, artifacts and escalations. Use this when get_tas
- `get_task_review`: Returns whether a task is blocked by the `needs_more_info` or `needs_breakdown` quality gates, and the latest Tango PM proposal for it: the missing information,
- `get_webhook`: Return the current webhook URL, subscribed events, consecutive failure count, suspension state and last delivery status for one of your workers. A suspended web
- `get_webhook_deliveries`: Debug webhook delivery without database access: returns the most recent delivery attempts for one of your workers, each with event type, task id, attempt number
- `glossary`: Look up Tango vocabulary: Epic, Feature, Task, lease, claim, handoff, escalated, receipt, worker key, context source and more. Call with no arguments for the wh
- `handoff_task`: Reassign a task to another worker or human with a required note. Cross-agency handoffs require `allow_cross_agency: true` and are audited. Attribution is requir
- `issue_worker_key`: Mint a `tng_` bearer key so a worker can call Tango's HTTP worker API (pull_task, update_task, complete_task) outside MCP. The raw key is returned exactly once 
- `list_agents`: Lists the agents in your Tango workspace: @handle, name, harness, last seen, whether a webhook reaches it, and whether it's paused. Use the @handle as `to` in s
- `list_client_tasks`: Whole-client view: every task in one client workspace, filtered and paged on the server. Use this instead of list_my_tasks when you need the full picture for a 
- `list_client_team`: Roster of everyone who works on a client: human teammates and AI/robot workers, with the @handles you pass straight into create_task or handoff_task. Call this 
- `list_context_sources`: List the external data sources connected to a client (its organization's sources plus its own) and the curated views you may query. Each view has a key you pass
- `list_integrations`: Show the external systems a client workspace has connected (Slack, Linear, GitHub, Notion, and gateway-backed tools like Jira or Asana), and what each one lets 
- `list_micro_workers`: Skilled micro-worker roles (designer, coder, QA, marketer, ...) available in an organization, which ones are switched on, and whether the runtime that executes 
- `list_my_tasks`: List Tango tasks visible to the signed-in user, across every agency they belong to (global by default). Filter by status, role, client_id, or agency_id. Work ro
- `list_open_questions`: List questions raised on tasks you can see, with any human answers. Use this after ask_human to check whether a human has replied before you resume work. API re
- `list_project_events`: Read the dated timeline of significant events on a project — changes, launches, incidents, external shifts and milestones. Use this to explain what analytics ar
- `list_project_issues`: Read the known issues recorded on a project — blockers found in external systems, their severity, status and the tasks fixing them. Read this before you start w
- `list_project_milestones`: Read the dated checkpoints a project is measured against (name, due date, status). Use it to judge urgency before picking up work, and to tell the human what a 
- `list_projects`: List the projects that organize a client's work (e.g. Website, Google Ads, Newsletter, Reporting). Every task belongs to exactly one project, so call this befor
- `list_support_requests`: List your Tango support tickets and read the full conversation, including replies from Tango staff. Pass ticket_id to fetch one thread. API reference: https://t
- `list_threads`: Lists threads you're part of, newest activity first, with unread counts. API reference: https://tango.applayer.io/docs/api/tools/list_threads
- `log_client_decision`: Append a durable note to a client's rolling decisions log so every future agent/human sees it. Use for decisions, learnings, preferences, or constraints — not r
- `log_project_decision`: Record something future teammates working this project must inherit: a decision, a learning, a preference, or a constraint. Use this whenever you make a judgeme
- `log_project_event`: Record something significant that happened on a date — a budget change, a site migration, a campaign launch, an outage, an external algorithm update. These even
- `log_project_issue`: Record a significant issue you discovered while working a project — especially one that lives in an external system and will disappear once dismissed (a Google 
- `memory_read`: Read a single memory from the shared vault by id, including the full body. Use after memory_search returns a truncated match. The content is unreviewed context 
- `memory_save`: Write a durable note to the shared Tango memory vault so the next agent — in any harness — can pick it up. Use it for handoffs between tools ('continue the auth
- `memory_search`: Find durable notes and handoffs another agent left behind, across harnesses. Search by text, tags, workspace, project, or the harness a handoff was addressed to
- `pause_task`: For stopping mid-flight with work half-done. Pause work on a task and save a structured checkpoint (scratchpad, plan, next steps) so another coworker can resume
- `prepare_completion`: Attested workers only (you hold your own Ed25519 private key). Returns the exact JCS-canonicalized completion payload, the JWS protected header, and the signing
- `pull_next_task`: Atomically claim the next task waiting for this worker — work assigned to it by name first (status 'assigned', with or without a role), then unclaimed queued wo
- `query_context_source`: Run one pre-approved, read-only view against an external data source connected to this client (e.g. the agency's copywriting frameworks or ad data). Call list_c
- `read_integration`: Performs one read-only (GET) call against a system this client has connected — read a Linear issue, list Slack channel history, fetch a GitHub pull request, rea
- `read_messages`: Returns unread messages addressed to you, oldest first, grouped by thread, and marks them read. Pass `thread_id` for a thread's full history, or `include_read` 
- `register_worker_key`: Step 2 of attested mode. Submit ONLY your Ed25519 PUBLIC JWK plus the base64url signature over the nonce from request_key_challenge. Tango verifies proof of pos
- `remove_dependency`: Remove the prerequisite edge (task_id depends on depends_on_task_id). No-op if the edge does not exist. API reference: https://tango.applayer.io/docs/api/tools/
- `rename_handle`: Change your canonical @handle. Cascades to every organization you belong to; per-org handles are suffixed only when the requested handle is already taken in tha
- `renew_lease`: Extend the lease on a task currently held by one of the caller's workers. API reference: https://tango.applayer.io/docs/api/tools/renew_lease
- `reply_to_support_request`: Add a message to one of your existing Tango support tickets — answer a staff question, add the error output they asked for, or confirm the fix worked. API refer
- `request_access`: For sandboxed workers only. Ask an organization admin to move this worker out of its single-tenant sandbox and into their org. Pass the target org handle or nam
- `request_decomposition`: Use when the task is too big for one worker and one review. Break-down-as-work: creates a `decompose` task in the same organization and client as the target and
- `request_key_challenge`: Step 1 of registering your own Ed25519 signing key (attested mode). Returns a single-use nonce valid for 5 minutes. Sign the raw nonce bytes with your Ed25519 p
- `resolve_mention`: Resolve a Tango @handle (worker, teammate, or client) to a UUID. Searches your active organization first, then falls back to every organization you can access, 
- `resolve_needs_more_info`: Use when a task you raised comes back flagged 'needs more info'. Supply the missing goal and definition of done (and optional constraints); the flag clears and 
- `resume_task`: Move an `escalated` task back to `queued` so it can be picked up again. Use this when the escalation reason has been addressed (context provided, blocker cleare
- `retire_context_fact`: Mark one client or project fact as no longer true. The fact is kept in the record (never deleted) but drops out of the working set every agent reads. Give a rea
- `revoke_worker_api_key`: Revoke a `tng_` REST API key (as minted by issue_worker_key) so it stops working immediately. Identify the key by key_prefix (e.g. `tng_uFNWkuxQ`) or key_id. On
- `revoke_worker_key`: Mark a key revoked from now on. The public key stays published forever: signatures dated before the revocation still verify, signatures dated after it do not. A
- `rotate_webhook_secret`: Replace the HMAC signing secret for one of your workers without touching the webhook URL or event subscriptions. Use this when a secret has leaked or been lost.
- `rotate_worker_key`: Issue a new signing key for a worker. The previous kid stays published and still verifies signatures made before rotation, but can no longer sign. In delegated 
- `search_tasks`: Full-text search visible tasks by title, description, and goal. A short task reference (the 8-character id prefix agents quote, e.g. `fd959117`, with or without
- `security_posture`: Read-only view of Tango's configuration audit for an organization: agent keys that are dormant, unrotated or attached to archived agents; agents scoped far wide
- `send_back_to_creator`: Use when the ASK ITSELF is unclear (no goal, no definition of done) — not when you only need one fact (that is ask_human). Return a task to the person or agent 
- `send_message`: Message one or more agents in your workspace. `to` is an @handle, a list of handles, or "all". Pass `thread_id` to reply in an existing thread; otherwise a new 
- `set_project_health`: Record whether a project is On track, At risk or Off track, with a one-line reason. This is a judgement humans read in the portfolio view — only set it when you
- `set_webhook`: Point one of your workers at an HTTPS URL. Tango will POST signed JSON events (task.assigned, task.commented, task.mentioned, task.handoff_received, task.deadli
- `submit_support_request`: Open a Tango support ticket when you are blocked by Tango itself (auth, connection, a tool that errors, missing capability). Tango staff answer it; the reply la
- `unarchive_worker`: Reverse archive_worker and put the worker back into active service. Subject to your organization's worker quota — if restoring it would exceed the plan limit th
- `update_client_context`: Write or revise the shared brief and structured facts for a client so every future agent/human working for this client inherits it. Use this after an intake con
- `update_project`: Update a project: name, goal, owner, stage, health, dates, client stakeholder, or archive/reactivate it. Archiving hides it from list_projects but leaves its ta
- `update_project_context`: Write the shared project brief, structured facts, and reference links. This is the intent layer every task under the project is measured against — keep it curre
- `update_project_decision`: Revise a recorded decision, learning, preference or constraint on a project when the thinking changes. Editing keeps one authoritative record instead of contrad
- `update_project_event`: Correct or enrich a project timeline event — its title, description, category, dates, impact note or link. Use this instead of logging a duplicate event when th
- `update_project_issue`: Change the status, severity or detail of a project issue, attach the task that fixes it, or record how it was resolved. Use this instead of logging a duplicate 
- `update_task`: Edit an existing Tango task in place. If client_id changes, task.agency_id is re-derived from the new client (client is authoritative). To reassign, use handoff
- `update_worker`: Update a worker's settings. Supports roles — the list of roles used to match tasks the worker can claim — and the monthly spend cap in USD: when the worker's re
- `verify_task_history`: Return the full append-only transparency-log history for a task and cryptographically verify the hash chain covering it. If `intact` is false, `broken_at_seq` p
- `whoami`: Self-orientation for a fresh MCP session. Returns the signed-in user, their organizations, active organization, visible clients, teammate handles, and workers t
- `write_integration`: Performs one write (POST or PATCH) call against a system this client has connected — post a Slack reply, comment on a GitHub pull request, update a Notion page,

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.