Connect an MCP client
Connect Claude Code, Claude Desktop, Cursor, VS Code and other MCP clients to a Glxymesh MCP server over Streamable HTTP with OAuth, and fix 401/404/405.
A client needs only the project’s endpoint URL. There’s no API key to create, because the client registers itself and you approve it in the browser.
https://mcp.glxymesh.com/mcp/<org>/<project>Add the endpoint
Section titled “Add the endpoint”claude mcp add --transport http glxymesh https://mcp.glxymesh.com/mcp/<org>/<project>Then, inside a session, run /mcp and choose glxymesh → Authenticate. A browser opens once
to sign in. After that, Claude Code keeps the token.
Remote servers are added in the app’s UI, not in a config file:
- Open Settings → Connectors → Add custom connector.
- Name it
Glxymesh. - Paste the endpoint URL.
- Choose Connect, then approve the sign-in page that opens.
Clients that read a JSON config use this format:
{ "mcpServers": { "glxymesh": { "type": "http", "url": "https://mcp.glxymesh.com/mcp/<org>/<project>" } }}Where this goes depends on the client: .cursor/mcp.json for Cursor, for example. Check your
client’s MCP documentation for the location and for whether it uses mcpServers or servers as
the top-level key.
What happens on first connect
Section titled “What happens on first connect”- The client calls the endpoint without a token and gets a
401pointing to the endpoint’s OAuth metadata. - The metadata names
accounts.glxymesh.comas the authorization server. - The client registers itself there through dynamic client registration.
- Your browser opens, you approve, and the client gets a token that belongs to you.
tools/listreturns the project’s tools. After that, every call appears on the console’s Invocations screen.
The token belongs to you, not to the project. Anyone who uses the endpoint signs in with their own account and needs to be a member of the organization.
Troubleshooting
Section titled “Troubleshooting”| Status | Meaning |
|---|---|
404 |
The org or project in the URL doesn’t exist for you. A project you aren’t a member of looks the same as one that doesn’t exist, so check the slugs in the console’s Settings. |
401 |
The token expired or was issued somewhere else. Re-authenticate in the client. It won’t register again. |
405 |
Expected when you open the URL in a browser. The endpoint accepts POST only. |
If a tool you pushed doesn’t appear, run gxmesh tools to check that it’s in the project you
connected to.