Local stdio MCP server for the Eon platform — OAuth client_credentials auth for CI, agents, and scripts
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"eon-mcp-local","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# eon-mcp-local Local stdio [MCP](https://modelcontextprotocol.io) server for the [Eon](https://eon.io) platform. Lets MCP clients (Claude Code, Cursor, Codex, Devin, scripts in CI) call Eon REST APIs over a non-interactive `client_credentials` OAuth flow. Unlike the remote `https://mcp.eon.io` server (which uses an interactive browser-based OAuth flow), this CLI is suitable for machines and pipelines. ## Install First install [`uv`](https://docs.astral.sh/uv/getting-started/installation/) via your preferred method — Homebrew, pipx, your OS package manager, or Astral's install script (see Astral's docs for checksum-verified options). Then pick one: ```bash # zero-install (uvx fetches on first run, caches for next time) — recommended uvx eon-mcp-local serve # persistent install uv tool install eon-mcp-local # or pipx if you prefer pipx install eon-mcp-local ``` ## Configure Create API credentials in the Eon console (Settings → API Credentials), then set: ```bash export EON_CLIENT_ID=... export EON_CLIENT_SECRET=... export EON_ACCOUNT_DOMAIN=acme # the 'acme' in 'acme.console.eon.io' ``` ## Wire into Claude Code ```bash claude mcp add eon -- uvx eon-mcp-local serve ``` Equivalent for Cursor / Codex / Devin: add a stdio MCP server with command `uvx eon-mcp-local serve` and the env vars above. ## Using from an agent framework See [`examples/adk_example.py`](examples/adk_example.py) for a runnable Google ADK agent that spawns `eon-mcp-local` as a stdio subprocess and exposes its tools to Gemini. The same pattern (spawn a subprocess, speak MCP over stdin/stdout) works with any MCP-aware framework. ## Environment variables | Variable | Required | Description | | --- | --- | --- | | `EON_CLIENT_ID` | yes | OAuth client_id from `POST /api/customer/v1/api-credentials` | | `EON_CLIENT_SECRET` | yes | OAuth client_secret from the same endpoint | | `EON_ACCOUNT_DOMAIN` | yes | Your tenant subdomain (the `acme` in `acme.console.eon.io`) | | `EON_LOG_LEVE…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.