Bring image processingto your AI assistant
Call theGlitch directly from Claude, Cursor, or any MCP-compatible AI assistant. Setup takes 30 seconds.
{
"mcpServers": {
"theglitch": {
"url": "https://mcp.theglitch.app/mcp",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}
Gives your AI assistant direct tools
Model Context Protocol — an open standard for AI assistants to call external services. One config line.
Added to the tool belt
14 image processing tools appear in your assistant's tool belt — like native tools.
Called in conversation
"Remove the background of this product photo" — the AI handles the rest, calling the tool with the right params.
Your key stays safe
With a local client the key stays on your machine; with the claude.ai connector the request is relayed via Anthropic. Either way the key only ever reaches theGlitch.
Works in the chat flow
glitch_social_preset
glitch_remove_bg
glitch_colorize → glitch_upscale
glitch_optimize
glitch_watermark → glitch_resize
glitch_remove_object
Connect in 30 seconds
Three ways in: add it to Claude by hand with no file to edit, connect with a config file, or run the connector package on your own machine. All 14 tools show up in your client either way.
Add it to Claude by hand
For Claude Desktop and claude.ai you do not have to edit any file — you can add the connector from the interface. This is the fastest route.
Open the connectors screen
Settings → Connectors → Add custom connector.
Paste the server address
Enter this URL in the server address field.
URLhttps://mcp.theglitch.app/mcpAdd your key as a header
Add a header in the advanced settings. You get your key from the dashboard.
Headerx-api-key: YOUR_API_KEYAdd — but do not press Connect
Save it with the Add button. Do not press Connect: this connection never asks you to sign in, it authenticates with the key.
Verify the tools
Open the tools icon in the chat box and confirm the 14 tools are listed.
Connect to the remote server
Nothing to install: you give your client the server address and the x-api-key header, and that is it. This is the route for clients that read their configuration from a file, like Cursor, VS Code and Claude Code.
Get an API key
Create a key in your dashboard — a unique string you pass to the server.
Add the config
Add the server address and the x-api-key header to your client's MCP configuration and replace YOUR_API_KEY with your own key. In Claude Desktop you add it from Settings → Connectors instead of editing a file.
{ "mcpServers": { "theglitch": { "url": "https://mcp.theglitch.app/mcp", "headers": { "x-api-key": "YOUR_API_KEY" } } } }Claude Code./.mcp.jsonCursor~/.cursor/mcp.jsonVS Code./.vscode/mcp.jsonRestart your client
Fully quit and reopen it. The 14 tools appear in your assistant's tool list.
Test it
Try: "Remove the background of this image: https://theglitch.app/showcase/bg-before.webp"
Or run the package on your own machine
Run the connector package locally with npx; requests then go straight from your own machine to theGlitch.
The @theglitch/mcp-server package has not been published to npm yet, so the npx command below will fail for now. This only affects the local method — the remote server above works today. The configuration is ready and will work as-is the moment the package ships.
{
"mcpServers": {
"theglitch": {
"command": "npx",
"args": [
"-y",
"@theglitch/mcp-server"
],
"env": {
"THEGLITCH_API_KEY": "YOUR_API_KEY"
}
}
}
}
14 tools, one connection
One hand-built tool for each of the 14 transforms in the REST API; the tool list ships with the connector and is not generated from the endpoints.
About MCP
Create an account, grab the key, integrate in 30 seconds.
No credit card. Start connecting from the Free plan.