Dailybot for AI agents
DailyBot runs async standups, reminders, and polls inside chat apps, keeping teams updated without adding another meeting to the calendar. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Dailybot.
Submit a check-in update
Submit a check-in for a team's standup, ready for others to review async.
Send kudos to a teammate
Give kudos to a user to recognize their work in front of the team.
Send a message to a channel
Send a message into a chat channel as part of an automated workflow.
6 Dailybot actions, graded by risk.
Every Dailybot action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- dailybot.find_userFind User by UUID
- dailybot.get_usersGet All Users
- dailybot.find_workflowFind Workflow by Name
write
3Create and change things. Allow, or ask the user first.
- dailybot.send_messageSend Message
- dailybot.create_checkinCreate Check-in
- dailybot.give_kudosGive Kudos to Users
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Dailybot in three steps.
- 01Your users connect DailybotThey add their Dailybot api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Check-in” can wait for the user to approve.
- 03Any agent can actYour agent calls Dailybot through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('dailybot', { read: 'allow', write: 'ask', // create_checkin destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Dailybot connects.
Users add their Dailybot api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Dailybot connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Dailybot from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Dailybot and Arc0, answered.
Can I use Dailybot with Claude, ChatGPT or Cursor?
Yes. Connect Dailybot to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Dailybot actions you allow.
How do users connect Dailybot?
Users add their Dailybot api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Dailybot actions can my agent take?
6 in total: 3 read, 3 write and 0 destructive, such as “create Check-in”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Dailybot?
Yes. Allow read actions and deny writes in the Dailybot policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Dailybot too?
Yes. The same Dailybot connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Dailybot into your agent.
Your users connect Dailybot once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan