modelcontextprotocol
show_server_info
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [ ] Documentation update
Checklist
- [x] I have read the MCP Documentation
- [x] My code follows the repository's style guidelines
- [x] New and existing tests pass locally
- [x] I have added appropriate error handling
- [x] I have added or updated documentation as needed
Additional context
I think it's more useful in the stdio case. Since nothing happens when you start the application.
But on the HTTP, it will be a bit noisy...
If it's in debug level then I think it's fine.
@Kludex @dsp-ant moved it to helper method and class, I think its very useful, for example in my code when im using sse i will add a route that return this object in some route for example /info (like in rest api have swagger json doc) the idea of it is to have something simple without creating a client that can be easily visible same for using stdio and then i will use the debug log i hope you would like it :)
@Kludex @dsp-ant moved it to helper method and class, I think its very useful, for example in my code when im using sse i will add a route that return this object in some route for example /info (like in rest api have swagger json doc) the idea of it is to have something simple without creating a client that can be easily visible same for using stdio and then i will use the debug log i hope you would like it :)
reping
I am closing this out since we haven't made much progress. I think this is mostly on us for screwing up reviewing this properly. Sorry @barnuri . I think in general we are still interested in the feeature, but mindful that we shouldn't add the underlying types to src/mcp/types.py since that file reflects the official protocol. This is an SDK feature only. If you are interested in redoing this ontop of the current state of the repo, please do so and ping me either via the MCP Contributor discord or on the PR and I will get to it.
Again, I am very sorry that we didn't review this in proper time and made the progress very slow.
