Runbear

Build and deploy AI agents to Slack from Claude Code, Codex, or Cursor - manage instructions, 2,000+ app integrations, triggers, and knowledge bases.

View on runbear.ioTry this MCPSponsored

Documentation

Runbear

Toggle Menu

Get StartedBook a Demo

Runbear MCP · Preview

Set it up from your coding client. Runbear keeps it running.

Install the Runbear MCP server once, then describe the workflow in Claude Code, Codex, or Cursor. Runbear drafts the trigger, the apps, and the output for your review. After you deploy it, it runs for your team.

OAuth in your browserThree coding clientsReview before deployment

Claude Code example showing Runbear drafting an agent

Claude Code example

Runbear MCP

>

When a Zoom meeting ends, wait 5 minutes, pull the notes from Granola, post the action items to #product-sync, open a Linear ticket for each one, and mention the owner.

runbear drafted a new agent configuration.

Meeting follow-up — review next

·Trigger Zoom meeting ends, then 5 min

·Apps Granola · Slack · Linear

·Output Slack recap and assigned Linear tickets

Drafted→You review→Runs in Runbear, every time

Nothing connected or deployed yet

>

Start with one MCP connection

Connect Runbear to your coding client

Choose the client you already use, run its install step, and complete OAuth in the browser.

Claude CodeCodexCursor

Claude Code

Requires remote HTTP MCP support.

Preview

Install commandCopy

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

1

Connect

Run the command in the project where you want Claude Code to use Runbear.

2

Authenticate

Run /mcp, select Runbear, and complete OAuth in the browser. Runbear uses your only or saved default organization.

3

Verify

/mcp should show Runbear as connected. You can also inspect the server from your terminal.

Verification commandsCopy

claude mcp list
claude mcp get runbear

Remove the local connection

OAuth without pasted API tokens

The first Runbear action opens a browser window. Sign in and return to your coding client. Runbear uses your only organization or saved MCP default, and you never paste a Runbear API token into chat.

If your account belongs to multiple organizations and OAuth cannot resolve a saved MCP default, contact Runbear Support before retrying.

Tied to your Runbear account

Bound to your only or saved default organization

No API token pasted into chat

Starter prompt keeps deployment out of scope

Create a review-first agent

The starter prompt asks your coding client to draft the instructions and propose the app connections, schedule, and output. It shows the complete configuration without connecting apps, creating triggers, or deploying.

First agent promptCopy

Create a new Runbear agent named Weekly Standup.

Draft instructions that collect team updates and summarize blockers.
Propose the app connections, weekly schedule, and output this agent would need.
After creating it, show me the complete configuration and recommendations.

Do not connect apps, create triggers, or deploy it yet.

Already have a Claude Code project?

Runbear Agent Skills deploys an existing Claude Code project into a hosted Agent SDK agent. It does not connect that agent to Slack automatically.

View Agent Skills

Start from the outcome

Describe work your team already does

Runbear turns the request into a draft blueprint: when the agent should run, which apps it needs, and what it should produce. You review each decision before connecting or deploying it.

Draft first

Meeting follow-up

Turn every meeting into assigned work nobody has to write up.

Trigger

Zoom meeting ends, then 5 min

Apps

Granola · Slack · Linear

Output

Slack recap and assigned Linear tickets

Draft first

Support triage

Turn new support conversations into a reviewable action plan.

Trigger

New Zendesk ticket

Apps

Zendesk · Slack

Output

Triage summary and draft reply

Draft first

Operations briefing

Give operators the context they need before deciding what to do.

Trigger

Weekdays at 9:00

Apps

Notion · Slack

Output

Team briefing with open decisions

What the first draft should show

Runbear appears connected in /mcp

OAuth returns you to Claude Code

The response presents Weekly Standup as undeployed

Claude Code shows the draft instructions and complete configuration

Proposed app connections, weekly schedule, and output are ready to review

You decide what goes live

  1. 1.Review the instructions and recommendations
  2. 2.Connect an approved app
  3. 3.Create the approved trigger or schedule
  4. 4.Run a test
  5. 5.Ask the client to deploy when ready

Turn the draft into a working agent

When the blueprint looks right, use the MCP reference to connect apps, create triggers, test the workflow, and deploy. It also documents permissions, traces, security, and limitations.

Tools and scopesAuthentication and permissionsLimitationsTroubleshooting

Start with the install commandRead the MCP reference

Runbear

Building with ❤️ from SF
128 King St.
San Francisco, CA 94107

© Runbear, Inc. 2026

GitHubTwitterLinkedInDiscordSlack

Product

Resources

Company