search_docsLABSCO SUMMARY
PipeCD's docs become something the agent can quote.
Deployment questions get answered out of the project's own documentation rather than from whatever the model remembers. The search narrows to the right page and the read brings the page itself back, so an answer arrives with the text it came from.
What it is
A local MCP server over the official PipeCD documentation. It clones the docs from GitHub into a temporary directory, indexes the Markdown by title and content, and answers full-text searches against that index.
What you get
- Full-text search across the PipeCD docs, with space-separated keywords treated as AND
- Results paged with an offset and a limit, twenty by default
- The full content of a page returned by its path
Requirements
npx, plus a GitHub personal access token with read:packages scope — the package is published to GitHub Packages, so the registry line and the token go in your .npmrc first.
Setup effort
Follow the published steps — Create a GitHub personal access token with read:packages scope.
USE CASES
01
Answering a configuration question from the actual docs
Search the keywords, then read the page the top hit points at. The answer is the documentation's wording, not a paraphrase of it.
02
Finding out whether PipeCD supports something
One search settles whether the feature is documented at all, which is usually the faster half of the question.
03
Reading a page end to end once the search points at it
Take the path from the search result and pull the whole page, rather than working from the snippet.
2 tools
Listed in project docs. Your client may show a different list.
read_docsBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
Create a GitHub personal access token with read:packages scope.
Add these two lines to your .npmrc file:
FILE · .npmrc
@pipe-cd:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=<YOUR_TOKEN>MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"pipe-cd.docs-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"@pipe-cd/docs-mcp-server@latest"
]
}
}
}
