- Home
- MCP servers
- Docs2prompt
Docs2prompt
- python
0
GitHub Stars
python
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"melbourneandrew-docs2prompt-mcp": {
"command": "uv",
"args": [
"--directory",
"/YOUR/LOCAL/PATH/docs2prompt-mcp/src",
"run",
"main.py"
]
}
}
}You run an MCP server that exposes docs2prompt as a local, MCP-compatible endpoint. This lets any MCP client turn repository or hosted documentation into prompts using the docs2prompt workflow, with authentication and a simple local command to start the server.
How to use
Connect your MCP client to the local server configured for docs2prompt and use it to generate prompts from documentation sources. The server runs locally via the UV runtime and points to the docs2prompt runtime code. By providing a GitHub token (readonly access is usually sufficient) you enable docs2prompt to fetch and process repository documentation on demand. You’ll interact with standard MCP client setup flows and the docs2prompt runtime will handle turning documentation into LLM-friendly prompts during your sessions.
How to install
Prerequisites: you need UV installed on your system and a working environment for running MCP servers.
Install UV by running the following command in your terminal.
Clone the MCP server repository that contains the docs2prompt integration.
Configure your MCP client to point to the local server using the provided command and environment setup.
Additional steps and configuration
Use the following MCP server config snippet in your MCP client configuration. Replace the path with your local workspace and provide your GitHub access token in the GITHUB_TOKEN field.
{
"mcpServers": {
"docs2prompt": {
"command": "uv",
"args": [
"--directory",
"/YOUR/LOCAL/PATH/docs2prompt-mcp/src",
"run",
"main.py"
],
"env": {
"GITHUB_TOKEN": ""
}
}
}
}
Notes on security and usage
The GITHUB_TOKEN must be kept secure and should have only the minimum permissions necessary for your use case. Do not expose the token in shared configurations. When you start the server, ensure your local environment is secure and access to the MCP client is restricted to authorized users.