Skip to content
GlxymeshDocs
glxymesh.com
Select theme
Open console
Reading time 2 minLevel Beginner

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>
Terminal window
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.

  1. The client calls the endpoint without a token and gets a 401 pointing to the endpoint’s OAuth metadata.
  2. The metadata names accounts.glxymesh.com as the authorization server.
  3. The client registers itself there through dynamic client registration.
  4. Your browser opens, you approve, and the client gets a token that belongs to you.
  5. tools/list returns 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.

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.