MCP server (connect your AI assistant)

CHAMPREP hosts a remote Model Context Protocol (MCP) server. Connect it to an MCP-capable AI client — Claude, Claude Code, Cursor, VS Code, and others — and your assistant can act on your CHAMPREP account: list and book calendar events, read and draft mail, manage work boards, search your drive, create invoices, and more, all by conversation.

There is nothing to install for modern clients. The server is hosted at:

Environment	Endpoint
Production	https://ai-api.champrep.com/mcp
Test	https://test-ai-api.champrep.com/mcp

1. Create an API key

Your assistant authenticates with a CHAMPREP API key.

1. Sign in at champrep.com and open Account → API Keys.
2. Create a key and select its scopes — these decide which tools your assistant can use. calendar:read exposes read-only calendar tools; calendar:write also exposes tools that create or change events. Grant only the services you want the assistant to reach.
3. Copy the key (cpk_live_…). It is shown once.

The key acts as you: everything the assistant does is bounded by your own plan, your organization’s policies, and the scopes you chose. Keys can be revoked at any time from the same page.

2. Connect your client

Claude Code

claude mcp add --transport http champrep https://ai-api.champrep.com/mcp \
  --header "Authorization: Bearer cpk_live_YOUR_KEY"

Cursor, VS Code, Windsurf

Add to the client’s MCP configuration:

{
  "mcpServers": {
    "champrep": {
      "url": "https://ai-api.champrep.com/mcp",
      "headers": { "Authorization": "Bearer cpk_live_YOUR_KEY" }
    }
  }
}

Claude Desktop and other stdio-only clients

Clients that only launch local MCP servers can use the official bridge — a tiny relay to the hosted endpoint (requires Node 18+):

{
  "mcpServers": {
    "champrep": {
      "command": "npx",
      "args": ["-y", "@champrep/mcp"],
      "env": { "CHAMPREP_API_KEY": "cpk_live_YOUR_KEY" }
    }
  }
}

3. Try it

Ask your assistant things like:

• “What’s on my CHAMPREP calendar this week?”
• “Draft a reply to the latest email in the support mailbox.”
• “Create a work ticket for the onboarding bug and assign it to me.”
• “Find the Q3 proposal in my drive and summarize it.”

What the assistant can and cannot do

• Acts only as you. Every tool call runs with your identity — the same tenancy, plan limits, and organization rules as when you use CHAMPREP yourself.
• Scope-limited. A key without mail:write never exposes mail-sending tools to the assistant, and your per-service AI permissions (AI settings in your account) apply as well.
• No destructive tools. Deletes and other irreversible operations are not exposed over MCP.
• Your AI, your tokens. MCP does not consume CHAMPREP AI credits — the reasoning model is your own AI client’s.

Troubleshooting

Symptom	Fix
401 / “Missing credentials”	The Authorization: Bearer cpk_… header is absent or the key was mistyped.
“Invalid API key”	The key was revoked, expired, or belongs to the other environment (test vs production).
Tools are missing	The key’s scopes exclude that service, or the service is disabled in your AI permission settings.
429 rate limit	The assistant is looping; retry after a minute.

Questions? Contact support.