Connect your agent
Playhead connects to every MCP client through one URL. On Claude that is a button and a sign-in, with nothing to install and nothing to paste — which is also why it works on a phone. Every other client is either a deeplink or one line in a config file.
Last updated
One-click connect
Claude first, because it is where most people connect and the only route that also covers phones.
Claude CodeOne command in the terminal, then /mcp to sign in.
claude mcp add --transport http playhead https://mcp.tryplayhead.com/mcpNo deeplink exists for the terminal, so this is the install.
- ChatGPTNeeds Developer mode under Settings → Connectors → Advanced first.
CodexAdd the server to Codex's config file.
[mcp_servers.playhead] url = "https://mcp.tryplayhead.com/mcp" auth = "oauth"Append to ~/.codex/config.toml — the CLI, IDE extension and desktop app share it.
- CursorAdds the server to Cursor's MCP settings.
- VS CodeOpens VS Code and adds the server to your MCP configuration.
- LM StudioAdds the server to LM Studio's MCP list.
The server URL
Everything above points at the same address. Paste it wherever a client asks for an MCP server.
HTTP transport
https://mcp.tryplayhead.com/mcp
| Client | How | Notes |
|---|---|---|
| Claude | Web dialog | Web, desktop and mobile. Opens the connector dialog with the URL filled in. |
| Claude Code | Config | One command in the terminal, then /mcp to sign in. |
| ChatGPT | Web dialog | Needs Developer mode under Settings → Connectors → Advanced first. |
| Codex | Config | Add the server to Codex's config file. |
| Cursor | Deeplink | Adds the server to Cursor's MCP settings. |
| VS Code | Deeplink | Opens VS Code and adds the server to your MCP configuration. |
| LM Studio | Deeplink | Adds the server to LM Studio's MCP list. |
Analysing files on your own machine
A server elsewhere has no access to your disk, so the two transports differ here — and only here.
Over stdio, a path works exactly like a link. Pass ~/Movies/cut.mov or ./export.mp4 as the url and the file is uploaded once and reused for every later call, keyed by path, size and modification time — re-export over the same filename and the new cut is uploaded rather than the old one served.
Over the remote HTTP transport, the reply to a local path is the exact command that sends the bytes, carrying an upload ticket that needs no key of its own. Run it wherever the file is and continue with the upl_… id it returns.
claude mcp add playhead -e PLAYHEAD_API_KEY=sk_live_… -- npx -y @playhead/mcpPer-client guides
One page each, because what differs between a terminal with a filesystem and a phone is a real difference.
Questions
- Do I need an API key to connect an agent?
- No. The connect links carry no secret and could not — we store only a hash of each key. The connection authenticates by signing in to your Playhead account instead, which is why these links are safe to share, bookmark or publish.
- Can I use this from Claude on iOS or Android?
- Yes. A remote MCP connector runs on our servers rather than on your device, so once it is added it works everywhere you use Claude — the browser, the desktop app and both mobile apps.
- Why does a connect button sometimes do nothing?
- Deeplinks hand the URL to a local application, and an application that is not installed fails silently. Paste the server URL into that client's MCP settings by hand instead.
- Can one account be connected to several clients at once?
- Yes. The connection is attached to you rather than to a machine, so adding Cursor after Claude costs nothing and both spend from the same balance.