Skip to content

Commit 5b781c9

Browse files
committed
Flatten spec pages
1 parent c3b5e69 commit 5b781c9

30 files changed

+67
-65
lines changed

docs/_index.md

Lines changed: 58 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,63 @@
22
title: Specification
33
cascade:
44
type: docs
5-
weight: 1
5+
breadcrumbs: false
6+
weight: 10
67
---
7-
The following is the formal specification of the Model Context Protocol, and aims
8-
to be a resource for implementors.
98

10-
For a user guides and SDK configuration, plesae visit https://modelcontextprotocol.io.
9+
{{< callout type="info" >}}
10+
**Protocol Revision**: 2024-11-05
11+
{{< /callout >}}
12+
13+
The [Model Context Protocol](https://modelcontextprotocol.io) (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you're building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need.
14+
15+
This specification defines the authoritative protocol requirements based on the TypeScript schema in [schema.ts](https://github.com/modelcontextprotocol/specification/blob/main/schema/schema.ts).
16+
17+
For implementation guides and examples, visit [modelcontextprotocol.io](https://modelcontextprotocol.io).
18+
19+
## Overview
20+
21+
MCP provides a standardized way for applications to:
22+
23+
- Share contextual information with language models
24+
- Expose tools and capabilities to AI systems
25+
- Build composable integrations and workflows
26+
27+
The protocol uses JSON-RPC 2.0 messages to establish communication between:
28+
29+
- **Clients**: Applications that integrate with language models
30+
- **Servers**: Services that provide context and capabilities
31+
- **Hosts**: Processes that manage client connections
32+
33+
## Core Protocol Features
34+
35+
MCP defines several key components:
36+
37+
### Base Protocol
38+
- JSON-RPC message format
39+
- Capability negotiation
40+
- Session lifecycle management
41+
42+
### Context Primitives
43+
- **Resources**: Data exposed via URIs
44+
- **Prompts**: Template-based interactions
45+
- **Tools**: Executable functions
46+
- **Sampling**: LLM generation control
47+
48+
### Cross-Cutting Concerns
49+
- Progress tracking
50+
- Error handling
51+
- Security boundaries
52+
- Backwards compatibility
53+
54+
## Learn More
55+
56+
Explore the detailed specification for each protocol component:
57+
58+
{{< cards >}}
59+
{{< card link="architecture" title="Architecture" icon="template" >}}
60+
{{< card link="basic" title="Base Protocol" icon="code" >}}
61+
{{< card link="server" title="Server Features" icon="server" >}}
62+
{{< card link="client" title="Client Features" icon="user" >}}
63+
{{< card link="contributing" title="Contributing" icon="pencil" >}}
64+
{{< /cards >}}

docs/specification/architecture/_index.md renamed to docs/architecture/_index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
title: Architecture
33
cascade:
44
type: docs
5+
breadcrumbs: false
56
weight: 1
67
---
78

docs/specification/basic/_index.md renamed to docs/basic/_index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
title: Base Protocol
33
cascade:
44
type: docs
5+
breadcrumbs: false
56
weight: 2
67
---
78

File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

0 commit comments

Comments
 (0)