Graunt

npx add-mcp 'https://api.graunt.com/v1/mcp'

Add Graunt as a connector and your assistant can search the catalog, read a packet's terms, cite it, and read the files of any free packet whose seller requires no account, all with no account and no key. Using a packet you already own takes one more step: connect your library with your Graunt account, or hand your assistant your AI access key.

Use a packet you own

The catalog connector searches Graunt's public catalog, and it does not carry the packets you own. Those travel two ways: connect your library (the same connector settings, a second server URL, and one sign-in), or a read-only AI access key from your library. Each client below has both sets of steps. See how to use your AI access key for handing it to your assistant and revoking it.

Add the connector

Use these settings in any client:

• Server URL: https://api.graunt.com/v1/mcp
• Authentication: none (the catalog is public)
• Protocol: Streamable HTTP (MCP) over JSON-RPC 2.0

ChatGPT

1. Open Settings → Plugins and choose Browse directory. On that page, click Add → Add custom MCP server.
2. Name it Graunt, leave Connection on Server URL, paste https://api.graunt.com/v1/mcp, and set Authentication to No authentication. ChatGPT starts on OAuth, which the catalog does not use.
3. Tick I understand and want to continue. Create as a plugin stays disabled until you do. OpenAI shows this notice for any custom server. This one is read-only and takes no credential.
4. Click Create as a plugin. It appears under Installed. Open it and choose Try in chat.
5. Ask it to find a packet by keyword. A working connector answers with a listing and a graunt.com/listings/… link you can open.

Your library in ChatGPT. Add a second custom MCP server the same way, with these changes:

1. Name it Graunt library and paste https://api.graunt.com/v1/mcp/library.
2. Leave Authentication on OAuth. ChatGPT finds Graunt's sign-in on its own. Advanced OAuth settings shows Dynamic Client Registration and the scope library:read, and nothing there needs changing.
3. After Create as a plugin, click Continue to Graunt library. Sign in at graunt.com and click Allow read access.

A custom connector belongs to the account that adds it. On Business and Enterprise workspaces an admin may need to permit custom connectors first, under Workspace Settings → Permissions & Roles → Connected Data. On those plans an admin can instead add it once for the whole workspace. If the connector cannot reach Graunt, check whether Lockdown mode is on. It sits under Settings → Security and login and limits what can connect to external services.

Claude

1. Open Settings → Customize → Connectors, then Add → Add custom connector.
2. Name it Graunt, paste https://api.graunt.com/v1/mcp as the MCP server URL, and click Continue.
3. Claude detects No sign-in. Keep it and click Add.
4. Enable it in a conversation from the + menu.

Your library in Claude. Add a second custom connector the same way, with these changes:

1. Name it Graunt library, paste https://api.graunt.com/v1/mcp/library, and click Continue.
2. Claude detects Sign in now and Register automatically. Keep both and click Add.
3. Click Connect. Sign in at graunt.com and click Allow read access.

No developer mode or risk acknowledgement is required here. On Team and Enterprise plans an organization owner can add it once and members enable it per conversation. Claude reaches the server from its own cloud rather than from your machine, so anything that blocks that path (VPN, IP allowlist, private DNS) breaks it even when the URL opens in your browser.

Claude Code

1. Add the catalog connector from your terminal: claude mcp add --transport http graunt https://api.graunt.com/v1/mcp
2. To read the packets you own as well, add the library connector: claude mcp add --transport http graunt-library https://api.graunt.com/v1/mcp/library. Then, in Claude Code, run /mcp, choose graunt-library, and pick Authenticate. Sign in at graunt.com and click Allow read access.
3. Ask Claude Code to search Graunt for a topic. A working connector answers with a listing and a graunt.com/listings/… link you can open.

Each command adds the server to the project you run it in. Add --scope user to have it in every project.

Other MCP clients

For Cursor, Windsurf, and other MCP clients, follow your client's MCP setup instructions and use the same server URL with no authentication.

Cursor and VS Code can take it in one click:

• Add to Cursor
• Add to VS Code

Both links carry only the server URL https://api.graunt.com/v1/mcp shown above. No command runs on your machine and no credential is passed. To configure it manually, add that URL to your editor's MCP settings.

Assistants that read web pages

An assistant that browses rather than connecting needs nothing configured: graunt.com/explore, GET /v1/listings?q=, and GET /v1/listings/{id} are public and take no key and no headers.

What the connector reaches

search takes keywords and returns matching packets with their public URLs. fetch takes a packet id and returns its description, commercial terms, and rights. For a free packet that needs no account, fetch also returns the files: small text files such as CSV, JSON and Markdown in full (up to 200 KB of text), and a short-lived download link for each listed file (at most 100 per fetch). Images, audio and video carry no link and download from the packet's page. tools/list also returns Graunt's own catalog reads: listing search and detail, the agent commerce manifest, the packet manifest, and the capability and Refinery support endpoints. Every one reads the same public catalog this site serves, so this connector reaches published listings and free downloads only, never a buyer's entitled content. The packets you own travel on the library connector instead. Clients cache tool definitions. Use the client's Refresh control to pick up changes.

Connect your library

A second connector carries the packets you own. It uses the same settings screen as the catalog connector, with two differences: the server URL ends in /library, and you sign in with your Graunt account.

• Server URL: https://api.graunt.com/v1/mcp/library
• Authentication: OAuth. Your client discovers it on its own. You sign in at graunt.com once and click Allow read access.

1. Add a second connector with the library URL and name it Graunt library. There is no client ID or secret to enter: the client registers itself with Graunt.
2. The client opens Graunt's sign-in, then a consent screen. Allowing grants read-only access to the packets this account owns. The connection cannot purchase, publish, or change anything.
3. After you sign in, the connection works across conversations and devices until you revoke it.

Step by step: ChatGPT, Claude, and Claude Code, where the second command adds this connector and /mcp → Authenticate opens the sign-in.

The connected library adds three tools: library_list (what you own), library_get_item (one packet's files and terms), and library_read_file (read a file range, metered against your library's daily byte budget). The public catalog tools are included, so one assistant can search, cite, and read what you own in the same conversation.

Revoke a connection from Account → Connected assistants. It stops working immediately in every conversation that used it. Your other keys keep working.

Connect with a credential

• Server: POST https://api.graunt.com/v1/mcp or POST https://api.graunt.com/v1/mcp/messages
• Auth: Authorization: Bearer grnt_agent_<64hex>
• Scopes: quote:read, buy:execute, sell:submit, receipt:read, bundle:assemble, publish:review_read

A credential widens tools/list to the tools your scopes allow. Send the header only on the calls that need it. A credential that is present is always verified, so a token that does not carry the authority you asked for is rejected rather than quietly narrowed.

Discover

• tools/list returns the catalog available to your credential's scopes, or the public tools when you send none.
• GET /v1/mcp/server-info returns the server descriptor + capability summary (public; cache-control: public, max-age=300).

Discovery keys pasted as a link

Agent discovery keys open the public catalog, and they are pasted as a link. Some assistants fetch such a link only when the workspace permits it. In ChatGPT Work (Business and Enterprise), a workspace admin can allowlist graunt.com for agent browsing, per OpenAI's allowlisting guide. Without such a workspace, use the connector above or the public reads.

You can permanently turn off a key you no longer want. Every read stops immediately. The route depends on whether the key is linked to an account, and the two do not overlap.

• Linked to an account: turn it off from your account. Linked keys are the only ones listed there.
• Never linked (the usual case for a key pasted straight into an assistant): post the key itself to POST /v1/agent-keys/starter/revoke. Send it in the request body, never in a URL.

Execute purchases

Purchases run through the same commerce path as human checkout, with the same financial math and review gates. Idempotency-Key is required on every execute.

Execute at POST /v1/agents/purchases/execute. The MCP connector carries no purchase tools, so every client buys through that endpoint.

Limits

• No amount limit on a paid purchase.
• A purchase charged to the card on file for your organization stays within the daily and monthly spend caps the account holder set for that agent.
• Per-credential rate limits apply (BUY, SELL, read).

Agent identity

Agents authenticate with a scoped grnt_agent_* credential issued by a Graunt account. An account login token is not accepted on this transport. Agent identity is always the account that issued the credential. There is no standalone autonomous agent principal.

Live state

/v1/meta/capabilities lists what Graunt offers to an agent, in machine-readable form.