Connect a client

Add Daybook's MCP server to Claude, Claude Desktop, Claude Code, Cursor, VS Code or your own agent, with a token that acts as you.

Daybook's MCP server speaks streamable HTTP at one URL. Every client sends a credential with each request; Daybook takes the workspace and the person from it, so there is nothing else to configure.

https://mcp.daybookhealthcare.com/mcp

Credentials

Use an assistant token for a person's own AI app: what Claude does shows under that person's name. Use a secret key for an agent that runs on your servers with no person behind each request. Make one token per app, so revoking the laptop leaves the phone working. A token is shown once and Daybook keeps only its hash; revoke it from the same page and the app using it stops at once.

Claude Code

claude mcp add --transport http daybook https://mcp.daybookhealthcare.com/mcp \
  --header "Authorization: Bearer rcm_mcp_..."

Add --scope user to have it in every project. /mcp in Claude Code shows the server and its tools; the playbooks appear as slash commands, such as /mcp__daybook__work_a_denial.

Claude and Claude Desktop

Claude takes a custom connector by URL alone, so the token goes in the URL as its last path segment.

1. Open the connectors

   In Claude, on the web or in the desktop app, open Settings → Connectors and choose Add custom connector.

2. Paste the URL with your token
   textCopy

   https://mcp.daybookhealthcare.com/mcp/rcm_mcp_...

3. Turn it on in a chat

   Open the tools menu in a chat and switch Daybook on. Claude asks before it runs a tool that writes, unless you allow it always.

A URL with a token in it is a password and can appear in request logs, so give it a token of its own. To keep the token out of the URL in Claude Desktop, bridge with mcp-remote in claude_desktop_config.json instead:

{
  "mcpServers": {
    "daybook": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.daybookhealthcare.com/mcp",
               "--header", "Authorization: Bearer ${DAYBOOK_TOKEN}"],
      "env": { "DAYBOOK_TOKEN": "rcm_mcp_..." }
    }
  }
}

Cursor

Add the server to ~/.cursor/mcp.json, or to .cursor/mcp.json in one project:

{
  "mcpServers": {
    "daybook": {
      "url": "https://mcp.daybookhealthcare.com/mcp",
      "headers": { "Authorization": "Bearer rcm_mcp_..." }
    }
  }
}

VS Code

Add it to .vscode/mcp.json; VS Code asks for the token once and keeps it in its secret store:

{
  "inputs": [
    { "type": "promptString", "id": "daybook-token", "description": "Daybook assistant token", "password": true }
  ],
  "servers": {
    "daybook": {
      "type": "http",
      "url": "https://mcp.daybookhealthcare.com/mcp",
      "headers": { "Authorization": "Bearer ${input:daybook-token}" }
    }
  }
}

Your own agent

An agent you run, on the Claude Agent SDK or any MCP client library, connects the same way with a bearer header. On a server, use a secret key from your secrets manager.

import { query } from "@anthropic-ai/claude-agent-sdk";

for await (const message of query({
  prompt: "Work the denials queue: for each claim, say why it was denied and the next step.",
  options: {
    mcpServers: {
      daybook: {
        type: "http",
        url: "https://mcp.daybookhealthcare.com/mcp",
        headers: { Authorization: `Bearer ${process.env.DAYBOOK_API_KEY}` },
      },
    },
    allowedTools: ["mcp__daybook__worklist", "mcp__daybook__get_claim", "mcp__daybook__list_denials"],
  },
})) {
  if (message.type === "result" && message.subtype === "success") console.log(message.result);
}

Other clients

A client that takes a header sends Authorization: Bearer <token> to the URL. A client that takes only a URL uses the token as the last path segment, as Claude does.

When it does not connect