API overview — EvalGate Docs MCP Resource
API overview
is one of 21 resources on the
EvalGate Docs
MCP server. Connect the server and your client can attach it as context.
by client
How to attach API overview from your client
- Claude Code EvalGate Docs Resource/API overview run in your project directory
- Claude Desktop EvalGate Docs Resource/API overview ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EvalGate Docs Resource/API overview ~/.cursor/mcp.json
- VS Code EvalGate Docs Resource/API overview .vscode/mcp.json
- Zed EvalGate Docs Resource/API overview ~/.config/zed/settings.json
- Windsurf EvalGate Docs Resource/API overview ~/.codeium/windsurf/mcp_config.json
- Cline EvalGate Docs Resource/API overview ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EvalGate Docs Resource/API overview ~/.gemini/settings.json
- Grok EvalGate Docs Resource/API overview .mcp.json (in your project root)
- ChatGPT EvalGate Docs Resource/API overview Settings → Connectors → Advanced → Developer mode
- Claude.ai EvalGate Docs Resource/API overview Settings → Connectors → Add custom connector
- LangChain EvalGate Docs Resource/API overview pip install langchain-mcp-adapters
Other resources on this server
- Official EvalGate Agent Skills
- EvalGate capability map
- Setup and getting started
- Credential-free local regression gate
- Write evaluation specs (TypeScript and Python)
- Python SDK and CLI
- Go SDK installation and first request
- Ruby SDK installation and first request
- API authentication
- MCP and HTTP Tool APIs
- MCP integration
- Evaluations
- CI/CD integration
- Webhooks and Slack
- Agent framework integrations
- Prompt Hub
- Experiments
- Deployable Assets
- Traces
- EvalGate documentation browser
Read from the server itself, by connecting to it and calling resources/list on 5 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.