Connect your agent

Every MCP-capable agent connects to the same streamable-HTTP endpoint:

https://api.packagemaze.com/mcp

Keep 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.

claude mcp add --transport http packagemaze https://api.packagemaze.com/mcp

Then run /mcp and authenticate.

Open Settings → Connectors → Add custom connector. There is no command or config file — paste the endpoint:

https://api.packagemaze.com/mcp

Approve PackageMaze on the consent screen that opens. Traffic originates from Anthropic's cloud.

codex mcp add packagemaze --url https://api.packagemaze.com/mcp --oauth-client-id packagemaze-codex
codex mcp login packagemaze

{
  "mcpServers": {
    "packagemaze": {
      "url": "https://api.packagemaze.com/mcp"
    }
  }
}

Or add it in one click: Add to Cursor.

{
  "servers": {
    "packagemaze": {
      "type": "http",
      "url": "https://api.packagemaze.com/mcp"
    }
  }
}

Or install it from the browser: Install in VS Code.

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/mcp

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.

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.