list_agentsLABSCO SUMMARY
verify_app_to_agent is the tool that stops the classic failure: an agent shipped with a connection that was never actually working.
Attaching an app and having the attachment work are two different things, and the gap usually surfaces in front of the whole channel. A verification step in the tool set means the wiring is checkable before deployment rather than after. Pair it with inspect-runs: building an agent conversationally is fine, but you need the execution traces to find out why it answered the way it did. Note the credit-based platform pricing — the endpoint is not billed separately during early access, but the runs are.
What it is
Runbear builds agents that live where your team works. The endpoint lets you create those agents, attach apps and contexts to them, and put them into a Slack channel — which is where they run.
What you get
- Agents — list, get, create, update, plus a personal agent
- Contexts — create, update, delete the knowledge an agent draws on
- Apps and tools — search apps, attach, connect to an agent and verify the connection, list an agent's tools, detach one
- Triggers — list, get, create an external trigger, schedule a job, update or delete
- Deployment and operations — deploy to Slack including joining channels, run on demand, and inspect recent execution traces
Requirements
OAuth. The connection is scoped to your organisation and least-privilege by their description, and can be disconnected at any time. The endpoint is in early access, with the tool set still expanding.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Assembling an agent
Create it, give it context, attach the apps it needs.
02
Checking the wiring before it goes live
Verify the app-to-agent connection rather than discovering it in the channel.
03
Putting it in front of the team
Deploy to Slack and join the channels.
04
Making it run on its own
External triggers and scheduled jobs.
05
Working out what it did
Read the recent execution traces.
24 tools
Listed in project docs. Your client may show a different list.
get_agentcreate_agentupdate_agentget_personal_agentlist_contextscreate_contextupdate_contextdelete_contextsearch_appsattach_applist_agent_toolsdetach_toolconnect_app_to_agentverify_app_to_agentlist_triggersget_triggercreate_external_triggercreate_scheduled_jobupdate_triggerdelete_triggerdeploy-to-slack (install agent, join channels, go live)run-on-demand (triggers/schedules)inspect-runs (recent execution traces)BEFORE YOU INSTALL
What to know first
Tools you get
24 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.0 — the connection is tied to your user account and scoped to your organisation
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://api.runbear.io/mcpRequirements
- OAuth 2.0 — the connection is tied to your user account and scoped to your organisation
