Control Deskgram 2 through MCP

Control Deskgram 2 through MCP

Connect an AI agent to the running Deskgram 2 app through a local MCP endpoint. Read accounts and module schemas, validate task parameters, create tasks and retrieve their results.

Module settings

Open Settings → MCP, set a token, enable the listener and save. The default endpoint is http://127.0.0.1:8765/mcp; use Authorization: Bearer <token>. In OpenCode, configure mcp.deskgram with type: remote, url, headers and enabled: true. Use the token from Settings, not the placeholder returned by deskgram_get_mcp_instructions. The client must reach the same computer; a cloud agent cannot reach your app through its own localhost. Keep Deskgram running. The current 17 tools are deskgram_health, deskgram_echo, deskgram_get_mcp_instructions, deskgram_list_modules, deskgram_get_module_schema, deskgram_get_profile_setup_schema, deskgram_list_accounts, deskgram_list_account_folders, deskgram_get_account, deskgram_get_account_limits, deskgram_list_tasks, deskgram_get_task, deskgram_create_task, deskgram_stop_task, deskgram_validate_batch, deskgram_create_batch and deskgram_validate_account. Query tools/list for current argument schemas. Detailed contracts exist for profile_setup.validate_account, search_channels_groups and collect_audience. Other allowed modules may use generic_adapter. Set allowed_modules and account/input-recipient limits. Scheduler is not supported through create_task; direct account moves, archiving, updates and limit resets are blocked.

Check before running

Start with health, echo and tools/list. POST JSON-RPC is supported; authenticated GET /mcp returns 405 and there is no separate SSE stream. Client compatibility requires its own check. Dry-run defaults to on and validates structure, actions and limits, without testing Telegram sessions, proxies or chat access. Real creation requires allow_dangerous_tools=true and dry_run=false; execute=false is not supported for creation. Save task_id and query deskgram_get_task with include_result=true: task completion does not mean every account succeeded. Check the task list before retrying after a disconnect, since creation has no idempotency-key. Stop uses deskgram_stop_task without dangerous-mode. Local HTTP and contracts were tested in isolation; live account execution and compatibility with every client are not claimed.

Related tasks and guides

Choose a related task or open the detailed guide. Linked Russian guides are marked accordingly.

More Deskgram 2 modules