claude mcp list: add --json flag to expose connector UUIDs

Resolved 💬 2 comments Opened Apr 4, 2026 by atreidesmodi Closed May 14, 2026

Problem

Remote triggers (/v1/code/triggers) require a connector_uuid in the mcp_connections field to wire MCP connectors to scheduled agents. There is no programmatic way to discover a connector's UUID after creating it in the Claude.ai UI.

claude mcp list shows custom connectors with their names and URLs but does not expose the UUID:

claude.ai Atreides Email: https://atreides.backcreek.us/mcp - ✓ Connected
claude.ai Test MCP: https://atreides.backcreek.us/mcp-test - ✓ Connected

The CLI clearly fetches this data from the backend (including the UUID), but doesn't surface it.

Requested Change

Add --json or --output json flag to claude mcp list and claude mcp get that outputs the full connector metadata including uuid/connector_uuid:

[
  {
    "name": "Atreides Email",
    "url": "https://atreides.backcreek.us/mcp",
    "uuid": "9ca5c2ba-baee-4b12-ae02-28c7bd80d985",
    "status": "connected"
  }
]

Why This Matters

Without this, creating remote triggers with MCP connectors from CLI requires a manual UI workaround:

  1. Create trigger via CLI
  2. Go to Claude.ai web UI to attach the connector to any trigger
  3. Read back the trigger via API to capture the UUID
  4. Use that UUID for future triggers

This doesn't scale when managing many MCP servers and scheduled agents programmatically.

Environment

  • Claude Code 2.1.92
  • macOS Tahoe 26.4

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗