docs(mcp): add MCP Tool Search page - #451
Conversation
Walkthrough for the mcp_tool_search / mcp_tool_call virtual tools: quick start over REST and the MCP Python SDK, config for a proxy-wide default via default_key_generate_params.object_permission, the token-overlap ranking algorithm, prerequisites, access-control guarantees, and when to reach for tool search vs. the semantic filter.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a9302bec5b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| -d '{ | ||
| "object_permission": { | ||
| "mcp_tool_search_enabled": true, | ||
| "mcp_servers": ["github", "slack"] |
There was a problem hiding this comment.
With this key scoped to only github and slack, the following quick-start commands search for and call math-add/math-multiply, but the page later states that search only surfaces tools the key can already reach and mcp_tool_call enforces the server allowlist. A reader copying the example as-is will either get no math results or a 403 when calling math-add; the allowed mcp_servers should include the server that owns the demonstrated tools, or the demonstrated tool names should come from github/slack.
Useful? React with 👍 / 👎.
2 participants
Summary
New docs page walking through the MCP tool search feature from BerriAI/litellm#31776 and BerriAI/litellm#31777. Lives under the MCP Gateway sidebar group.
Structure:
mcp_tool_search_enabled, hittools/list, search, call. Same flow shown over the streamable-http endpoint with the MCP Python SDK.litellm_settings.default_key_generate_params.object_permission, including the caller-scope-safety note (the default merges after validation, so a non-admin personal-key request doesn't 403).top_kdefault 5, score > 0, stable sort tiebreak, per-calltop_koverride).mcp_tool_callstill runs through_get_allowed_mcp_servers+execute_mcp_toolso the server allowlist, IP filter, and per-keymcp_tool_permissionsstill apply.Sidebar entry inserted after
mcp_semantic_filterin both the MCP Gateway category and the/mcpproxy-API mirror.Test plan
npm startrenders the page at/docs/mcp_tool_searchwith no build errors/mcp - Model Context Protocol) show the new entry between semantic filter and permission management