Documentation Index
Fetch the complete documentation index at: https://evalgate.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
MCP API — tool discovery and execution
Discover Evalgate tools anonymously and execute them from any MCP-compatible AI agent, IDE assistant, or custom client using a bearer token.Evalgate exposes an MCP-style API that lets AI agents and IDE assistants (Cursor, Claude Desktop, ChatGPT) discover and call Evalgate operations as structured tools. Tool discovery is public — no authentication required. Tool execution requires a bearer token.
GET /api/mcp/tools — list available tools
Returns all tools available for MCP execution. This endpoint requires no authentication and is designed for tool discovery by agent runtimes and IDE plugins.Response
The MCP protocol version implemented by this server.
POST /api/mcp/call — execute a tool
Executes a named tool with the provided arguments. Requires a bearer token.Request body
The name of the tool to execute, exactly as returned by
GET /api/mcp/tools.Arguments matching the tool’s
inputSchema. Required fields in the schema must be present.Success response (200)
Always
true on success.Array of result items. Each item has a
type field (json or text) and carries the tool’s result in either json (an object) or text (a string).Error response (4xx / 5xx)
Always
false on error.Machine-readable error code. See API error codes for the full list.
Human-readable error description.
UUID for support diagnostics.
Available tools
eval.quality.latest
Get the latest quality score for an evaluation, optionally compared to a baseline.| Parameter | Type | Required | Description |
|---|---|---|---|
evaluationId | number | Yes | Numeric ID of the evaluation |
baseline | string | No | Comparison baseline: published, previous, or production |
eval.run.create
Start a new evaluation run.| Parameter | Type | Required | Description |
|---|---|---|---|
evaluationId | number | Yes | Numeric ID of the evaluation to run |
environment | string | No | Target environment: dev, staging, or prod |
eval.trace.create
Create a distributed trace record.| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Display name for the trace |
metadata | object | No | Arbitrary JSON context to store with the trace |
eval.testcase.list
List test cases for an evaluation.| Parameter | Type | Required | Description |
|---|---|---|---|
evaluationId | number | Yes | Numeric ID of the evaluation |
limit | number | No | Maximum number of test cases to return |
Connecting an MCP client
The
GET /api/mcp/tools discovery call does not need an API key. Only include the auth field in your MCP client configuration — the client will send it automatically when calling POST /api/mcp/call.