You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enhance search_servers documentation and update server entry structure
- Updated documentation to include repository information and separate MCP endpoints from source code repositories.
- Added `source_code_url` field to `ServerEntry` struct for better clarity on source code links.
- Modified tests to validate the new `source_code_url` field and ensure correct parsing of server entries.
In this example, the result indicates a server named “WeatherInfo”, with a base MCP endpoint URL. The user or agent can then call:
78
+
In this example, the result indicates a server named “WeatherInfo”, with a base MCP endpoint URL for direct connection and a separate source code repository URL. The user or agent can then call:
In a real scenario, the above JSON could be printed to the console or returned as an MCP tool response. The user/agent sees two matching servers from MCP Run and can choose one to add. Each entry includes url (the base endpoint to connect to the MCP server) so that no additional lookup is required beyond this search.
132
+
In a real scenario, the above JSON could be printed to the console or returned as an MCP tool response. The user/agent sees two matching servers from MCP Run and can choose one to add. Each entry includes url (the base endpoint to connect to the MCP server) and source_code_url (link to the source repository) so that no additional lookup is required beyond this search.
0 commit comments