Skip to content

Commit

Permalink
Merge branch 'main' into sm/annotated-timestamp
Browse files Browse the repository at this point in the history
  • Loading branch information
jerome3o-anthropic authored Feb 12, 2025
2 parents 461630e + 55c983f commit 041666b
Show file tree
Hide file tree
Showing 5 changed files with 397 additions and 127 deletions.
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,8 @@
This repo contains the specification and protocol schema for the Model Context Protocol.

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

## Contributing

Expand Down
117 changes: 0 additions & 117 deletions docs/specification/CLAUDE.md

This file was deleted.

15 changes: 10 additions & 5 deletions docs/specification/draft/basic/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,14 +53,19 @@ See the following pages for more details on the different components:

## Auth

Authentication and authorization are not currently part of the core MCP specification,
but we are considering ways to introduce them in future. Join us in
MCP provides an [Authorization]({{< ref "/specification/draft/basic/authorization" >}})
framework for HTTP+SSE transport. Implementations using HTTP+SSE transport **SHOULD**
conform to this specification, whereas implementations using STDIO transport **SHOULD
NOT** follow this specification, and instead retrieve credentials from the environment.

Additionally, clients and servers **MAY** negotiate their own custom authentication and
authorization strategies.

For further discussions and contributions to the evolution of MCP’s auth mechanisms, join
us in
[GitHub Discussions](https://github.com/modelcontextprotocol/specification/discussions)
to help shape the future of the protocol!

Clients and servers **MAY** negotiate their own custom authentication and authorization
strategies.

## Schema

The full specification of the protocol is defined as a
Expand Down
Loading

0 comments on commit 041666b

Please sign in to comment.