1.8.0-experimental.3 (2026-02-25)

Features

Allow server "description" to be configured

Example:

server_info:
  name: "Acme Corp GraphQL Server"
  version: "2.0.0"
  title: "Acme MCP Server"
  website_url: "https://acme.com/mcp-docs"
  description: "MCP server for Acme Corp's GraphQL API"

Support custom tool descriptions for all operation sources

Users can now provide custom tool descriptions via the overrides.descriptions config, regardless of the operation source (manifest, uplink, collection, local files). This lets AI models better understand when and how to use each tool, without requiring changes to operation files or manifests.

overrides:
  descriptions:
    GetAlerts: "Get active weather alerts for a US state"
    GetForecast: "Get a detailed weather forecast for a coordinate"

Fixes

Fix server crash on collection sync with invalid operations

A single operation with malformed variables JSON in a collection would crash the entire server. Invalid operations are now skipped with a warning, and the server continues serving with the remaining valid operations.

Fix JSON schema type mapping for GraphQL Int

Map GraphQL Int to JSON schema { "type": "integer" } instead of { "type": "number" }. This tells MCP clients to send integer values rather than floats (e.g. 1234 instead of 1234.0), fixing input coercion errors on GraphQL servers that strictly validate Int inputs.

Gate outputSchema and structuredContent on negotiated MCP protocol version

When enable_output_schema is configured, the server now advertises MCP protocol version 2025-06-18 and only includes outputSchema in tools/list and structuredContent in tools/call responses when the client negotiates a protocol version that supports them (>= 2025-06-18). Previously, these fields were sent regardless of the negotiated version, which could cause errors in clients that don't recognize them.