Integrations
Bots reach your tools through MCP servers and app connections, and each bot only gets the tools its job needs.
MCP servers
Koshra speaks the Model Context Protocol. Add an MCP server to a bot and its tools appear for that bot, under the same Allow, Ask and Block rules as everything else.
App connections
App connections give bots access to services such as Slack, email and a CRM. Connections are locked down per bot: a bot only gets what its role needs.
Email and Slack
Bots can draft email and Slack messages. Anything outbound waits for your approval.
CRM and project tracker
Bots can read and update your CRM and project tracker. Deletes and merges are blocked, and bulk changes need approval.
App catalog
MCP and app-connection adapters are implemented. A catalog row, including Salesforce, Zendesk, Jira or Microsoft Teams, does not mean that app is connected or tested. Each connection needs setup, permission review and validation.
Cloud computers
Bots currently use shared cloud computers, with distinct home paths. Dedicated per-bot computers and fully validated live viewing are coming soon. Full supervisor restart and reconnection acceptance is unfinished.
On the way Coming soon
- A validated visible browser for each bot
- Mac OS-enforced sandboxing
- X (Twitter) sign-in for bots
Also as Markdown for AI agents.
Last updated