mcp_roborest is an MCP server for working with the RoboREST app in Bitrix24.

RoboREST — App builder lets you create Python activities and robots, HTML/JS widgets, cron jobs, and run read-only Bitrix24 REST calls.

🔗 The roborest app is a builder for robots and mini-apps in Bitrix24.
🔗 mcp_roborest is a programmatic interface that lets an AI agent or IDE read, test, create, and update these entities without manually copying code between systems.

Activities: list_activities, get_activity, update_activity, test_activity
— export Python code, edit parameters, test on real CRM data.

Widgets: list_widgets, get_widget, update_widget, test_widget
— edit HTML/JS, update placement, run static checks, and get a placement_url for manual testing in Bitrix24.

Activities and robots: export code, update parameters, test on real CRM entities, debug results.

Widgets: edit HTML/JS, change placement, manual checks in the Bitrix24 interface.

Cron: daily summaries, notifications, scheduled data checks.

Diagnostics: find contact_id, deal_id, product_id via b24_rest_call for tests.

1. Robot finds deals by contact and product — activity takes contact_id and product_id, tested via MCP on real data, then published to a business process.

2. Widget in a CRM tab — load via get_widget, edit, test_widget + manual test via placement_url.

3. Cron sends a daily summary — collects open deals at 09:00, test via test_cron, then activate on schedule.

💾 Keep a local copy of code before major changes.
📝 Put metadata in the file header: id, placement, test parameters.
🧪 Save working testValue for activities right away.
🔍 Use b24_rest_call first to find real data for tests.
✅ After any change: test → publish → verify.

Summary: mcp_roborest is a practical interface for the cycle write → test → publish → verify when building Bitrix24 automations with RoboREST.

Cron: list_crons, get_cron, update_cron, test_cron
— background Python scenarios on a schedule, test runs without waiting for the real cron.

Read-only REST: b24_rest_call
— read CRM data on the connected portal. Write methods (.add, .update, .delete) are blocked.

Activities: list_activities → get_activity → edit locally → test_activity → update_activity

Widgets: list_widgets → get_widget → edit HTML/JS → test_widget → manual test → update_widget

Cron: write code → update_cron → test_cron → check logs → activate on schedule

Dev cycle: write → test → publish → verify.

🔒 b24_rest_call is read-only. Creating or changing entities requires code inside activities/cron or the Bitrix24 UI.

👁️ test_widget does not replace manual testing of appearance and behavior in a CRM tab.

📝 Logs are the main diagnostic source. Add logger to activities and cron from the start.