Why it matters
Running multiple AI agents against a company's tools means wiring each agent to each tool separately. Every new agent duplicates the setup, and every credential lives in a different config. Executor collapses that into one catalog and one connection.
The big picture
Executor is an MCP gateway. Any MCP-compatible agent, including Claude Code, Cursor, and Codex, points at one Executor endpoint and reaches every tool you have connected. Sources can be OpenAPI specs, GraphQL schemas, existing MCP servers, or Google Discovery documents. If it can be represented with a JSON schema, it can be an integration, per the README.
How it works
An agent sees exactly one tool called execute. When the agent calls it, Executor runs a search against your tool catalog, loads only the matching tool's schema, and runs the code in an isolated JavaScript sandbox. Credentials are resolved host-side and attached to the outbound request only. They never enter the sandbox heap or the model context at all. That is not a policy assertion. It is a structural constraint of the architecture.
By the numbers
The context efficiency argument is concrete and sourced from executor.sh directly. Connecting GitHub (720 tools), Stripe (510), Jira (240), Sentry (170), Linear (130), Gmail (95), Notion (80), and Slack (70) without Executor gives the model 1,640 tools consuming roughly 278,800 tokens. With Executor, the model sees 1 tool consuming roughly 1,044 tokens. That is a 99.6% reduction in tool-related prompt overhead.
Zoom in
Safety semantics travel with each tool. Executor preserves the verb meaning it imported: GET vs DELETE for OpenAPI, destructiveHint for MCP, mutations for GraphQL. Agents auto-run the safe operations and pause for human approval before the destructive ones. The guardrails apply uniformly regardless of which surface calls the tool.
At a glance
The repo had 2,349 stars and 30 contributors as of June 2026, with 93 releases and the latest at v1.5.19 (June 24, 2026). The project is MIT licensed and primarily TypeScript (96.7%). Three deployment modes are available: cloud (free tier included), native desktop for Mac, Windows, and Linux, and a headless CLI via npm i -g executor.
Yes, but
The cloud free tier caps at 3 members and 10,000 executions per month, with overage at $0.20 per 1,000 additional executions. The Team plan runs $150 per org per month for unlimited members and 250,000 included executions. Call tracing and audit logs are listed as coming soon on the free and team tiers, with audit logs available on Enterprise. Anyone who needs a full audit trail today should plan on the Enterprise tier or self-hosting with their own logging layer.
The bottom line
Executor solves a real, underappreciated problem: every new agent surface reinvents the integration wiring. One gateway with one tool shape, lazy schema loading, and host-side credential isolation makes the multi-agent setup actually manageable without sacrificing safety.