Skip to main content
the edgeful MCP server exposes the same report catalog as the API, as tools your AI agent can call directly in a conversation: list_allowed_report_endpoints, describe_report_endpoint, call_report_endpoint, and get_discovery_scan. no local project, no .env file, no coding agent required, just add the connector and ask a question.
this is a different setup path from set up API with your AI agent, which wires the REST API into a local codebase. use MCP when you want edgeful available directly inside your chat client; use the API path when you’re building something that calls edgeful from your own code.
server URL: https://api.edgeful.com/mcp

​
Claude (Desktop or Web)

1

add the connector

in Claude, go to Settings → Connectors → Add custom connector.
2

point it at edgeful

name it edgeful and set the URL to https://api.edgeful.com/mcp, then save.
3

connect

click Connect. a browser window opens an edgeful sign-in and consent screen, not a bare API key prompt. sign in with your edgeful account and click Allow.
4

ask a question

back in Claude, the edgeful tools are available in the conversation. try something like “what are the top reports for ES right now?” and watch it make a tool call.

​
Codex

1

add the server

app: open Codex → ⚙️ Settings → MCP servers → + Add server. name it edgeful, set type to Streamable HTTP, and set the URL to https://api.edgeful.com/mcp. no headers or key needed, save.CLI: the same config is shared through ~/.codex/config.toml, so entries added in the app show up there too.
2

authenticate

the server shows up flagged as requiring OAuth. click Authenticate, sign in with your edgeful account in the browser tab that opens, and click Allow. in the CLI, run codex mcp login edgeful if it asks you to reauth.
3

use it

restart if Codex asks you to, then the edgeful tools are available in a thread. /mcp in the composer lists active servers.

​
clients without a native OAuth connector (Cursor, older setups)

some MCP clients can’t run the OAuth handshake yet and only support a static bearer token. for those, keep using an edgeful API key over mcp-remote, the same setup this replaces for Claude and Codex:
  1. generate a key in the API dashboard → API Keys (see authentication for the full key format and rotation flow).
  2. add this to your client’s MCP config:
mcp config
  1. set EDGEFUL_API_KEY in your environment (never paste the key directly into a shared config file).

​
plan access

MCP calls are entitlement-gated the same way the REST API is: your edgeful account needs an active API-enabled plan (Essential, Pro, or All Access). signing in works for any account, but a tool call from an account without an API-enabled plan returns a missing_entitlement error. see authentication for the full plan breakdown.

​
works with

Claude Desktop, Claude Web, Codex (app and CLI), Cursor, and any MCP client that speaks Streamable HTTP.