Skip to main content

AI Assistant Access

sypho-mcp is a stdio MCP server, installed alongside the CLI, that exposes your control plane itself to an MCP client like Claude Code — agents, deployments, runs, scheduled tasks, webhooks, and structured data, all through natural-language tool calls instead of typing sypho commands by hand.

This is unrelated to the MCP servers your agents call at run time — see MCP Servers for that. sypho-mcp is for operating the platform, not something a running agent talks to.

Register it​

claude mcp add --scope user sypho -- sypho-mcp

It shares the CLI's login — whatever profile sypho login set up in ~/.sypho/config.toml (SYPHO_PROFILE picks a non-default one). If you haven't logged in yet, just ask — the server can call login itself.

What you can ask it to do​

  • Agents & deployments — list, inspect, deploy, roll back, delete, see what deleting a version would affect first.
  • Runs — create, inspect, debug, pull logs.
  • Scheduled tasks & webhooks — create, update, list.
  • Skills — push_skill publishes a skill directory, same as sypho skill push.
  • Agent scaffolding — init_agent and deploy_agent do what sypho init/sypho build/sypho deploy do, without leaving your assistant.
  • Multiple orgs — list_profiles, then pass profile on calls that need a non-default one.

If a specific route has no dedicated tool, api_request calls the control-plane API directly — nothing is actually out of reach.

Example​

"List my agents, then show me what happens if I delete version 0.3.0 of support-triage."

The assistant calls list_agents, then get_agent_deletion_plan, with no sypho commands typed and no control-plane URLs or tokens to remember.