GlitchTip MCP server

What the model can do

GlitchTip error tracking, hosted or self-hosted: projects, issues with counts and when first and last seen, and one issue's latest stack trace and comments. Can add, edit and delete comments, resolve, ignore, reopen, assign or delete an issue, create or delete releases and record deploys, create, change or delete uptime monitors and projects, create teams and private status pages, and invite or remove members.

Reads

• glitchtip_list_projectsGlitchTip projects in the connected organization: id, slug, name, platform, when created and first event.
• glitchtip_list_issuesGlitchTip issues (grouped errors), most recently seen first by default: id, short id, title, culprit, status, level, event and user counts…
• glitchtip_get_issueOne GlitchTip issue: its summary, the latest event (title, message, culprit, platform, tags and the exception's last stack frames, without user…
• glitchtip_list_monitorsGlitchTip uptime monitors in the connected organization: id, name, type, url, whether up and since when, interval, timeout, expected status…
• glitchtip_list_releasesGlitchTip releases in the connected organization, newest first: version, when released and created, ref, projects, and how many deploys and commits.
• glitchtip_list_teamsGlitchTip teams in the connected organization (the team slug glitchtip_create_project takes): slug, member count and projects.
• glitchtip_list_membersMembers of the connected GlitchTip organization (the member id glitchtip_remove_member takes): id, name, role, whether still a pending invite…

Acts, when you ask

These change something in GlitchTip. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• glitchtip_add_commentAdds a comment to a GlitchTip issue as the token's user.
• glitchtip_update_commentEdits a GlitchTip comment, REPLACING its whole text; the old text is not kept anywhere.
• glitchtip_delete_commentDESTRUCTIVE, deletes a comment from a GlitchTip issue.
• glitchtip_update_issueChanges a GlitchTip issue's status (resolved, ignored, or unresolved to reopen it) and/or who it is assigned to…
• glitchtip_create_releaseRecords a release (a version of your code) in GlitchTip for one or more projects (by slug), with an optional git ref and release date…
• glitchtip_create_deployRecords in GlitchTip that a release was deployed to an environment (a record only: nothing is deployed)…
• glitchtip_delete_releaseDESTRUCTIVE, deletes a GlitchTip release by version, with its deploy records and uploaded files.
• glitchtip_create_monitorCreates a GlitchTip uptime monitor: a name, a type (Ping, GET, POST, TCP Port, SSL or Heartbeat), the URL to check (not for Heartbeat)…
• glitchtip_update_monitorChanges a GlitchTip uptime monitor, REPLACING the fields given (name, type, url, interval, timeout, expected status or body, confirmation threshold)…
• glitchtip_delete_monitorDESTRUCTIVE, deletes a GlitchTip uptime monitor and its check history; the address stops being watched.
• glitchtip_create_projectCreates a GlitchTip project under a team (by team slug, from glitchtip_list_teams): a name, and optionally a slug, platform (e.g. javascript…
• glitchtip_update_projectChanges a GlitchTip project's name, slug, platform or event throttle rate, REPLACING the values given and keeping the rest…
• glitchtip_delete_projectDESTRUCTIVE, deletes a GlitchTip project with all its issues, events, releases' links…
• glitchtip_create_teamCreates a team in the connected GlitchTip organization by slug.
• glitchtip_create_status_pageCreates a private status page in the connected GlitchTip organization, by name.
• glitchtip_invite_memberCHANGES ACCESS AND SENDS AN EMAIL.
• glitchtip_remove_memberDESTRUCTIVE, CHANGES ACCESS.
• glitchtip_delete_issueDESTRUCTIVE, deletes a GlitchTip issue with its events and comments.

Connect it

First connect GlitchTip on Dashboard → Connections, then add Memtro to your client once. The GlitchTip tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared GlitchTip connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which new errors appeared in the checkout project today?
• › How many users has the payment timeout error affected?
• › Where in the code does issue CHECKOUT-4F fail?
• › Resolve CHECKOUT-4F and add a comment saying the fix shipped in 2.14
• › Record release 2.14 as deployed to production

Questions

Is this an official GlitchTip MCP server?

No. It is Memtro's MCP server with Memtro's GlitchTip connector behind it: the connector reads GlitchTip through its API with the credentials you connect on Dashboard → Connections, and GlitchTip publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in GlitchTip?

Only when you ask, and only what it has been granted: add a comment to an issue; edit a comment's text; delete a comment; resolve, ignore or reopen an issue, or change who it is assigned to; delete an issue; record a release for one or more projects; record a deploy of a release to an environment; delete a release (permanent); create an uptime monitor; change an uptime monitor; delete an uptime monitor (permanent); create a project under a team; rename a project or change its platform or throttle; delete a project with all its issues (permanent); create a team; create a private status page; invite a person to the organization (emails them); remove a member from the organization. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server