Run tasks across your connected tools

Executor MCP is an aeon skill: Run a task through your Executor Cloud tool catalog - one MCP endpoint proxying every integration you connected (MCP servers, OpenAPI specs, GraphQL APIs), with per-tool allow/approve/block policies. OAuth Connect via the dashboard MCP panel. Like every aeon skill it is one SKILL.md prompt file that runs unattended on your own GitHub Actions, on a schedule or when you trigger it, and sends what it finds to Telegram, Discord, Slack or email.

Execute one task through Executor Cloud (executor.sh/mcp) - a proxy that fronts every integration the operator connected (upstream MCP servers, OpenAPI specs, GraphQL endpoints) as a single tool catalog. Credentials live in Executor and are attached upstream per call; this agent never sees them. Every call is governed by a per-tool policy: allow, require approval, or block.

Every aeon skill takes one optional text input, var, set in aeon.yml or typed in when you run it by hand. It picks the target or the mode for that run.

The task to run against the Executor catalog, e.g. list my open Linear issues and summarize by project or what integrations are connected?. Required. If empty, log EXEC_NO_TASK and exit cleanly (no notify).

Besides the model you connected to aeon, Executor MCP uses the following. Add secrets as GitHub Actions secrets on your aeon repo, or in Aeon Connect.

• executor MCP server - required, connect it once from the dashboard MCP panel (OAuth)

Easiest: open Aeon Connect, sign in with GitHub and turn on Executor MCP. No clone, no terminal. To add it to an existing aeon repo from a shell, run:

Then switch it on in aeon.yml (the default schedule is filled in):

skills:
  executor-mcp: { enabled: true, schedule: "workflow_dispatch", var: "" }

New to aeon? Read the docs for how skills, schedules and memory fit together, or browse all skills.