ProudNet Document MCP
Official# ProudNet Document MCP
An MCP (Model Context Protocol) server that provides ProudNet documentation access for AI tools.
## Installation
```bash
npm install -g proudnet-document-mcp
```
## Configuration
### Claude Desktop
Configuration file locations:
- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`
Add the following configuration:
```json
{
"mcpServers": {
"proudnet": {
"command": "npx",
"args": ["proudnet-document-mcp"]
}
}
}
```
Restart Claude Desktop after configuration.
## Available Tools
- **search_proudnet_docs** - Search ProudNet documentation
- **get_proudnet_page** - Get specific documentation page content
- **list_proudnet_sections** - List documentation sections
## Usage
### Using with AI Tools
In MCP-supported tools like Claude:
- "How do I set up P2P connections in ProudNet?"
- "Search for ProudNet RMI usage"
- "Find server configuration information in ProudNet docs"
## License
MITTDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_proudnet_page retrieves content from a specific page, list_proudnet_sections lists main sections, and search_proudnet_docs searches for topics. There is no overlap in functionality, making it easy for an agent to select the right tool without confusion.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_proudnet_page, list_proudnet_sections, search_proudnet_docs). The naming is predictable and readable throughout the set, with no deviations in style.
With 3 tools, the count is reasonable for a documentation server, covering key operations like retrieving, listing, and searching. It is slightly minimal but well-scoped, as each tool serves a distinct and necessary function without feeling thin.
The tool surface covers essential documentation interactions: getting specific content, listing sections, and searching. Minor gaps might include operations like updating or managing documentation, but for a read-only documentation domain, the coverage is sufficient for agent workflows.