Skip to main content
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

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

Install the Superlog plugin, then run /mcp and sign in:
See Claude for the Claude apps and other options.

Tools

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. The telemetry, error, dashboard, alert, synthetic, and Terraform tools need telemetry, which is in early access. create_ingest_key returns the new key once, with the OpenTelemetry settings for it. get_error_notifications and update_error_notifications are for workspace owners and admins. 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.”