Context Repo DocsOther MCP Clients
Connect Context Repo to any MCP-compatible client using stdio, SSE, or Streamable HTTP transport. This guide covers the generic setup for clients not listed in our specific guides.
Context Repo works with any client that supports the Model Context Protocol. If your client isn't covered by our Cursor, Claude Desktop, VS Code, or Windsurf guides, use one of the three transport options below.
Transport options
Context Repo supports three ways to connect:
| Transport | URL / Command | Best for |
|---|---|---|
| Streamable HTTP (recommended) | https://contextrepo.com/mcp | Remote clients, no local install needed |
| SSE (legacy) | https://contextrepo.com/sse | Clients that don't support Streamable HTTP yet |
| stdio (local) | npx -y context-repo-mcp | Local-first clients, offline-capable |
Which should you pick? Streamable HTTP is the recommended transport — it's the simplest to configure and doesn't require Node.js on your machine. Use stdio if your client only supports local servers, or SSE if your client specifically requires Server-Sent Events.
Streamable HTTP setup (recommended)
Get your API key
Go to Dashboard > Settings > API Keys and click Create API Key. Select the prompts.read and documents.read permissions, then copy the generated key.
Configure your client
Point your MCP client at the Streamable HTTP endpoint:
https://contextrepo.com/mcpSet the Authorization header to your API key:
Authorization: Bearer cr_your_api_key_hereThe exact configuration depends on your client. Here's a generic JSON config example:
{
"mcpServers": {
"context-repo": {
"url": "https://contextrepo.com/mcp",
"headers": {
"Authorization": "Bearer cr_your_api_key_here"
}
}
}
}Replace cr_your_api_key_here with your actual API key.
Verify the connection
Ask your AI assistant:
List my promptsYou should see your Context Repo prompts listed. If you haven't created any yet, the assistant will tell you the list is empty — that still confirms the connection is working.
SSE setup
Get your API key
Go to Dashboard > Settings > API Keys and click Create API Key with prompts.read and documents.read permissions.
Configure your client
Point your MCP client at the SSE endpoint:
https://contextrepo.com/sseSet the Authorization header to your API key:
Authorization: Bearer cr_your_api_key_hereGeneric JSON config example:
{
"mcpServers": {
"context-repo": {
"url": "https://contextrepo.com/sse",
"headers": {
"Authorization": "Bearer cr_your_api_key_here"
}
}
}
}Verify the connection
Ask your AI assistant to list your prompts or documents to confirm the connection works.
stdio setup (local)
Install Node.js
The stdio transport runs the MCP server locally. You'll need Node.js 18 or later installed on your machine.
node --version
# Should print v18.x.x or higherGet your API key
Go to Dashboard > Settings > API Keys and click Create API Key with prompts.read and documents.read permissions.
Configure your client
Set up your client to run the Context Repo MCP server via npx:
- Command:
npx - Arguments:
-y context-repo-mcp - Environment variable:
CONTEXTREPO_API_KEYset to your API key
Generic JSON config example:
{
"mcpServers": {
"context-repo": {
"command": "npx",
"args": ["-y", "context-repo-mcp"],
"env": {
"CONTEXTREPO_API_KEY": "cr_your_api_key_here"
}
}
}
}Replace cr_your_api_key_here with your actual API key.
Verify the connection
Ask your AI assistant:
List my promptsIf you see your prompts (or an empty list confirmation), the connection is working.
Troubleshooting
Server not starting (stdio)
Make sure Node.js 18+ is installed and npx is available on your system PATH. If you're using nvm, switch to a supported version with nvm use 18.
Authentication errors
Double-check that your API key is correct and hasn't been revoked. Generate a new key from Dashboard > Settings > API Keys if needed. Ensure there are no extra spaces or line breaks in your key.
Connection refused (HTTP/SSE)
Verify that your client can reach https://contextrepo.com. Check for proxy or firewall settings that might block outbound HTTPS connections.