@@ -31,26 +31,11 @@ This video demonstrates how you can onboard an MCP server to LiteLLM Proxy, use
31
31
1 . Allow proxy admin users to perform create, update, and delete operations on MCP servers stored in the db.
32
32
2 . Allows users to view and call tools to the MCP servers they have access to.
33
33
34
- LiteLLM exposes the following MCP endpoints:
35
-
36
- - GET ` /mcp/enabled ` - Returns if MCP is enabled (python>=3.10 requirements are met)
37
- - GET ` /mcp/tools/list ` - List all available tools
38
- - POST ` /mcp/tools/call ` - Call a specific tool with the provided arguments
39
- - GET ` /v1/mcp/server ` - Returns all of the configured mcp servers in the db filtered by requestor's access
40
- - GET ` /v1/mcp/server/{server_id} ` - Returns the the specific mcp server in the db given ` server_id ` filtered by requestor's access
41
- - PUT ` /v1/mcp/server ` - Updates an existing external mcp server.
42
- - POST ` /v1/mcp/server ` - Add a new external mcp server.
43
- - DELETE ` /v1/mcp/server/{server_id} ` - Deletes the mcp server given ` server_id ` .
44
-
45
- When MCP clients connect to LiteLLM they can follow this workflow:
46
-
47
- 1 . Connect to the LiteLLM MCP server
48
- 2 . List all available tools on LiteLLM
49
- 3 . Client makes LLM API request with tool call(s)
50
- 4 . LLM API returns which tools to call and with what arguments
51
- 5 . MCP client makes MCP tool calls to LiteLLM
52
- 6 . LiteLLM makes the tool calls to the appropriate MCP server
53
- 7 . LiteLLM returns the tool call results to the MCP client
34
+
35
+ When MCP clients connect to LiteLLM's MCP Gateway they can run the following MCP operations::
36
+ 1 . List Tools: List all available MCP tools on LiteLLM
37
+ 2 . Call Tools: Call a specific MCP tool with the provided arguments
38
+
54
39
55
40
#### Usage
56
41
0 commit comments