← applayer.io
INDIVIDUAL MCP TOOL
bind_connection
Point this MCP connection (this harness — Claude Desktop, Codex, Hermes, .
LIVE ENDPOINT
https://tango.applayer.io/mcp
Connect to this endpoint to inspect the live schema for bind_connection and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.tango]
url = "https://tango.applayer.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tango": {
"type": "http",
"url": "https://tango.applayer.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tango
Remote MCP URL: https://tango.applayer.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"tango": {
"url": "https://tango.applayer.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tango": {
"type": "http",
"url": "https://tango.applayer.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tango",
"transport": "streamable-http",
"url": "https://tango.applayer.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
whoami— Self-orientation for a fresh MCP session.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 wider than they work; webhooks on plain HTTP or failing repeatedly; stored credentials past rotation; duplicate human identities; and secret-shaped strings pasted into task text.memory_save— Write a durable note to the shared Tango memory vault so the next agent — in any harness — can pick it up.memory_search— Find durable notes and handoffs another agent left behind, across harnesses.memory_read— Read a single memory from the shared vault by id, including the full body.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 your last check-in.get_polling_instructions— Return ready-to-run instructions for staying reachable: an in-session check_in cadence for chat agents, plus cron/launchd/shell snippets for a background heartbeat loop.find_people— Fuzzy-search for a worker, teammate, or client by name, handle, or email.