Glitch MCP

VS Code

For use with the Agent in VS Code chat.

Server URL
https://mcp.glitchads.ai/mcp

Adding the server

Run MCP: Add Server from the Command Palette for a guided setup, or write the configuration yourself. Per workspace, in .vscode/mcp.json:

{
  "servers": {
    "glitch": {
      "type": "http",
      "url": "https://mcp.glitchads.ai/mcp"
    }
  }
}

For a server across all your workspaces, run MCP: Open User Configuration and add the same entry there.

For an API key, use the inputs pattern. VS Code asks for the secret when the server first starts and stores it securely, so the key is never written into the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "glitch-key",
      "description": "Glitch API key",
      "password": true
    }
  ],
  "servers": {
    "glitch": {
      "type": "http",
      "url": "https://mcp.glitchads.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${input:glitch-key}"
      }
    }
  }
}

VS Code does not pass servers that use input variables, like the one above, to Agent Host sessions.

Without a header, VS Code signs in with OAuth and registers itself with Glitch through Dynamic Client Registration. The first time a server starts, VS Code asks you to confirm that you trust it.

Using it

In the chat input, select Agent from the agent picker. Select Configure Tools to see the glitch_* tools and choose which are enabled. With the default Manual permissions, VS Code asks for your confirmation before a tool call that is not auto-approved runs.

Check it worked

  • The MCP SERVERS - INSTALLED section of the Extensions view lists glitch, and so does MCP: List Servers.
  • The tool list shows tools named glitch_*: all thirty-one when every scope was approved, and fewer when some were not.

Ask: "List my Glitch organizations." You should get back the organizations your connection covers, with your role in each.

Troubleshooting

The MCP options are missing entirely MCP can be disabled by policy in a managed VS Code install: the chat.mcp.access setting set to none. Ask your administrator.
The server does not start Run MCP: List Servers, select glitch and choose Show Output to read the log. The same list can restart the server.
insufficient_scope The error names the scope that is missing. Authenticate the server again, approving the extra access. If your Glitch role does not allow it, ask an organization Admin or Owner.
org_access_denied The organization slug is wrong, your Glitch user is not a member of that organization, or the membership ended. glitch_list_organizations shows the slugs you can use.
Revoking access Remove the server from mcp.json, or revoke it in Glitch on the Connections page under Connected Apps. Either stops access on the next request.

Next