Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEVDOCS_CACHE_DIRNoDirectory where DevDocs docsets are cached. Defaults to ~/.cache/devdocs-mcp/ if not set.~/.cache/devdocs-mcp/

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_docsetsA

List installed (cached) docsets, or search the DevDocs catalog for installable ones (installed=false requires filter).

install_docsetA

Download a DevDocs docset into the local cache (re-downloads only if upstream is newer).

remove_docsetA

Delete a docset from the local cache.

searchA

Fuzzy search entry names across installed docsets. Returns compact rows: slug, type, name, path. Feed a path to read/toc.

readA

Read a docset page as markdown. Append #anchor to the path to get just that section. Long pages paginate via offset.

tocA

Heading outline of a page: level, title, anchor. Pick a section and read path#anchor instead of paging the whole page.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: three manage docsets (list, install, remove) and three navigate content (search, read, toc). There is no overlap or ambiguity.

Naming Consistency3/5

The first three tools follow a consistent verb_noun snake_case pattern (remove_docset, list_docsets, install_docset), but the remaining three use bare verbs or a noun (search, read, toc). This mixed convention is readable but not fully consistent.

Tool Count5/5

With 6 tools, the server is well-scoped for its purpose of managing and reading DevDocs documentation. Each tool earns its place and there is no bloat.

Completeness5/5

The server covers the full lifecycle: list/install/remove docsets and search/read/navigate pages. The install tool also handles updates, leaving no obvious gaps for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues