AI agents often struggle with securely and reliably interacting with external systems. Executor addresses this by providing a local-first execution environment that offers AI agents a structured TypeScript runtime, a discoverable tool catalog, and a unified way to connect to various external systems like MCP servers, OpenAPI APIs, and GraphQL APIs. This allows agents to call typed functions instead of relying on insecure shell access or cumbersome API definitions, enhancing both security and developer productivity.

How It Works

Executor operates as a local control plane for agent tool usage. A local daemon indexes connected sources (e.g., MCP servers, OpenAPI documents, GraphQL endpoints) into a unified workspace tool catalog. Agents execute TypeScript code against this catalog via a CLI or an MCP bridge. A key feature is its human-in-the-loop capability: when a tool requires credentials or user input, execution pauses, initiates a secure local flow (such as OAuth or secret capture), and then resumes, keeping sensitive information out of the agent's direct context.

Quick Start & Requirements

• Install: For package distribution: npm install -g executor. For local development: bun install followed by bun dev.
• Run: Package distribution: executor up. Local development: bun run executor call ....
• Prerequisites: Bun runtime is recommended for local development; Node.js/npm for package installation. No specific hardware like GPUs are mentioned.
• Links: Discord community: https://discord.gg/eF29HBHwM6. Default local base URL: http://127.0.0.1:8788.

Highlighted Details

• Supports connecting diverse external tool sources including MCP, OpenAPI, and GraphQL.
• Agent code is written in TypeScript and interacts with a discoverable tool catalog.
• Features built-in human-in-the-loop workflows for secure credential management and user interaction.
• Includes a React-based web UI for managing sources, inspecting tools, and handling secrets.

Maintenance & Community

• The project is actively developed, with the current implementation residing in the apps/ and packages/ directories.
• It is noted as being on its "third major architecture iteration," indicating a history of development and refinement.
• A Discord community is available for support and discussion: https://discord.gg/eF29HBHwM6.

Licensing & Compatibility

• The provided README does not specify a software license. This omission is a critical factor for evaluating adoption, especially concerning commercial use or the creation of derivative works.

Limitations & Caveats

• The absence of a clear license is a significant adoption blocker requiring immediate clarification.
• Being on its third major architectural iteration suggests potential for ongoing changes, API instability, and evolving best practices.