What problem does it solve?
It lets an agent run a single task against every integration an operator has connected (MCP servers, OpenAPI specs, GraphQL APIs) through one Executor Cloud MCP endpoint, without ever handling credentials, while enforcing per-tool allow, approval, and block policies.
Core Features & Use Cases
- Unified tool catalog discovery: Enumerates the
mcp__executor__* tools exposed by the Executor server each run and maps the task onto them, never assuming an integration exists.
- Policy-governed execution: Honors allow, require-approval, and block outcomes per call, caps runs at 15 calls, and sequences irreversible writes as the final action.
- Structured reporting: Delivers exactly one Markdown notify per run and appends a result-coded log entry (EXEC_OK, EXEC_AUTH_STALE, EXEC_POLICY_BLOCKED, etc.) to the daily memory log.
- Use Case: Ask the agent to list open Linear issues and summarize them by project; it discovers the Linear integration through Executor, calls the tools within policy, and reports the summary plus any pending approvals.
Quick Start
Run this skill with a task such as "list my open Linear issues and summarize by project" after connecting Executor in the dashboard MCP panel.