Skip to content

Commit 041666b

Browse files
Merge branch 'main' into sm/annotated-timestamp
2 parents 461630e + 55c983f commit 041666b

File tree

5 files changed

+397
-127
lines changed

5 files changed

+397
-127
lines changed

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,8 @@
33
This repo contains the specification and protocol schema for the Model Context Protocol.
44

55
The schema is [defined in TypeScript](schema/2024-11-05/schema.ts) first, but
6-
[made available as JSON Schema](schema/2024-11-05/schema.json) as well, for wider compatibility.
6+
[made available as JSON Schema](schema/2024-11-05/schema.json) as well, for wider
7+
compatibility.
78

89
## Contributing
910

docs/specification/CLAUDE.md

Lines changed: 0 additions & 117 deletions
This file was deleted.

docs/specification/draft/basic/_index.md

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -53,14 +53,19 @@ See the following pages for more details on the different components:
5353

5454
## Auth
5555

56-
Authentication and authorization are not currently part of the core MCP specification,
57-
but we are considering ways to introduce them in future. Join us in
56+
MCP provides an [Authorization]({{< ref "/specification/draft/basic/authorization" >}})
57+
framework for HTTP+SSE transport. Implementations using HTTP+SSE transport **SHOULD**
58+
conform to this specification, whereas implementations using STDIO transport **SHOULD
59+
NOT** follow this specification, and instead retrieve credentials from the environment.
60+
61+
Additionally, clients and servers **MAY** negotiate their own custom authentication and
62+
authorization strategies.
63+
64+
For further discussions and contributions to the evolution of MCP’s auth mechanisms, join
65+
us in
5866
[GitHub Discussions](https://github.com/modelcontextprotocol/specification/discussions)
5967
to help shape the future of the protocol!
6068

61-
Clients and servers **MAY** negotiate their own custom authentication and authorization
62-
strategies.
63-
6469
## Schema
6570

6671
The full specification of the protocol is defined as a

0 commit comments

Comments
 (0)