MCP server

The Supermetal MCP server lets your MCP client inspect and operate the connectors running on an agent. Each agent exposes /mcp on its own URL.

Connect a client

Point your client to your Supermetal agent.

Run this command.

claude mcp add --transport http --scope user \
  supermetal https://supermetal.example.com/mcp

If you have authentication configured, add this option to the command.

--header "Authorization: Basic <base64-credentials>"

Run this command.

codex mcp add supermetal --url https://supermetal.example.com/mcp

If you have authentication configured, add this entry to ~/.codex/config.toml.

[mcp_servers.supermetal.http_headers]
Authorization = "Basic <base64-credentials>"

Add the server to ~/.cursor/mcp.json or your project's .cursor/mcp.json.

{
  "mcpServers": {
    "supermetal": {
      "url": "https://supermetal.example.com/mcp"
    }
  }
}

If you have authentication configured, add this property to the server entry.

"headers": {
  "Authorization": "Basic <base64-credentials>"
}

Any MCP client that accepts a server URL and can reach the agent can connect. Examples include Claude Desktop, Cline, OpenCode, VS Code with GitHub Copilot, and Zed.

Follow the client's instructions for adding a server. Name it supermetal and use your agent's /mcp URL. If you have authentication configured, choose a client that accepts custom request headers and add Authorization: Basic <base64-credentials>.

Restart or reload your client. Then ask it to list the connectors on the agent to check the connection.

Multiple agents

Add each Supermetal agent under a distinct name. The client sends each tool call to the named agent. For example, use supermetal-finance and supermetal-analytics for two deployments.

Available tools

Tool	Description
`listConnectors`	List connectors and their status.
`getConnector`	Get a connector and its status.
`getConnectorHistory`	Get connector status history.
`getCatalog`	Get the schemas, tables, and columns available from a source.
`getConnectorConfigurationSchema`	Get the configuration schema for a source or target type.
`getMetrics`	Get agent metrics.
`listTasks`	List recent connector tasks, including snapshot state.
`getTask`	Get a connector task.
`sendConnectorCommand`	Send a connector command.

Example prompts

Try requests like these.

"Which connectors on this agent need attention?"
"Show the recent history and tasks for connector <connector-id>."
"List the source tables available to connector <connector-id>."
"Show the current metrics for this agent."
"Show the fields required for a PostgreSQL source."
"Which replication types does a PostgreSQL source support, and when should I use each one?"
"Restart connector <connector-id>."

Connect a client

Multiple agents

Available tools

Example prompts

On this page