Skip to main content
Was this helpful?

Connecting MCP Hosts

This page shows practical connection patterns for PrimeCal MCP with the Alex Example demo user, using a manually-generated static agent API key (ag_sk_...).

If your AI assistant instead offers a Connect or Add connector button and supports OAuth, use Connecting via OAuth instead — it reaches the same MCP server without copying a key by hand.

All sample outputs on this page come from the fictional example user Alex Example; your output will show your own data.

Connection Modes​

PrimeCal's MCP server uses Streamable HTTP at https://api.primecal.eu/api/mcp. Use one agent API key per host instance.

Do not point MCP hosts at https://app.primecal.eu/api/mcp — that host serves the web app, not the API.

Chrome MCP (HTTP)​

Use this when your Chrome MCP extension/bridge supports remote HTTP MCP servers.

Before generating the host config in PrimeCal, choose the narrowest permission group that fits the host:

  • Minimal for smoke tests and context-only assistants
  • All read-only for browsing calendars, tasks, reservations, and automation state safely
  • Operational read/write only when the host must create or update planning data
  1. Open your Chrome MCP host settings.
  2. Add a server named primecal.
  3. Set endpoint URL to https://api.primecal.eu/api/mcp.
  4. Add header Authorization: Agent ag_sk_<token>.
  5. Save and reconnect.
  6. Run tools/list, then call primecal_calendars_list.

Example JSON block used by many Chrome MCP tools:

{
  "name": "primecal",
  "transport": "http",
  "url": "https://api.primecal.eu/api/mcp",
  "headers": {
    "Authorization": "Agent ag_sk_your_token_here"
  }
}

If your extension uses a different field name (endpoint, serverUrl, authHeaders), keep the same values but map them to that UI.

PrimeCal may also emit a non-sensitive permissionGroup annotation in its generated config. Treat that as operator-facing metadata only. The host should still rely on the explicit scoped MCP capabilities returned by PrimeCal.

Claude Desktop, VS Code, or Cursor​

These hosts connect the same way as Chrome MCP: as a remote HTTP MCP server, using your agent API key. There is no local install step — PrimeCal's MCP server is the hosted one at api.primecal.eu, the same server every other host connects to.

Use the same values as Chrome:

  • URL: https://api.primecal.eu/api/mcp
  • Auth header: Authorization: Agent ag_sk_<token>

Claude Code uses the same remote HTTP transport shape:

{
  "primecal": {
    "type": "http",
    "url": "https://api.primecal.eu/api/mcp",
    "headers": {
      "Authorization": "Agent ag_sk_your_token_here"
    }
  }
}

Start validation with:

  1. tools/list
  2. primecal_profile_get
  3. primecal_context_snapshot

Validation Checklist (Alex Example)​

After connecting, verify:

  • primecal_profile_get returns timezone: Europe/Budapest.
  • primecal_calendars_list includes Work, Personal, Side projects.
  • primecal_tasks_list returns seeded tasks.
  • tools/list matches the permission group you selected. For example, an All read-only host should not see create, update, delete, or trigger-only tools.