show_server_info

[barnuri]

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[barnuri]

@Kludex can you review ?

[barnuri]

@dsp-ant can you look ?

[dsp-ant]

@Kludex any opinions? I personally understand why you would want this, but i think it would be better suited in your application as either a call before starting the server or as an extension to the FastMCP server class. I appreciate the effort but would politely decline adding this.

[Kludex]

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.

[barnuri]

ok i will change to debug

[barnuri]

@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 :)