Signing in
The server needs to know whose account a search is charged to. There are two ways to tell it, and both end in the same kind of token.
The server needs a paid plan. Before you sign in, the
tool list and read_docs work, and the first call that needs an account
asks you to sign in; a free account also gets account, and every other
tool answers plan_required - see Limits and errors.
Your client
Page ids for read_docs: mcp/claude, mcp/chatgpt,
mcp/editors (code editors and command-line agents),
mcp/automation, mcp/developers.
| Client | How it signs in |
|---|---|
| Claude, web and desktop | OAuth |
| Claude Code | OAuth or token |
| ChatGPT | OAuth |
| Codex CLI | OAuth or token |
| Goose | Token or OAuth |
| VS Code | Token |
| Cursor | Token |
| Devin Desktop | Token |
| Gemini CLI | Token |
| opencode | Token |
| MiMo Code | Token |
| DeepSeek Harness | Token |
| Qwen Code | Token |
| n8n, Make, Zapier | Token |
| Your own code | Token or OAuth |
Sign in with OAuth
For Claude, ChatGPT and other assistants that offer it. Nothing to copy:
- Add the server URL
https://api.publicwww.com/mcpand choose OAuth if the assistant asks how to authenticate. - Leave OAuth client ID and client secret empty, if the form has them: PublicWWW does not register clients, it recognises each assistant by a document the assistant publishes on its own site.
- The assistant opens PublicWWW. Sign in with the one-time code we email you, if you are not signed in already.
- You see which application is asking, the site that vouches for it and where you will be sent back. Press Allow.
The connection then appears on your profile page, tab API / MCP, under Connected apps.
Or use a token
For code editors, command-line agents and your own scripts. Issue a token on your profile page and give the client this header:
Authorization: Bearer <token>
It is the same token the API uses, and up to ten can exist at once, so give each client its own: if one leaks, delete it alone. Keep tokens out of files you commit - most clients can read the token from an environment variable or ask for it once; the client pages show how.
A client that offers OAuth may still fail to sign in here: some register
themselves with every server first, or expect to return to an address of
their own scheme such as myapp://. Neither is supported. The first
shows as the error does not support dynamic client registration. The
fix is a token in the header and, in opencode and MiMo Code,
"oauth": false.
Without an MCP client
The server speaks JSON-RPC over HTTP. A tool is not a method of its own: list the
tools with tools/list and call one with tools/call, with
no handshake first:
curl https://api.publicwww.com/mcp \
-H "Authorization: Bearer $PUBLICWWW_TOKEN" \
-H "Content-Type: application/json" \
-d '{"jsonrpc": "2.0", "id": 1, "method": "tools/call",
"params": {"name": "search",
"arguments": {"query": "\"angular.min.js\"", "rows": 5}}}'
The answer carries the result as JSON in structuredContent and as text
in content (read_docs: Markdown text only). More in
Your own code (mcp/developers).
How long access lasts
Until you take it away: tokens and connected apps do not expire. On your profile page, Disconnect an app under Connected apps (it has to ask again) or Delete a token, and access ends at once. Removing PublicWWW in the assistant does not always tell us, so disconnect it here too.
What the assistant gets
All the tools. Only the cluster tools change your account: they create, rename, combine and delete clusters, and extraction spends your points. Searches count against your plan's daily searches as if you ran them yourself. The assistant does not see your email or payments.
Building an application that signs people in? The OAuth flow, the client metadata document and the endpoints are in OAuth 2.1 for applications.
Next Claude