Set Up WCP with Claude Code
Get connected in about 5 minutes.
Prerequisites
- Claude Code CLI installed (install guide)
- A terminal application
- A WCP Cloud account (you'll create one in Step 1)
Sign Up for WCP Cloud
Go to workcontextprotocol.io/login and enter your email address.
Check your inbox for an email from WCP Cloud and click the login button.
You're logged in and can see your dashboard.
Get Your Connection URL
Go to Settings and find your MCP connection URL.
You have your MCP connection URL.
Configure Claude Code
Open your terminal and run this command:
That's it — one command and you're connected.
The command completed without errors.
Verify It Works
Start a new Claude Code session and ask Claude to run wcp_namespaces. You should see your default namespace listed.
Claude shows your namespaces. You're all set!
Remote & Headless Environments
If you're running Claude Code in a remote environment where you can't open a browser — like zo.computer, GitHub Codespaces, or an SSH session — skip Steps 1–2 above. Instead:
Add the MCP server without auth
Run this in your terminal:
Trigger the device code flow
Start Claude Code and try any tool call (e.g. ask Claude to run wcp_namespaces). Claude will show you a message like:
Activate on any device
Open workcontextprotocol.io/activate on any device — your phone, a laptop, anything with a browser. Enter the code and your email address, then click Connect Device.
Run the connection command
After activating, you'll see a claude mcp add command with your auth token included. Copy it and run it in your remote terminal. This replaces the unauthenticated connection from Step 1.
Try wcp_namespaces again — you should see your namespaces.
The code expires in 15 minutes. If it expires, just try another tool call and you'll get a fresh code.
Troubleshooting
"Connection refused" or timeout
Make sure the URL is exactly https://workcontextprotocol.io/mcp. Check your internet connection and try again.
"Unauthorized" or token error
Your connection may have expired. Log in at Settings and check your MCP connection URL. Make sure your email is verified.
"No tools found"
Restart your platform after adding the MCP connector. Most platforms need a full restart (not just a new conversation) to pick up new MCP servers.
Tool calls return errors
Check that your email is verified. Go to Settings to confirm your verification status. Unverified accounts can connect but cannot use tools.
Can't open a browser on this machine
Add the MCP server without auth and try a tool call — you'll get a device code to activate from any other device (phone, laptop). See the Remote & Headless Environments section of the Claude Code guide.
wcp_namespaces returns empty
This is normal for brand new accounts. A default namespace was created when you signed up. Try asking your AI assistant to call wcp_namespaces — you should see at least one namespace listed.
Using a different platform?