Connect an AI client
innernet speaks MCP (Model Context Protocol). Anything MCP-aware can read and write your projects with one config snippet. Below: the three most common clients.
You only ever paste a URL. Every client below is configured with just the MCP endpoint — https://innernet.live/api/mcp. On first use the client opens a browser sign-in (OAuth 2.1); you sign in at innernet.live and approve. The client gets a scoped token automatically. You never copy a key by hand, and you should never paste an API key into an AI chat — that path is for the CLI and scripts only (see the bottom of this page).Claude Desktop
Go to innernet.live/connect, click "Connect Claude Desktop", sign in, approve. Claude Desktop receives an OAuth token and installs the MCP server automatically.
Manual install (for advanced users): paste this into your ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"innernet": {
"url": "https://innernet.live/api/mcp",
"transport": "http"
}
}
}Cursor
Open Settings → MCP → Add Server. Use the same URL and the OAuth flow at innernet.live/connect to authorize.
ChatGPT (Deep Research connector)
ChatGPT requires a confidential OAuth client. The /connect flow generates one automatically — you'll see client_id and client_secreton the page exactly once. Paste both into ChatGPT's connector setup.
ChatGPT uses two tools by name: search and fetch. innernet exposes both alongside the regular innernet_* tools.
Cline, Continue, Zed, custom clients
Any MCP-aware client works. Point it at https://innernet.live/api/mcp with a URL-only config — the client runs the OAuth browser sign-in on first use, exactly like the clients above. No key needed.
API keys — CLI & scripts only
The OAuth flow above is the right path for every chat and IDE client. The one exception is non-interactive access — the innernet CLI, cron jobs, CI — where there is no browser to open. For those, mint a long-lived key at /account and send it as Authorization: Bearer innernet_....
Never paste an API key into an AI chat, and if an AI ever asks you for one to "connect innernet," that's wrong — point it at the URL above and let the OAuth sign-in run instead.
Trouble?
Run curl https://innernet.live/api/mcp — you should get JSON back with the tool list. If you get HTML, check that the URL is right. If you get a 401, your token is missing or expired.