Docs

Connect MCP

Make EasyNet capabilities available to an MCP client, or connect tools from an upstream MCP server. Choose the direction in the guide.

Choose a direction. Inbound installs EasyNet as an MCP server for a local AI client; outbound binds tools from an explicitly configured upstream MCP server into one EasyNet Agent.

All connection paths

Run this guide

What do you want to connect?

These are alternative paths. You do not need to run both.

Use EasyNet from CodexGive an EasyNet Agent an MCP tool

Outcome: Install EasyNet as an MCP server in your local Codex client. Codex can then request the tools exposed by your EasyNet Runtime.
Before you run it: The CLI and isolated configuration preview are public. Live tools require a paired, responsive Runtime. A normal dry-run may print secrets from existing client configuration; the preview below uses /dev/null to avoid reading it. This path does not require an upstream MCP server or an EasyNet Agent registration.

Pair and start your Runtime first

zsh · EasyNet → Codex

easynet mcp status
# Safe preview: do not read or print the existing Codex configuration.
easynet mcp install codex \
  --name easynet \
  --config-path /dev/null \
  --dry-run

# After reviewing the isolated preview, write the real client entry.
easynet mcp install codex --name easynet

Verify the result and boundary

Success looks like: The isolated preview shows only the proposed EasyNet entry. After installing it, restart Codex and verify its live tool list against the Runtime. An entry in the configuration file alone does not prove tools are reachable.
Still separate: This is a same-device stdio connection using the local Runtime identity, not a separate Codex caller. The --tenant and --agent labels do not grant permissions or isolate clients. In tools/list, x-easynet.ability and the description identify the Ability; tools/call must use the returned name. Verify cross-device access and caller isolation separately.