# Dailybot MCP setup

> Configure the Dailybot remote MCP server in Claude, Claude Code, Cursor, VS Code, or an eligible ChatGPT workspace.

Language: en
Canonical: https://www.dailybot.com/developers/mcp
Markdown: send header `Accept: text/markdown` on any URL to receive Markdown instead of HTML.
Last Updated: 2026-11-17

---

Dailybot's remote MCP server uses Streamable HTTP and browser OAuth. Use `https://mcp.dailybot.com/mcp` as the server URL. The person signing in needs an active Dailybot organization membership and that organization must have MCP access. One authorization selects one person and one organization; tools use that person's current permissions.

## Instructions for a configuring agent

Identify the client's MCP configuration format before editing. Add a `dailybot` server entry without replacing other servers. Use the matching section below. Never request or store a Dailybot API key, JWT, CLI token, or browser session for this connection. Ask the person to complete OAuth in the browser. Report success only after the client shows Dailybot tools and a read request succeeds. Show any drafted write action to the person and wait for approval in the client before sending it.

## Claude (web or Desktop)

Claude uses a remote connector configured in its interface. On a personal plan, open Customize → Connectors and add a custom connector. On Team or Enterprise, an owner first adds it in organization settings. Enter `Dailybot` and `https://mcp.dailybot.com/mcp`; then connect, sign in to Dailybot, and enable the connector in a conversation when needed. Do not paste the Cursor JSON into Claude Desktop's local-server configuration. See [Claude's connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

## Claude Code

Run:

```bash
claude mcp add --transport http dailybot https://mcp.dailybot.com/mcp
```

Open Claude Code and use `/mcp` to complete browser sign-in if it does not start automatically. See [Claude Code MCP documentation](https://code.claude.com/docs/en/mcp).

## Cursor

Add this to `~/.cursor/mcp.json` for all projects or `.cursor/mcp.json` for one project. Preserve any existing `mcpServers` entries. Open Cursor's MCP settings and complete OAuth in the browser.

```json
{
  "mcpServers": {
    "dailybot": {
      "url": "https://mcp.dailybot.com/mcp"
    }
  }
}
```

See [Cursor MCP documentation](https://docs.cursor.com/context/model-context-protocol).

## VS Code with Copilot

In a Copilot session, open Chat: Open Customizations → MCP Servers → Add Server, choose HTTP, enter `https://mcp.dailybot.com/mcp`, choose a Copilot configuration destination, and complete OAuth. For manual configuration, add the following entry to `~/.copilot/mcp-config.json` or workspace-root `.mcp.json`. These files use `mcpServers`; older editor-managed `.vscode/mcp.json` files use a different `servers` format.

```json
{
  "mcpServers": {
    "dailybot": {
      "type": "http",
      "url": "https://mcp.dailybot.com/mcp",
      "tools": ["*"]
    }
  }
}
```

See [VS Code MCP configuration](https://code.visualstudio.com/docs/agents/reference/mcp-configuration).

## ChatGPT

Use ChatGPT on the web in an eligible workspace. Full MCP actions, including writes, require Business or Enterprise/Edu; workspace permissions determine who may create a custom app. An admin, owner, or authorized developer creates an app using `https://mcp.dailybot.com/mcp`, chooses OAuth, signs in to Dailybot, scans the tools, and completes any required workspace review. Select the Dailybot app in the conversation. See [ChatGPT's custom MCP guide](https://help.openai.com/en/articles/12584461-connecting-custom-mcp-servers-in-chatgpt).

## Other clients

If your client supports remote MCP over HTTPS and browser OAuth, add `https://mcp.dailybot.com/mcp` and follow its authentication flow. A client's configuration syntax may differ from the examples above.

## Verify and troubleshoot

With Dailybot enabled in a conversation, ask “What needs me today?” Expect a briefing limited to your access. A saved configuration alone does not prove that OAuth finished or tools are usable.

- `HTTP 503` with “Dailybot MCP is not available right now.”: connection is temporarily unavailable. Try again later. An existing authorization remains if access is paused.
- `HTTP 403` with “Inbound MCP is not enabled for an eligible organization.”: no organization available to this account is enabled for MCP. Check membership and ask your Dailybot administrator about availability.
- `HTTP 401` after connecting: the session may have expired, access may have been revoked, or MCP may be paused. Reconnect if the client asks you to sign in again.
- No Dailybot tools: check that the client enabled the server, OAuth finished, and the organization has MCP access.
- New permissions granted after connecting: reconnect to authorize the additional access.

Writes run as the signed-in person. Review tool actions and approve them in the client when asked; Dailybot does not open a separate approval modal for each action. The live tool list in your client is the authority for what this connection can use. Dailybot MCP covers check-ins, forms, briefings, team pulse, people, kudos, time off, reminders, messages, and automations within your permissions. You can list and create reminders, but cannot edit an existing one. An automation must be active and runnable by you. Company knowledge search is not available through this server.
