Skip to content

Conversation

@Joffref
Copy link
Contributor

@Joffref Joffref commented Jul 14, 2025

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

2. **Informational** SEP describes a Model Context Protocol design issue, or provides general guidelines or information to the MCP community, but does not propose a new feature. Informational SEPs do not necessarily represent a MCP community consensus or recommendation.
3. **Process** SEP describes a process surrounding MCP, or proposes a change to (or an event in) a process. Process SEPs are like Standards Track SEPs but apply to areas other than the MCP protocol itself.

### Examples of SEP Types
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be easier if it's added within the SEP types section, to save readers from having to scroll up?

Here are concrete examples for each SEP type:

1. **Standards Track** — Asynchronous support in MCP ([Transport-agnostic resumable streams #899](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/899))
2. **Informational** — Load balancing with MCP ([Add best practices when using load balancer #325](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/325))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if this example is a good qualifier of SEP. Could you help elaborate?


Here are concrete examples for each SEP type:

1. **Standards Track** — Asynchronous support in MCP ([Transport-agnostic resumable streams #899](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/899))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would be a good example
#284 - A major change on the implementation of MCP.

@Joffref Joffref requested a review from a team July 18, 2025 16:32
@dsp-ant dsp-ant requested review from a team and tzolov September 23, 2025 21:10
@dsp-ant
Copy link
Member

dsp-ant commented Nov 24, 2025

I think having examples would actually be good, but we should probably choose examples that were implemented.

@domdomegg domdomegg requested review from a team as code owners November 25, 2025 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants