Runbear vs Tines (2026)

Runbear

by Runbear, Inc.

Tines

by Tines

Pros

• ✓Works in both MCP directions, acting as a client from Slack and exposing its own hosted MCP server for Claude Code, Claude Desktop, Cursor, VS Code, Windsurf and Zed.
• ✓Credit-based pricing with no per-seat charge, so cost tracks usage rather than headcount, and both published tiers list their exact credit allowance.
• ✓Per-user authorization on shared agents plus a SIEM-exportable audit log, and the vendor states plainly that customer data is not used for model training.

Limitations

• ⚠The MCP server is in early access with an expanding tool set, and the vendor states some agent settings remain dashboard-only.
• ⚠The vendor publishes two different integration counts, 2,500+ on its integrations page and 2,000+ in its llms.txt and its own submission, and we could not establish which is current.
• ⚠Independent evidence is thin at one G2 review and seven Product Hunt reviews, with no Capterra or Trustpilot presence, and the SOC 2 Type II report is gated behind a trust center access request.

Pros

• ✓An MCP server on every plan, including Community Edition, exposes workflows to AI clients, and the AI Agent action can also call tools on external MCP servers.
• ✓Language models run by default on Tines-hosted AWS Bedrock infrastructure in the tenant's region, with no training on customer data.
• ✓SOC 2 Type 2, ISO/IEC 27001:2022 and ISO/IEC 42001:2023 for AI management are listed in its public Trust Center.

Limitations

• ⚠Business and Enterprise editions publish no rates, so pricing above the free Community Edition requires a sales conversation.
• ⚠Community Edition is capped at three flows, and each MCP server with connected tools counts as one of them.
• ⚠Cases, Advanced Workflows such as Records and Dashboards, and self-hosting are available only on paid editions.