Connect an MCP client

Endpoint

All MCP clients connect to the single Streamable-HTTP endpoint at https://mcp.packagento.com/mcp. The endpoint enforces OAuth on every request; no additional API keys are needed.

Claude Code (recommended)

Claude Code is the primary route in use by Packagento developers. Two equivalent paths:

Add from the shell

Run this once from any terminal — Claude Code stores the server in your user-level config and every session picks it up:

claude mcp add --transport http packagento https://mcp.packagento.com/mcp

To scope the server to a single project instead of every session, add --scope project and run the command from that project's root. The server entry lands in .mcp.json beside your code.

Add from inside an existing session

Already in a Claude Code session? Type /mcp at the prompt to open the MCP server manager. Choose Add server, pick HTTP, and enter https://mcp.packagento.com/mcp.

First-run OAuth

The first time Claude Code calls a Packagento tool, your browser opens the consent screen. Sign in to Packagento if you are not already, click "Allow", and the tool call completes. Subsequent calls in the same session, and every future session on the same machine, run without prompting until the refresh token rotates (every 90 days).

Confirm it is live

Type /mcp at any time to see the connection status; or ask the assistant "who am I on Packagento?" — the whoami tool round-trips through OAuth and returns your customer + active org.

Other MCP-compatible clients

Any client supporting Streamable HTTP MCP transport will work. Point it at https://mcp.packagento.com/mcp and complete OAuth in the browser tab the client launches. The exact UI varies — consult your client's own documentation for "add an MCP server" or "add a custom connector".

Managing connected applications

Each MCP client that completes OAuth shows up under MCP Integrations in your customer area. From there you can see when each application last made a tool call and revoke its access individually. Revocation invalidates the refresh token immediately; the client will prompt you to re-authorise on its next call.

Open MCP Integrations →

What the consent screen shows

The consent screen identifies the requesting application by name and shows the redirect URI it will be sent to. If the application requested specific scopes, those appear too; if it did not, the consent screen omits the section and the application gets the default access for the OAuth client it registered as. Approve "Allow" only for applications you trust to act as you on Packagento.