Give agents & MCP their own docs page - #558
Merged
Merged
Conversation
The getting-started page had grown a tail about llms.txt and the MCP server that had nothing to do with getting started, and the MCP part was one line deep -- it never said what the server exposes or how a library gets served by it. Move both sections to their own "Agents" page, last in the nav, and flesh out the MCP one: what the resources and the tool return, a concrete index-then-fetch round-trip, the claude-code plugin, a walk through the inspector, and the three steps for a library to get served. Also drop the /api/sse claims from the manifest and the getting-started page: the SSE transport needs a Redis instance to relay messages, which this deployment does not have, so that endpoint never answers. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013ongoBHFSoa6KgksdTTQ86
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The getting-started page had grown a tail about
llms.txtand the MCP server that had nothing to do with getting started, and the MCP part was one line deep (npx @modelcontextprotocol/inspector, no context) -- it never said what the server exposes, nor how a library gets served by it.What's here
Agentspage (/agents/introduction, last in the nav) holding both sections, moved out of getting-started, which keeps a three-line pointer.pmndrs/claude-code-pluginshortcut for claude-code, a walk through the inspector (screenshot), and Getting your library served -- the three steps for a library to earn theMCPbadge: publish/llms-full.txt, check it, flipllms_full: trueinlibs./api/sseclaims from the manifest served to agents and from the docs. The legacy SSE transport needs a Redis instance to relay messages between the SSE stream and/api/message; this deployment has none and passes noredisUrl, soGET https://docs.pmnd.rs/api/ssenever answers -- verified in prod, it hangs until the 60s timeout. Only streamable HTTP at/api/mcpworks.Notes
/api/ssestays routable (/api/[transport]matches any segment) and hangs rather than failing fast. Returning a 404 for any transport other thanmcpwould be a separate change -- happy to add it here if wanted.🤖 Generated with Claude Code
https://claude.ai/code/session_013ongoBHFSoa6KgksdTTQ86