-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
feat: MCP Servers with CRUD operations #10699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
wagnerjt seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but please add testing
Title
MCP Server CRUD operations for the following endpoints and operations:
It works following the Least-Privilege Principle, where if no mcp servers are included at the token level, then the user won't have access (with the exception of admin-like users).
all-team-mcpservers
, then we additionally grab all the team's mcp server list.Endpoints here:
Note: Tests will be added shortly. I wanted to get feedback on the endpoint difference since these are not consistent with LiteLLM's info requests and the update will be a
PUT
instead of thePOST
I am going to add the additional team + token CRUD operations in another PR, but have it stubbed out for now.
Relevant issues
MCP Server Discussion
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/
directory, Adding at least 1 test is a hard requirement - see detailsmake test-unit
Type
🆕 New Feature
📖 Documentation
✅ Test