Claude App, claude.ai and Cowork

Warning

Under construction: The time cockpit MCP server and this documentation are under active development, and breaking changes are possible. Tools may be renamed, changed or removed, and dialog labels and configuration steps may change without notice. Check back for updates before rolling the setup out to your users, and expect to adapt your configuration, skills and prompts after an update.

The hosted Claude interfaces (claude.ai, Claude Desktop, Claude Mobile, Cowork) do not use the Claude Code configuration files. Remote MCP servers are added as a custom connector. Custom connectors are available on all plans (Free: one connector). On Team and Enterprise plans an owner creates the connector and members connect to it.

Warning

Review required: This client has not yet been verified end-to-end against the time cockpit MCP server. The steps follow Anthropic's connector documentation; dialog labels may differ between versions.

Add a Custom Connector

Pro / Max (personal):

  1. Open Customize → Connectors and choose Add custom connector.
  2. Name: Time Cockpit. MCP server URL: https://mcp.timecockpit.com — with URL segments if needed, e.g. https://mcp.timecockpit.com/tcTenantId/<tenant-id> or …/access/readonly/scope/owndata. Claude probes the URL and pre-fills detected settings.
  3. Authentication: Sign in now.
  4. OAuth client: Use your own OAuth client, client ID <client-id> of your app registration, leave the client secret empty (public client). Older dialogs: Advanced settings → OAuth Client ID.
  5. Add, then Connect. Sign in with Entra ID; you are redirected to https://claude.ai/api/mcp/auth_callback — this URI must be registered as platform Web on your app registration (see Entra ID Setup).
  6. In a chat, enable the connector for the conversation via + → Connectors.

Team / Enterprise: Only an Owner or Primary Owner can add custom connectors — the Admin role cannot (it covers member management only) — and only in the organization settings, not under Customize → Connectors. Owner: profile menu → Settings → Organization settings → Connectors → Add custom connector, enter the MCP server URL and, under Advanced settings, the client ID. Members then find the connector under Customize → Connectors → Your custom connectors and choose Connect.

Note

If Customize → Connectors shows existing custom connectors but no Add custom connector button, your account is a member (or admin) of a Team or Enterprise organization. Ask an organization owner to add the time cockpit connector, or to promote you to Owner.

Note

Authentication settings (OAuth client, request headers) cannot be changed after a connector has been created. To change them, remove the connector and add it again; members have to reconnect.

Tenant and Modes Without Headers

The connector dialog has a Request headers section (beta, not enabled everywhere), but custom header names such as X-tc-tenant-id have to be approved by Anthropic. This is not necessary: all settings can be passed as URL segments. For the common case of one Entra tenant mapped to one time cockpit tenant, the bare URL is enough because the tenant is resolved from your Entra sign-in.

Alternative for Claude Desktop: Local Bridge with mcp-remote

Claude Desktop additionally starts local stdio servers from %APPDATA%\Claude\claude_desktop_config.json; these are also available in Cowork sessions. With mcp-remote as a bridge you can use headers, your client ID, and a fixed callback port as with Codex. This requires Node.js and is intended for power users.

Warning

Review required: The mcp-remote bridge has not been tested against the time cockpit MCP server.

{
  "mcpServers": {
    "timecockpit": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://mcp.timecockpit.com",
        "--header", "X-tc-tenant-id:<tenant-id>",
        "--static-oauth-client-info", "{\"client_id\":\"<client-id>\"}",
        "64485"
      ]
    }
  }
}