Server identity
Name, version, description, homepage and metadata that identify the server.
Specification
The MCPDS document format
A single, human-authored *.mcp.yaml file fully describes an MCP server and serves as the source of truth for scaffolding, documentation, client configuration and registry entries.
JSON Schema at a glance
The package version tracks the schema version. A major bump signals a breaking change to the schema structure - your mcpds: field pins which contract a document targets.
What a document describes
Eight sections, one contract. Each maps to a part of the MCP server you would otherwise wire up by hand.
Transports
stdio, HTTP and SSE transport definitions with their connection details.
Authentication
None, API key, OAuth 2.1 and custom schemes, declared up front.
Tools
Callable operations with JSON Schema input and output contracts.
Resources
Readable resources and resource templates exposed by the server.
Prompts
Reusable prompt templates with typed arguments.
Components
Shared schema fragments referenced across tools and prompts.
Packaging
How the server is distributed, run and registered.
Using the package
The @mcpds/spec package ships the schema and TypeScript types for tools built on top of MCPDS.
$ npm install @mcpds/spec
import { mcpdsSchema, type McpdsDocument } from "@mcpds/spec";Validate your YAML
Reference the bundled JSON Schema directly from your editor for inline validation and autocomplete.
server.mcp.yaml
# yaml-language-server: $schema=
# https://unpkg.com/@mcpds/spec/
# schemas/mcpds-1.0.schema.json
mcpds: "1.0"Versioning
The package version tracks the schema version. A major bump signals a breaking change to the schema structure.