executor MCP工具

Quick start

The fastest path is Executor Cloud: sign in, add an integration, and point your agents at the hosted MCP endpoint. Nothing to install.

To run it locally instead (Node.js 20+):

npm install -g executor   # or: pnpm add -g / bun add -g / yarn global add
executor install          # install the durable background service
executor web              # open the web UI in your browser

executor install keeps the service running across restarts. For a throwaway foreground runtime, use executor web --foreground. From the web UI, add your first integration and connect an agent.

Over HTTP (the running service serves a streamable-HTTP endpoint)

npx add-mcp http://127.0.0.1:4788/mcp --transport http --name executor

Or over stdio, with the executor CLI on your PATH

npx add-mcp "executor mcp" --name executor ```

The Connect card in the web UI shows the exact command (and port, if it differs) already filled in. Most MCP clients only load servers at startup, so you may need to restart the client or open a new chat before the Executor tools appear.

CLI reference

executor install                    # install/start the durable background service
executor web                        # open the running web UI
executor web --foreground           # start a temporary foreground runtime + web UI
executor daemon run                 # start persistent local daemon in background
executor daemon status              # show daemon status
executor daemon stop                # stop daemon
executor daemon restart             # restart daemon
executor mcp                        # start MCP endpoint (stdio)
executor call <path...> '{"k":"v"}' # invoke a tool by path segments
executor call <path...> --help      # browse namespaces/resources/methods
executor call <path...> --help --match "<text>" --limit <n> # narrow huge namespaces
executor resume --execution-id <id> # resume paused execution
executor tools search "<query>"     # search tools by intent
executor tools sources              # list configured sources + tool counts
executor tools describe <path>      # show tool TypeScript/JSON schema

References

As part of my coding process, I give my agent access to references to other codebases to understand patterns and how other people have implemented systems. A non-exhaustive list:

• FumaDB - Storage adapter reference
• Effect - General code patterns
• OpenCode - Plugin system reference
• OpenClaw - Plugin system reference
• Emdash - Plugin system reference
• Pi - Plugin system reference

You are also encouraged to use this codebase as a reference to understand how it is implemented.

Add an integration

From the web UI, click Add Source, paste an OpenAPI, GraphQL, or MCP URL, and Executor detects the type, indexes the tools, and handles auth. Or add one from the CLI:

executor call executor openapi addSource '{
  "spec": "https://petstore3.swagger.io/api/v3/openapi.json",
  "namespace": "petstore",
  "baseUrl": "https://petstore3.swagger.io/api/v3"
}'

Use baseUrl when the OpenAPI document has relative servers entries (for example "/api/v3"). Confirm it is live with executor tools sources.