list_docs
List every page of the picomcp documentation, with its URL. Use it to pick a page for read_doc.
Takes no parameters.

io.github.picomcpPublished by GitHub account picomcpv0.1.0Updated Nov 4, 2026
Search and read the picomcp docs while your agent writes TypeScript MCP servers.
picomcp docs's local MCP server; no sign-in required; STDIO; 3 tools.
No AI overview yet: these facts come from the registry entry and the server itself.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
The picomcp documentation as an MCP server. Add it to Claude Code, Cursor or any MCP client, and your coding agent can search and read the picomcp docs while it writes your MCP server.
It is built with picomcp itself, in about 100 lines: read the source.
Claude Code
Cursor, Windsurf, Claude Desktop and other clients: add it to the MCP config file (.cursor/mcp.json for Cursor, claude_desktop_config.json for Claude Desktop):
Needs Node 22 or later.
Every page is also available as a resource, picomcp-docs://{title}.
The server downloads llms-full.txt from the docs site on the first call and keeps it in memory. It always serves the latest published docs, with no update to install.
Set PICOMCP_DOCS to read from another copy of the site, for example a local build at http://localhost:4321.
MIT
Source: packages/docs/README.md at commit d7d418e
List every page of the picomcp documentation, with its URL. Use it to pick a page for read_doc.
Takes no parameters.
Search the picomcp documentation. Returns up to 5 matching pages with a short excerpt. Then call read_doc with a title to get the full page.
queryrequiredRead a full page of the picomcp documentation as Markdown.
pagerequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
claude mcp add picomcp-docs -- npx -y picomcp-docs{ "mcpServers": { "picomcp-docs": { "command": "npx", "args": ["-y", "picomcp-docs"] } }}