Add default /docs route to list information about the SSE MCP server

[mconflitti-pbc]

Is your feature request related to a problem? Please describe.
Would be useful to have an equivalent to something like how FastAPI generates OpenAPI docs and are automatically accessible at /docs route.

Describe the solution you'd like
Add a /docs route to the starlette app that provides information about the mcp server (available tools, prompts, resources, version, etc.)

Describe alternatives you've considered
none

Additional context
Basic example I currently use:

[panz2018]

I have developed web servers that integrate MCP SSE functionality:

• Using FastAPI: fastapi_mcp_sse
• Using Starlette: starlette_mcp_sse

These servers can be extended with custom routes while retaining full MCP SSE capabilities. For the FastAPI, you can find the OpenAPI docs after starting the server:

• Documentation (Swagger UI): http://localhost:8000/docs
• Documentation (ReDoc): http://localhost:8000/redoc

[pzhao1799]

@mconflitti-pbc If I'm understanding correctly, you're looking for an autogenerated UI similar to an swagger/redoc UI that clearly lists the tools, prompts, and resources based on what is defined by the server developer? I'm happy to take a stab at this - will share a proposal.

[mconflitti-pbc]

@mconflitti-pbc If I'm understanding correctly, you're looking for an autogenerated UI similar to an swagger/redoc UI that clearly lists the tools, prompts, and resources based on what is defined by the server developer? I'm happy to take a stab at this - will share a proposal.

Exactly! Could be neat to even provide a way to test out the various tools. That could be just a form submission or even a locally running LLM with tool support that uses webgpu to run the tool e2e.

OpenAPI docs are for developers to learn more about how to use the api. Since the main target for an MCP server is an LLM and the secondary target is for the person, it may make sense to just provide the various tool descriptions and examples of prompts that would trigger those tools.

If there was a way to define an html or md file that the MCP server code or fastmcp code can ingest and display. That could be a mechanism for the MCP developer to provide instructions on how to set up that particular MCP as well.

I could see these docs being served for both SSE and STDIO transports.