Dailybot MCP setup
Connect Dailybot to a remote MCP client with browser OAuth. Follow setup for Claude, Claude Code, Cursor, VS Code, or an eligible ChatGPT workspace.
Dailybot is a remote MCP server. You add one URL in your assistant, sign in to Dailybot in the browser, pick one organization, and the assistant works as you.
Configuring this for a coding agent? Copy the Markdown guide above and ask the agent to follow the section for your client. You complete the browser sign-in; the agent should not request or store your credentials.
Product overview · Create a Dailybot account
https://mcp.dailybot.com/mcp This is the only production URL. Never use api.dailybot.com here.
Rules that keep the connection correct
- Display name in the client: Dailybot.
- Auth is browser sign-in (OAuth). Do not paste an API key, JWT, or CLI token into the MCP client.
- A connection belongs to one person and one organization. Tool calls use that person’s current Dailybot permissions.
- Write actions run as you. Review the action and confirm in the client when asked. Dailybot does not open a separate approval modal for each action.
- Client menus change. This URL does not.
What you need
- A Dailybot account and an active membership in an organization with MCP access.
- An MCP client that can add a remote HTTPS server and complete OAuth in the browser.
Connection flow
- Add a remote MCP server named Dailybot.
- Paste https://mcp.dailybot.com/mcp.
- When the browser opens, sign in to Dailybot, pick one organization, allow the connection.
- Return to the assistant. If it asks you to enable the Dailybot connector for that chat, turn it on.
Setup by client
Choose your client below. The server URL stays the same, but configuration files, sign-in steps, and client availability differ.
{
"mcpServers": {
"dailybot": {
"url": "https://mcp.dailybot.com/mcp"
}
}
}{
"mcpServers": {
"dailybot": {
"type": "http",
"url": "https://mcp.dailybot.com/mcp",
"tools": ["*"]
}
}
}claude mcp add --transport http dailybot https://mcp.dailybot.com/mcphttps://mcp.dailybot.com/mcpClaude (claude.ai and Claude Desktop)
- On a personal Claude plan, open Customize → Connectors and add a custom connector. On Team or Enterprise, an owner first adds the connector in organization settings.
- Enter Dailybot as the name and https://mcp.dailybot.com/mcp as the remote URL.
- Connect and sign in to Dailybot. In a conversation, enable Dailybot under Connectors when needed.
ChatGPT
- Use ChatGPT on the web in an eligible workspace. Full MCP actions, including writes, require Business or Enterprise/Edu; workspace permissions control who can create a custom app.
- An admin, owner, or authorized developer creates a custom app and enters https://mcp.dailybot.com/mcp.
- Choose OAuth, complete Dailybot sign-in, and let ChatGPT scan the tools. The workspace admin reviews access and publishes the app when required.
- Select the Dailybot app in a conversation before asking it to use your data.
Cursor
Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project). Open Cursor’s MCP settings and complete OAuth in the browser.
{
"mcpServers": {
"dailybot": {
"url": "https://mcp.dailybot.com/mcp"
}
}
}VS Code
In a Copilot session, open Chat: Open Customizations → MCP Servers → Add Server, choose HTTP, enter the URL, and finish OAuth. For manual Copilot configuration, use the JSON below in ~/.copilot/mcp-config.json or a workspace-root .mcp.json. The older .vscode/mcp.json uses a different format.
{
"mcpServers": {
"dailybot": {
"type": "http",
"url": "https://mcp.dailybot.com/mcp",
"tools": ["*"]
}
}
}Claude Code
Run this command. Open Claude Code and use /mcp to complete browser sign-in if it does not start automatically.
claude mcp add --transport http dailybot https://mcp.dailybot.com/mcpAny other MCP client
If the client supports remote MCP over HTTPS and browser OAuth, add the URL and follow that client’s authentication flow.
https://mcp.dailybot.com/mcpNever paste credentials
Check that it worked
In a new chat, with Dailybot connected, ask:
What needs me today?Expect a briefing limited to your access. If Dailybot tools are unavailable, check that the client enabled the server, OAuth finished, and your organization has MCP access. A saved configuration alone does not verify a connection.
If sign-in fails
- Do not retry with an API key. MCP only signs in through the browser.
- HTTP 503 with “Dailybot MCP is not available right now.” means MCP is temporarily unavailable for connection. Try again later. An existing grant remains in place if access is paused.
- HTTP 403 with “Inbound MCP is not enabled for an eligible organization.” means no organization available to this account is enabled for MCP. Check your membership and ask your Dailybot administrator about availability.
- A 401 after connecting can mean the session expired, access was revoked, or MCP was paused. Reconnect if your client asks you to sign in again.
- If new permissions were granted after you connected, reconnect to authorize the additional access.
What the assistant can do
The tool list in your client shows 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.