Title: Open to tools/search and resources/search · Issue #204 · modelcontextprotocol/modelcontextprotocol · GitHub
Open Graph Title: Open to tools/search and resources/search · Issue #204 · modelcontextprotocol/modelcontextprotocol
X Title: Open to tools/search and resources/search · Issue #204 · modelcontextprotocol/modelcontextprotocol
Description: Is the dev team here open to a spec update that adds a simple search endpoint to the tool and resource endpoints? Potentially prompts, too. The idea would be to enable agentic searching for proper tools when there may actually be thousan...
Open Graph Description: Is the dev team here open to a spec update that adds a simple search endpoint to the tool and resource endpoints? Potentially prompts, too. The idea would be to enable agentic searching for proper ...
X Description: Is the dev team here open to a spec update that adds a simple search endpoint to the tool and resource endpoints? Potentially prompts, too. The idea would be to enable agentic searching for proper ...
Opengraph URL: https://github.com/modelcontextprotocol/modelcontextprotocol/issues/204
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Open to tools/search and resources/search","articleBody":"Is the dev team here open to a spec update that adds a simple search endpoint to the tool and resource endpoints? Potentially prompts, too. The idea would be to enable agentic searching for proper tools when there may actually be thousands of tools. \n\nI know part of the design here was very focused servers, but I think we need to enable a generic MCP tool discovery mechanism when you have larger servers. Wanted to gauge temperature or see if this had been considered. This might also require some sort of namespacing concept, curious if folks have thought about that and/or would be open to it (ie list all tools for a namespace).\n\nHigh level, I guess the question is, at a sufficiently large enterprise, have you considered how an aggregator would work that allows ai driven discovery of enterprise capabilities across teams without manually adding multiple MCP servers?\n\nThanks!","author":{"url":"https://github.com/patwhite","@type":"Person","name":"patwhite"},"datePublished":"2025-03-16T14:29:47.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":27},"url":"https://github.com/204/modelcontextprotocol/issues/204"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:fe30fe98-2358-3d6e-266e-a53b1e89ecef |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | BDBE:29ED0C:A6EFDF:DCC359:6A5BAB5D |
| html-safe-nonce | 8deaad505655088e908f5086392f624f5a44d636918f0ba2ce6a05a5a8618b79 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCREJFOjI5RUQwQzpBNkVGREY6RENDMzU5OjZBNUJBQjVEIiwidmlzaXRvcl9pZCI6IjM2OTE2NDcwMzU0ODc1Mjk4MjEiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | c78f994660b0338ac6a11c06a3b0b4a2512e8d6e93dd0a7e0da3d9f58b5eb8f4 |
| hovercard-subject-tag | issue:2923100543 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/modelcontextprotocol/modelcontextprotocol/204/issue_layout |
| twitter:image | https://opengraph.githubassets.com/51810d6c26b24d386ef4b88896b18568d3e0b30d3088dd296b51739a0085ef63/modelcontextprotocol/modelcontextprotocol/issues/204 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/51810d6c26b24d386ef4b88896b18568d3e0b30d3088dd296b51739a0085ef63/modelcontextprotocol/modelcontextprotocol/issues/204 |
| og:image:alt | Is the dev team here open to a spec update that adds a simple search endpoint to the tool and resource endpoints? Potentially prompts, too. The idea would be to enable agentic searching for proper ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | patwhite |
| hostname | github.com |
| expected-hostname | github.com |
| None | 5290d7e14309ad1e76106a9c4237bd1041517e83ea182c8ab756752cb0c6940b |
| turbo-cache-control | no-preview |
| go-import | github.com/modelcontextprotocol/modelcontextprotocol git https://github.com/modelcontextprotocol/modelcontextprotocol.git |
| octolytics-dimension-user_id | 182288589 |
| octolytics-dimension-user_login | modelcontextprotocol |
| octolytics-dimension-repository_id | 862570523 |
| octolytics-dimension-repository_nwo | modelcontextprotocol/modelcontextprotocol |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 862570523 |
| octolytics-dimension-repository_network_root_nwo | modelcontextprotocol/modelcontextprotocol |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 9c975978430e9ad293956f2bbdaf153b1bd84a99 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width