Connect your AI agent to Glitchgrab (MCP)

Glitchgrab has an MCP server, so an AI agent (Claude Code, Claude.ai, Claude Desktop or any MCP client) can work with your projects directly. It can read reports, issues and recorded calls, comment on issues with screenshots, and write your guides.

The address is:

https://glitchgrab.dev/api/mcp

The same steps, with copy buttons, are on the Guides and API Tokens pages under Connect your AI agent (MCP).

Claude Code: sign in with your browser (recommended)

Run once:

claude mcp add --transport http --scope user glitchgrab https://glitchgrab.dev/api/mcp

The first time the agent uses a Glitchgrab tool, a browser opens on Connect <app>. It shows who you are signed in as and what the agent will be able to do. Press Approve.

--scope user makes it available in every project on your machine. Leave it out to add it to the current project only.

Claude.ai or Claude Desktop

1. Settings → Connectors → Add custom connector.
2. Paste https://glitchgrab.dev/api/mcp.
3. Press Connect, then Approve on the Glitchgrab page that opens.

CI, or a machine with no browser

Use a repo token (see Create an API token):

claude mcp add --transport http glitchgrab https://glitchgrab.dev/api/mcp \
  --header "Authorization: Bearer gg_your_token"

Sign-in, token or server key

	Browser sign-in	gg_ SDK token	ggc_ server key
Repos	every repo you own	only the token's repo	only the key's project
Guides	read and write	read published guides only	read and write
Recorded calls	the calls you can open on Calls	no	no (over MCP)
Reports, issues	yes	yes	no
Search Console tools	yes	no	no
Where from	your own machine	CI, servers	your own server

A gg_ token ships in your app's JavaScript, so it can never write guides or reach call recordings.

For both of those, each project has one secret server key (ggc_…), issued on API Tokens → Server keys:

• Your server can use it to write guides (see Write guides from your own server).
• Your admin panel can use it to show calls you shared with the client (see Share a call with your client). This works through glitchgrab/server, not MCP.

Over MCP, a server key reaches the project's guide tools only.

What the agent can do

Tool	Does
list_repos	Your connected repos
get_reports	Recent reports, filterable by repo and status
get_issue	Read a GitHub issue and its comments
comment_on_issue	Comment on an issue as the Glitchgrab app
create_image_upload_url	Upload a screenshot and get a public link that renders even on private repos
list_guides / get_guide	Read your guides
save_guide / delete_guide	Create, update (by slug) or delete a guide
list_calls	Recorded calls you can open: title, date, length, who attended, transcript status, one-line summary, and whether the call is shared with the client
get_call	One call in full: audio links, transcript, summary with timestamps, and the screenshots taken during the call
get_indexing_status, list_not_indexed_pages, request_reindex	Google Search Console

It cannot close issues, push code, or change your account.

Call recordings

• get_call gives links, not files. They work for 15 minutes, so the agent should download the audio straight away (curl -o call.webm "<url>") or ask again.
• A call recorded by the bot has one audio track, call. A call recorded with the extension has two: client (everyone else on the call) and recorder (you).
• Screenshots come a page at a time; an hour-long call has around 300. Ask for more with framesOffset and framesLimit.
• The agent sees the same calls you see on Calls: projects you own or were given access to. Being in the org is not enough.

Try it

Ask the agent:

• "List my Glitchgrab repos."
• "Read issue 123 on owner/repo and summarise what the reporter saw."
• "Get yesterday's call on owner/repo and list everything the client asked for, with timestamps."
• "Write a guide on owner/repo for adding a client, with screenshots, and publish it."

Troubleshooting

• The browser never opens: run any Glitchgrab tool once. The sign-in starts on first use.
• "Can't connect" page: the connection request was not recognised. Remove the connector and add it again.
• A tool says it needs your own login: you connected with a gg_ token or a server key, and that tool needs the browser sign-in. Call tools always do.
• A tool says it is not available to a server key over MCP: a server key reaches guides only. Connect with your browser sign-in for everything else.
• An audio link stopped working: it expired after 15 minutes. Run get_call again.
• New tools don't show up after an update: reconnect the connector so the agent reloads the tool list.
• Using Claude Desktop with a local server instead? See Use the local Glitchgrab MCP server.