A hosted MCP server that exposes your collections, documents, forms, pages and design tokens to any AI agent that speaks the protocol.
Nothing to install. The server is running and maintained for you. You just need an MCP client (like Claude Code, Codex CLI, or Gemini CLI) that can point at the URL above.
Dynamic Client Registration. All three clients speak RFC 7591 DCR. On first connect, an OAuth application is created for you automatically — nothing to configure in the Console.
anthropic · claude.ai/code
Register the server:
claude mcp add --transport http solidpixels https://mcp.app.solidpixels.com/_mcp
Run /mcp, pick solidpixels, then Authenticate. Your browser opens, you sign in to your solidpixels account, approve the scopes and you’re connected.
If Claude Code is already running in another terminal, restart that session so the new server appears in /mcp.
Commit this to your project’s .mcp.json to share the server with the team:
{ "mcpServers": { "solidpixels": { "type": "http", "url": "https://mcp.app.solidpixels.com/_mcp" } } }
OAuth tokens are negotiated on first use and stored by Claude Code per user.
Use this if you work with multiple websites. Run inside your project folder:
claude mcp add --transport http --scope project solidpixels-myproject https://mcp.app.solidpixels.com/_mcp
The key part is --scope project — the server is stored in the folder’s .mcp.json instead of your user config, so each project folder can connect to a different website.
It is recommended to start conversations with “list my pages via solidpixels-myproject” first to make sure Claude is connected to the desired website.
Remove a registered server:
claude mcp remove solidpixels
Change solidpixels to the name you registered the server under, e.g. solidpixels-myproject.
openai · openai/codex
Heads up. Remote HTTP MCP is still experimental in Codex CLI. Add experimental_use_rmcp_client = true to ~/.codex/config.toml first.
Register the server:
codex mcp add solidpixels --url https://mcp.app.solidpixels.com/_mcp
Authenticate:
codex mcp login solidpixels
Opens your browser for OAuth sign-in to your solidpixels account.
Edit ~/.codex/config.toml:
experimental_use_rmcp_client = true [mcp_servers.solidpixels] url = "https://mcp.app.solidpixels.com/_mcp"
google · google-gemini/gemini-cli
Register the server:
gemini mcp add --name solidpixels --http-url https://mcp.app.solidpixels.com/_mcp
Gemini detects the 401 on the first tool call and starts the OAuth flow automatically — sign in to your solidpixels account and approve the scopes. You can also force it with /mcp auth solidpixels.
Edit ~/.gemini/settings.json:
{ "mcpServers": { "solidpixels": { "httpUrl": "https://mcp.app.solidpixels.com/_mcp" } } }
Skip Dynamic Client Registration and manage your own OAuth client instead.
Use this path if DCR is blocked in your environment, if you want to pin a specific client_id, or if you need to rotate credentials yourself. Everyone else should stick with the automatic flow in the client cards above.
Fill in the form:
Claude Code listens on port 8080 for the OAuth callback. The redirect URI must match exactly.
Once connected, ask your agent something real:
> list my collections and first 3 items solidpixels · data_list_collections (MCP) solidpixels · data_list_collection_items (MCP)(collectionId: "col_x", itemsPerPage: 3) Collections (1 total) 1. Products (products) — 8 items ┌──────────────┬──────────────┬──────┬────────────┐ │ Name │ Slug │ Qty │ Date │ ├──────────────┼──────────────┼──────┼────────────┤ │ Sample One │ sample-one │ 65 │ 2025-10-28 │ ├──────────────┼──────────────┼──────┼────────────┤ │ Sample Two │ sample-two │ 59 │ 2025-09-26 │ ├──────────────┼──────────────┼──────┼────────────┤ │ Sample Three │ sample-three │ 41 │ 2025-07-23 │ └──────────────┴──────────────┴──────┴────────────┘