Executor
An open-source centralized MCP proxy management tool that functions as a unified proxy layer between multiple Coding Agents and the external world. It supports integration with MCP Servers, OpenAPI, GraphQL, and Google Discovery, and provides three tiers of permission policy management.
Timeline (last 90 days)
The Executor usage process is divided into four steps: add integration, create connection, set policies, and connect Agent.
Executor is a unified proxy layer sitting between multiple Agents and the outside world, essentially a centralized MCP management and configuration tool.
In addition to MCP Server, Executor also supports OpenAPI, GraphQL, and Google Discovery—as long as an interface can be described using JSON Schema, it can be uniformly converted into a tool callable by an Agent.
Executor provides three permission policy tiers for each tool: always allow, execute after approval, and block directly.
Executor can automatically infer default policies from interface specifications; for example, GET requests are set to always allow by default.
Executor offers four running modes: local CLI, desktop client, hosted on Executor Cloud, and self-hosted Docker deployment or hosted on Cloudflare Worker.
Installing Executor locally requires Node.js version 20 or above, and can be completed using package managers such as npm or bun.
After installing Executor, running executor install registers it as a persistent background service, and running executor web opens the web management page.
Executor supports connecting to Agents via HTTP or stdio; the latter only requires running a single NPX command in the terminal.
The core mechanism by which FLARE achieves underlying decoupling is a communication abstraction layer and an Executor plugin system, where business logic is encapsulated in platform-agnostic Python components, and process startup, network communication, and resource requests are handled by the corresponding platform adapters.
All Facts (10)
The Executor usage process is divided into four steps: add integration, create connection, set policies, and connect Agent.
50%UnverifiedExecutor is a unified proxy layer sitting between multiple Agents and the outside world, essentially a centralized MCP management and configuration tool.
50%UnverifiedIn addition to MCP Server, Executor also supports OpenAPI, GraphQL, and Google Discovery—as long as an interface can be described using JSON Schema, it can be uniformly converted into a tool callable by an Agent.
50%UnverifiedExecutor provides three permission policy tiers for each tool: always allow, execute after approval, and block directly.
50%UnverifiedExecutor can automatically infer default policies from interface specifications; for example, GET requests are set to always allow by default.
50%UnverifiedExecutor offers four running modes: local CLI, desktop client, hosted on Executor Cloud, and self-hosted Docker deployment or hosted on Cloudflare Worker.
50%UnverifiedInstalling Executor locally requires Node.js version 20 or above, and can be completed using package managers such as npm or bun.
50%UnverifiedAfter installing Executor, running executor install registers it as a persistent background service, and running executor web opens the web management page.
50%UnverifiedExecutor supports connecting to Agents via HTTP or stdio; the latter only requires running a single NPX command in the terminal.
50%UnverifiedThe core mechanism by which FLARE achieves underlying decoupling is a communication abstraction layer and an Executor plugin system, where business logic is encapsulated in platform-agnostic Python components, and process startup, network communication, and resource requests are handled by the corresponding platform adapters.
50%