Connect your agent
Connect any MCP-capable agent to PackageMaze with one URL. Once connected, the agent works against the same Feeds, Tokens, and policies your team uses — nothing more.
https://api.packagemaze.com/mcpThe endpoint
#Every MCP-capable agent connects to the same streamable-HTTP endpoint:
https://api.packagemaze.com/mcpKeep this URL when clients upgrade. PackageMaze serves the modern 2026-07-28 protocol when a client uses it and preserves the compatible 2025-11-25 path for existing clients.
Connect your client
#Claude Code
#claude mcp add --scope user --transport http packagemaze https://api.packagemaze.com/mcpThen run /mcp and authenticate. User scope keeps PackageMaze connected in every repository on this machine, not only the one you ran the command in.
claude.ai / Claude Desktop
#Add it in one click: Add to Claude. Or open Customize → Connectors → Add → Add custom connector and paste the endpoint:
https://api.packagemaze.com/mcpApprove PackageMaze on the consent screen that opens. On Team and Enterprise plans an Owner adds the connector in Organization settings → Connectors, then each member connects with their own account. Traffic originates from Anthropic's cloud.
ChatGPT
#Open Plugins, select +, then Add custom MCP server. Name it PackageMaze, enter the endpoint as the Server URL, choose OAuth, and select Create as a plugin:
https://api.packagemaze.com/mcpInstall the plugin, then approve PackageMaze on the consent screen. Your ChatGPT account and workspace policies decide whether you can add a custom MCP server.
Codex
#codex mcp add packagemaze --url https://api.packagemaze.com/mcp --oauth-client-id packagemaze-codex
codex mcp login packagemazeGemini CLI
#gemini mcp add --scope user --transport http packagemaze https://api.packagemaze.com/mcpGemini CLI opens the browser to approve PackageMaze the first time it connects; run /mcp auth packagemaze to sign in again.
Goose
#Add it in one click: Add to Goose. Or run goose configure, choose Add Extension → Remote Extension (Streamable HTTP), and enter the endpoint.
Cursor
#{
"mcpServers": {
"packagemaze": {
"url": "https://api.packagemaze.com/mcp"
}
}
}Or add it in one click: Add to Cursor.
VS Code
#{
"servers": {
"packagemaze": {
"type": "http",
"url": "https://api.packagemaze.com/mcp"
}
}
}Or install it from the browser: Install in VS Code.
Other clients
#Any streamable-HTTP MCP client can use the endpoint directly. For stdio-only clients, bridge it with the mcp-remote shim:
npx -y mcp-remote https://api.packagemaze.com/mcpCompatibility
#Core tools, resources, prompts, and OAuth use the same endpoint in both protocol eras. See the current tool manifest for the live capability catalog and required scopes.
- Codex: the commands above work in its default compatibility mode and with its modern MCP mode enabled.
- Claude Code: the command above keeps using the supported compatibility path; upgrading PackageMaze does not require removing or re-adding the server.
- Other streamable-HTTP clients: use the same URL and complete OAuth in the browser. No PackageMaze-specific transport is required.
Optional enhancements degrade to the ordinary tool workflow:
- A client with MCP Apps support may embed Setup and guarded-change review. Other clients receive the same complete text and structured result.
- A modern client that declares form elicitation may show one guided Feed choice. Other clients receive the same follow-up questions and retry guidance.
- Modern routing and private catalog caching reduce protocol overhead without changing authorization. Every tool call still checks the current grant.
What connecting grants
#Connecting opens a consent screen that scopes the connection to one Organization and the Feeds you choose. Authorizations expire after three months, you can revoke one at any time from the Agents page, and connected agents don't count as seats.