This is the buyer side, packaged as MCP tools. If you instead want to put a paywall on your own MCP server so its tools get paid, that’s the seller side — see MCP Integration. The Docs MCP is a third, unrelated server that streams this documentation into your IDE.
The full guide lives in the MCP section: Catalog MCP Overview. It covers how to import the server into any harness, Claude or ChatGPT; authentication; the walkthrough quickstart; and the complete tool surface — with a reference page per tool. This page is the short introduction and the video.
See it in action
Claude, ChatGPT and a LangSmith Fleet agent each buy real services from a $5 budget approved once — recorded on live, with real money.
How it fits: discover, then pay
Discover
list_categories, search_services, and get_service read the Catalog — public, no key. Your agent finds a service and reads its protocol, endpoint, and price.Pay
pay_service hands the call to the Router, which reads the merchant’s 402, pays it from your Delegation, enforces the cap, and relays the vendor’s response. route_by_intent does both steps in one call.Get started
Import & authenticate
Instant-setup commands for Claude Code, Cursor, Continue and Claude Desktop, plus the OAuth path for Claude and ChatGPT.
Connect from your assistant
Claude, ChatGPT and LangSmith Fleet, step by step — approve a spending cap once, no API key.
Quickstart (API key)
Connect a host, run a discovery call, then a paid call — end to end.
Every tool, documented
A reference page per tool — arguments, returns, refusals, and a
curl to test it.Not this MCP
Nevermined ships three MCP servers. Make sure you want this one:Next
Catalog MCP Overview (full guide)
Import, auth, quickstart, and the complete tool reference.
Using the Catalog from a harness
The code-free playbook for driving discovery and payment from your agent.
Router: pay
Delegations, the spending cap, the rails, and every refusal code.
Payment ledger
Read back everything your agents have spent, across every protocol.