Codex CLI
To query your Framedash telemetry from the Codex CLI, register the Framedash MCP server with Codex. You get the same MCP tools the Claude Code plugin ships, without the plugin.
Register with codex mcp add
Section titled “Register with codex mcp add”Register the server as a stdio MCP server:
codex mcp add framedash \ --env FRAMEDASH_API_KEY=fd_xxx \ --env FRAMEDASH_PROJECT_ID=your-project-uuid \ -- npx -y @framedash/mcp-serverPass --env once per variable. FRAMEDASH_PROJECT_ID is optional.
Register via config.toml
Section titled “Register via config.toml”codex mcp add saves the server to your Codex configuration. To register it by hand, add this entry to ~/.codex/config.toml:
[mcp_servers.framedash]command = "npx"args = ["-y", "@framedash/mcp-server"]
[mcp_servers.framedash.env]FRAMEDASH_API_KEY = "fd_xxx"FRAMEDASH_PROJECT_ID = "your-project-uuid"Pass the API key as an environment variable; never paste it into chat.
Environment Variables
Section titled “Environment Variables”| Variable | Required | Description |
|---|---|---|
FRAMEDASH_API_KEY | Yes | API key scoped to the MCP tools you use. |
FRAMEDASH_PROJECT_ID | No | Default project UUID. |
FRAMEDASH_BASE_URL | No | API base URL (default: https://app.framedash.dev). |
See MCP Server for scope details.
Tell the Agent via AGENTS.md
Section titled “Tell the Agent via AGENTS.md”Codex reads a repository’s AGENTS.md. Put references to the Framedash docs, CLI, and MCP server in AGENTS.md so the agent knows how to instrument and query. See the AGENTS.md snippet for a copy-paste block.
The Non-Plugin Equivalent of the Claude Skills
Section titled “The Non-Plugin Equivalent of the Claude Skills”The Claude Code plugin bundles skills for SQL queries and CI recipes. Codex does not receive those skills, but the same material lives on these pages:
- Events Schema: columns you can query and validator rules.
- Troubleshooting: what to check when events do not arrive.
- MCP Server: the tool and resource reference.