Runbear MCP: turn a Claude Code workflow into a team agent

[bwook00]

A Claude Code workflow dies when the session ends.

That is the gap I kept hitting. I can describe the job, wire a couple of tools, and see a good first draft. Then I close the laptop, and none of it is a team agent. There is no durable trigger, no reviewed app connections, and no runtime that keeps posting to Slack or Linear after I am gone.

Runbear MCP is the handoff.

I stay in Claude Code and describe one workflow:

• wait for the meeting to end
• pull the notes from Granola
• post the action items to Slack
• open the matching Linear issues

Runbear MCP returns a reviewable draft: instructions, connections, trigger, output. Nothing is connected or deployed yet. After I approve it, that workflow keeps running in Slack or Microsoft Teams even after the local session is closed.

Demo: https://runbear.io/videos/posts/en/runbear-mcp-claude-code-demo.mp4

claude mcp add --transport http runbear https://api.runbear.io/mcp/cc

Then /mcp → Runbear → browser OAuth → describe the workflow you want to promote.

This is preview. The unresolved design question is the handoff boundary:

Should MCP stop at a reviewable draft, or be allowed to deploy after one explicit approval?

• Demo: https://runbear.io/videos/posts/en/runbear-mcp-claude-code-demo.mp4
• Docs: https://docs.runbear.io/api-reference/mcp-server