Skip to main content
Glama
MCP-Mirror

Library Docs MCP Server

by MCP-Mirror
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_docsC
Search the docs for a given query and library.
Supports langchain, llama-index, mcp, and openai.

Args:
    query: The query to search for (e.g. "Chroma DB")
    library: The library to search in (e.g. "langchain")

Returns:
    Text from the docs

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_docs' has a clear, distinct purpose of searching documentation for specified libraries.

Naming Consistency5/5

The single tool name 'get_docs' follows a clear verb_noun pattern. With only one tool, naming consistency is inherently perfect as there are no other tools to compare against.

Tool Count2/5

A single tool is insufficient for a documentation search server. While the tool covers basic search functionality, the server lacks tools for browsing documentation structure, getting library metadata, or handling multiple queries efficiently, making the tool count too low for the apparent scope.

Completeness2/5

The tool surface is severely incomplete for a documentation server. There are significant gaps: no ability to list available libraries, browse documentation hierarchies, get version-specific docs, or handle pagination/search refinement. The single search tool provides only basic functionality without supporting common documentation workflows.

Resources