aeonaeon

MCP

Drive your Aeon agent from ChatGPT, Claude, or Cursor via the remote Aeon Connect MCP server or local stdio tools.

Aeon skills work outside GitHub Actions too - drive your agent remotely from ChatGPT, Claude, or Cursor through Aeon Connect, or expose skills locally over stdio MCP.

Remote MCP (Aeon Connect)

Aeon Connect serves a Streamable HTTP MCP server at https://www.aeon.fun/connect/mcp (also listed in the official MCP Registry as fun.aeon/aeon). Sign in with GitHub via OAuth to list and trigger skills, inspect run status, read outputs and memory/, toggle skills, and send feedback (send_feedback). Execution still runs on your own GitHub Actions and model keys never pass through chat.

One-click install: Cursor · VS Code · Kiro · LM Studio

# Claude Code
claude mcp add --transport http aeon https://www.aeon.fun/connect/mcp
# Codex CLI
codex mcp add aeon --url https://www.aeon.fun/connect/mcp
# Gemini CLI
gemini mcp add --transport http aeon https://www.aeon.fun/connect/mcp
# VS Code
code --add-mcp '{"name":"aeon","type":"http","url":"https://www.aeon.fun/connect/mcp"}'

For read-only documentation queries without signing in, point any MCP client at the public docs server at https://www.aeon.fun/mcp.

Local Stdio MCP

Register your local clone's skills as aeon-<name> tools in Claude Desktop or Claude Code:

bin/add-mcp                # build and register local stdio MCP server
bin/add-mcp --desktop      # print Claude Desktop config snippet
bin/add-mcp --build-only   # compile without registering
bin/add-mcp --uninstall    # remove registration

See docs/examples/mcp/test_connection.py for a working stdio client example calling aeon-token-movers.

Consuming External MCP Servers

Skills can also act as MCP clients during a run. For example, base-mcp connects to the Base MCP server (https://mcp.base.org) to read balances and execute approved swaps across partner plugins (Morpho, Moonwell, Uniswap, Avantis, Virtuals, Aerodrome, Bankr).

One-Click OAuth Connect

OAuth-protected upstream MCP servers connect through a browser PKCE flow in the dashboard: tokens are captured server-side into encrypted repository secrets and refreshed before each run. Supported one-click connectors:

Token rotation requires GH_GLOBAL

OAuth refresh tokens rotate on every use. Because default GITHUB_TOKEN cannot write updated repository secrets, set GH_GLOBAL (or GH_SECRETS_PAT) so rotated refresh tokens persist across runs.

On this page