MCP server - Superlog

The Superlog MCP server gives an AI assistant the management API as tools. Ask it to create an automation, change tag mode, start a run, or check why a run failed.

Server details


URL	`https://superlog.sh/api/mcp`
Transport	Streamable HTTP
Authentication	OAuth sign-in, or `Authorization: Bearer <API key>`

Clients that support MCP OAuth sign you in through Superlog. You choose a workspace and approve access, and the assistant acts as you in that workspace. For clients without OAuth, create an API key under Settings → API keys and send it as a bearer token. See API keys. The assistant acts as the member who created the key.

Connect a client

Claude Code
Cursor
Codex
VS Code

Install the Superlog plugin, then run /mcp and sign in:

claude plugin marketplace add superloglabs/claude-plugin
claude plugin install superlog@superlog

See Claude for the Claude apps and other options.

Add the server to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:

{
  "mcpServers": {
    "superlog": {
      "url": "https://superlog.sh/api/mcp",
      "headers": { "Authorization": "Bearer slk_..." }
    }
  }
}

Add the server to ~/.codex/config.toml and set SUPERLOG_API_KEY in your environment:

[mcp_servers.superlog]
url = "https://superlog.sh/api/mcp"
bearer_token_env_var = "SUPERLOG_API_KEY"

Add the server to .vscode/mcp.json. VS Code asks for the key the first time it starts the server:

{
  "inputs": [
    { "type": "promptString", "id": "superlog-key", "description": "Superlog API key", "password": true }
  ],
  "servers": {
    "superlog": {
      "type": "http",
      "url": "https://superlog.sh/api/mcp",
      "headers": { "Authorization": "Bearer ${input:superlog-key}" }
    }
  }
}

Tools

Area	Tools
Workspace	`get_workspace`, `list_members`
Integrations	`list_available_integrations`, `start_integration_connection`, `list_integrations`, `refresh_integrations`, `list_sentry_environments`
Automations	`list_automations`, `get_automation`, `create_automation`, `update_automation`
Runs	`list_automation_runs`, `start_automation_run`, `get_automation_run`, `cancel_automation_run`, `send_automation_run_message`
Tag mode	`get_tag_mode`, `update_tag_mode`
Models	`list_included_models`, `list_model_credentials`, `list_model_credential_models`, `test_model_credential`, `delete_model_credential`
Secrets	`list_secrets`
API keys	`list_api_keys`, `revoke_api_key`

Each tool takes the same fields as its API endpoint. Read-only tools are marked as read-only. update_automation, cancel_automation_run, update_tag_mode, revoke_api_key, and delete_model_credential are marked as destructive, so clients can ask before running them. start_integration_connection returns a consent link for the person to open in their browser. Integrations that need a credential return a secure setup link instead, so the credential is entered in Superlog and not in the conversation. Adding a workspace secret or a model API key is not available as a tool, so those values never pass through a model. Use the app or the API for them.

Example requests

“Create an automation that reviews new Sentry regressions in the api project and opens a pull request in acme/api.”
“Turn off the weekly dependency review.”
“Why did the last run of the triage automation fail?”
“Let tag mode read the acme/web repository.”

​Server details

​Connect a client

​Tools

​Example requests

Server details

Connect a client

Tools

Example requests