🤖 Claude AI Documentation Assistant 📚

Created By
XPE-7a year ago
Overview

What is Claude AI Documentation Assistant?

Claude AI Documentation Assistant is a powerful MCP server that enhances Claude's capabilities by providing intelligent documentation search across various AI/ML libraries.

How to use Claude AI Documentation Assistant?

To use the assistant, clone the repository, set up your environment, and connect it to the Claude Desktop application. You can then ask Claude to search for documentation on specific topics.

Key features of Claude AI Documentation Assistant?

  • Smart documentation search across multiple AI/ML libraries.
  • Seamless integration with Claude's advanced reasoning capabilities.
  • Fast response times optimized for quick retrieval.
  • Extendable architecture to add more documentation sources.

Use cases of Claude AI Documentation Assistant?

  1. Searching for specific library documentation like LangChain or OpenAI.
  2. Assisting developers in understanding complex API usage.
  3. Providing quick access to documentation while coding.

FAQ from Claude AI Documentation Assistant?

  • What are the prerequisites?
    You need Python 3.8 or higher, a Claude Pro subscription, and a Serper API key.

  • Is it easy to set up?
    Yes! Follow the quick start guide in the documentation for installation and configuration steps.

  • Can I add more documentation sources?
    Yes! The architecture is designed to be extendable, allowing you to add new sources easily.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
XPE-7
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago