Skip to main content
Glama
Sign In
deenesjakoruzh
Python Docs Server

Python Docs Server

by AnuragRai017
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

python-docs-server MCP Server

A Model Context Protocol server

This is a TypeScript-based MCP server that provides tools to fetch Python documentation using the Brave Search API.

Features

Tools

  • get_python_docs - Get Python documentation for a given query

    • Takes a search query as a required parameter

    • Uses the Brave Search API to fetch relevant documentation links

Related MCP server: MCP2Brave

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Installation

To use with Claude Desktop, add the server config:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "python-docs-server": {
      "command": "/path/to/python-docs-server/build/index.js"
    }
  }
}

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.

Additional Resources

Available Tools

1 tool
get_python_docsC

Get Python documentation for a given query

Inputs: query (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as retrieving Python documentation, making it distinct by default.

    Naming Consistency5/5

    The single tool name 'get_python_docs' follows a clear verb_noun pattern (get + python_docs). Since there is only one tool, consistency is inherently perfect with no deviations to assess.

    Tool Count2/5

    A single tool is too few for a server named 'Python Docs Server', which suggests a broader scope like searching, browsing, or managing documentation. One tool feels thin and limits functionality, indicating a mismatch with the apparent purpose.

    Completeness2/5

    The tool set is severely incomplete for a documentation server. It only provides retrieval ('get_python_docs'), lacking essential operations such as search, list topics, get specific versions, or navigate documentation structure, which are typical for such a domain.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches