A portable, machine-readable contract format for Model Context Protocol (MCP) servers.
Archived v0.7 material. The current MCP Description specification is published at mcpdesc.org and maintained in the canonical
mcpdesc/mcpdesc-specificationrepository. This directory is retained for historical reference and v0.7 compatibility; do not make current specification changes here.
The MCP Description Specification defines a standard document format that describes the capabilities of an MCP server — its tools, resources, prompts, transports, and security requirements — without requiring a runtime connection.
Think of it as OpenAPI for MCP servers: a static contract that enables discovery, documentation, validation, and governance across the MCP ecosystem.
| Field | Value |
|---|---|
| Archived version | 0.7.0 |
| Status | Superseded by 0.8.0 |
| Schema | ../schemas/mcp-description/0.7.0.json |
mcpdesc: 0.7.0
info:
name: chess-rating-server
title: Chess Rating MCP Server
version: 1.0.0
transports:
- type: stdio
command: chess-rating
args:
- serve
tools:
- name: get_player_rating
description: Get the current Elo rating for a chess player
inputSchema:
type: object
properties:
player_id:
type: string
description: Player identifier
required:
- player_idspec/
mcp-description.md Assembled normative specification text
sections/ Normative specification, section by section
guides/ Rationale, tutorials, and comparisons (non-normative)
examples/ Example MCP Description documents
extensions/ Vendor extension specifications
implementations.md Known implementations and tooling
CHANGELOG.md Format version history
GOVERNANCE.md How the specification evolves
Versioned JSON Schemas live at the repository root under
../schemas/mcp-description/, shared with the
mcpcontract tooling.
- Read the spec: mcp-description.md
- Explore examples: examples/
- Try the archived schema: ../schemas/mcp-description/0.7.0.json
- Read the current specification: mcpdesc.org/docs/specification/0.8.0
- Write your first description: guides/getting-started.md
- MCP-native — tools, resources, and prompts use MCP protocol structures directly
- OpenAPI-aligned — familiar
info,security, and metadata patterns - Multi-transport — declare stdio, streamable-http, and SSE endpoints
- Extensible — vendor-specific metadata via the
x-extension mechanism - Versioned — schema evolution with backward compatibility tracking
- Offline-first — no server connection needed to understand capabilities
Vendors can attach additional metadata using the x-{vendor}-{feature} convention. See extensions/ for registered extensions.
See CONTRIBUTING.md for how to propose changes, and GOVERNANCE.md for how the specification evolves.
This specification is licensed under Apache License 2.0.