MCP gateway for every agent

Connect any agent to everything.Show it one tool.

Executor normalizes MCP, OpenAPI, GraphQL and custom integrations behind one endpoint—then loads a schema only when code calls it.

Run it locally ↗Inspect the aperture ↓

MIT LICENSEDLOCAL · CLOUD · CLIONE MCP ENDPOINT

SCHEMA FIELD / 1,640 TOOLS

github.searchCode()stripe.createCharge()jira.transitionIssue()sentry.resolveIssue()linear.createIssue()gmail.sendMessage()notion.query()slack.postMessage()

EXECUTORnormalize

MODEL SEES / 01 TOOLexecute(input)search → describe → call

MCP · OPENAPI · GRAPHQL · CUSTOMLAZY LOAD ↗

WITHOUT EXECUTOR1,640 tools≈ 278,800 tokens

→

WITH EXECUTOR1 tool≈ 1,044 tokens

Public comparison shown on executor.sh. Tool mix and token count are the published example, not a universal benchmark.

Context efficiency

Your model should reason about the task. Not inventory the warehouse.

Executor exposes a single code-mode tool. The agent searches the catalog, describes the one capability it needs, then calls it.

01tools.search()

Find the right capability without loading every schema.

02tools.describe.tool()

Bring only the selected input and output contract into view.

03tools[path](input)

Execute inside the sandbox with the configured connection.

One tool shape

Different protocols. Same way through.

Anything imported becomes a name, an input schema and an output schema—so the calling surface stays interchangeable.

MCPOPENAPIGRAPHQLCUSTOM

UNIFIED CONTRACTnameinput schemaoutput schema

CODEXCURSORCLAUDE CODECLI

RUN / 7421POLICY ACTIVE

GET · READAUTO-RUNsafe semantics preserved

DELETE · MUTATIONASK HUMANdestructive action pulls you back in

HOST SIDE••••••••••••token never enters sandbox heap

Guardrails travel with the tool

Safe paths stay easy. Sharp edges stay visible.

Executor preserves imported semantics—HTTP methods, MCP destructive hints and GraphQL mutations—so agents can auto-run routine reads and pause before destructive actions.

Isolated JavaScript sandbox
Credentials resolved host-side
Per-user and shared connections

Pick your path

One gateway. Three ways to own it.

01 / CLOUDTeam online in minutes.

Hosted auth, sync and policy controls with a free tier to start.

02 / DESKTOPEverything stays local.

Native Mac, Windows and Linux apps; integrations and sessions stay on device.

03 / CLIHeadless by default.

Install the background service and drive it from the terminal.

The model reasons

Executor handles the rest.

Point any MCP-capable agent at one endpoint and connect the tools your work actually needs.

Get started ↗