Skip to content

Conversation

@Rajesh-Narayanappa87
Copy link

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

@jonathanhefner
Copy link
Member

Hi, @Rajesh-Narayanappa87! 👋 If you are intending to submit this proposal as an SEP, please:

  • Fill out the GitHub issue title and description to help others butter understand your proposal.
  • Follow all the SEP guidelines, including those regarding the SEP number.
  • Be mindful of our AI Contributions guideliness.

@localden localden added the SEP label Dec 4, 2025
@localden localden changed the title Draft new proposal SEP: Add Context Headers (Tool, Prompt, Resources) to MCP Requests for Fine-Grained Rate Limiting Dec 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants