modelcontextprotocol / modelcontextprotocol/python-sdk
Enable FastMCP to filter tools, prompts, resources using a fine grained policy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.3k
- Forks
- 4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 31
Description
Description
The authorization protocol allows MCP to implement course grained authorization checks e.g. a principal can/cannot access the server.
For advanced use cases though it is useful to be able to limit access on a per tool/resource/prompt basis.
There are a range of authorization tools that can be used however rather than being specific I suggest it is better to provide a plugin API that allows providers to pick their underlying authorization approach.
I have a patch that shows this idea, I'll open a draft pull request to illustrate the idea and allow for further testing & refinement.
References
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the fine-grained authorization proposal and the patch mentioned in the issue, then compare it with the MCP authorization protocol. The work is complete when FastMCP exposes a provider plugin API that can allow or deny access independently for tools, prompts, and resources, with the approach refined through testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100