Guide
Connect Claude Code
Link PromptCache to Claude Code with OAuth
MCP URL
https://api.promptcache.app/api/mcp
Connect PromptCache to Claude Code so Claude can list, edit, render, and publish prompts in your workspace, using secure sign-in, not copy-pasted API keys.
Before you start
- A PromptCache account with at least one workspace
- Claude Code installed on your machine
The MCP URL for PromptCache is shown at the top of this page. Copy it when adding the server in Claude Code.
Connect in Claude Code
- In Claude Code, add a remote HTTP MCP server and paste the MCP URL from above.
- On first use, Claude opens your browser to sign in to PromptCache.
- Choose the workspace Claude should access, then click Allow access.
- Claude stores access tokens automatically. You do not paste secrets into config files.
After a successful connection you receive an in-app notification and email with links back to these guides.
Example: add from the terminal
claude mcp add --transport http promptcache https://api.promptcache.app/api/mcpClaude discovers OAuth settings from the server, no extra auth configuration is required.
What Claude can do
Default permissions include reading and writing prompts in the workspace you selected:
| Scope | Allows |
|---|---|
mcp | Connect to the MCP server |
prompts:read | List, read, render, and preview prompts |
prompts:write | Create, update, delete, publish, and fork prompts |
Available tools
Tools are named with a promptcache_ prefix, for example:
promptcache_list_prompts, browse prompts in your workspacepromptcache_get_prompt, read the live draftpromptcache_render_prompt, fill in variables and get rendered text (not an LLM call)promptcache_publish_prompt, save a published version snapshot
See Using MCP in Claude for practical tips on working with these tools.
Troubleshooting
| Problem | What to try |
|---|---|
| Browser does not open for sign-in | Confirm you are signed in at promptcache.app, then retry in Claude Code |
| Wrong workspace | Disconnect the MCP server and connect again; pick the correct workspace on the consent screen |
| 401 / access denied after connecting | Disconnect and reconnect; tokens may have been revoked |
| Claude cannot find a prompt | Check you connected the workspace where the prompt lives |
Next steps
- Using MCP in Claude, render vs publish, tool tips, and good prompts for Claude
- Prompts API, same operations over HTTP
