General MCP setup
Use the same Modeledge MCP server from Claude Code, Codex, Grok, Crush, OpenCode, and other MCP-compatible clients.
Connection details
Server name
modeledge
Server URL
https://mcp.modeledge.ai/mcp
Transport
streamable HTTP or HTTP MCP
Auth header
Authorization: Bearer <API key>
Key source
Modeledge account page
What every client needs
Most MCP clients need the same Modeledge connection details. The labels vary by client, but the values are consistent.
- Server name: modeledge
- Server URL: https://mcp.modeledge.ai/mcp
- Transport: streamable HTTP or HTTP MCP
- Authentication: bearer token using your Modeledge API key
Generic setup
Prefer an environment-variable-backed bearer token when your client supports one. Do not put the raw API key in a repository, committed config file, or shell history.
- Generate a Modeledge MCP API key from your account page.
- Open your client's MCP server settings and add a new HTTP server named modeledge.
- Set the server URL to https://mcp.modeledge.ai/mcp.
- Set authentication to a bearer token using your Modeledge API key. Use an environment-variable or secret-store reference when the client supports one.
- Reload the client, then ask it to list or use the Modeledge tools.
Client notes
- Claude Code has a dedicated add command. Use the Claude Code guide for the exact command.
- ChatGPT desktop and Codex share MCP configuration in ~/.codex/config.toml. Use the ChatGPT desktop / Codex guide for the exact command and macOS environment steps.
- Grok stores MCP servers in ~/.grok/config.toml (or a project .grok/config.toml). Use the Grok guide for the CLI command and TOML snippet.
- Crush, OpenCode, and similar clients usually expose this as an MCP server entry. Choose the HTTP transport and configure the same URL with an environment-backed bearer token when supported.