Skip to main content
Glama
xvantz

ts-docs-mcp

by xvantz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_package_docsA

Get accurate, version-specific API documentation for any npm package.

WHEN TO USE THIS TOOL:

  • ALWAYS call this tool when the user asks about a library, package, or framework.

  • ALWAYS call this tool BEFORE writing code that uses an external npm dependency.

  • ALWAYS call this tool when you need to know function signatures, types, interfaces, classes, or exports from a package.

  • Call this tool when the user says things like: 'use zod', 'write with axios', 'how does fastify work', 'express route handler', 'prisma schema', 'lodash merge'.

  • Call this tool when a package version is mentioned: 'zod@3.23', 'express 4.18' — pass it as the 'version' parameter.

DO NOT rely on training data for package APIs — training data is months out of date. This tool fetches the EXACT version the user needs from the actual source code.

Supports:

  • Specific version: get_package_docs('zod', version='3.23.8')

  • Subpath exports: get_package_docs('zod', subpath='v4/classic')

  • Symbol search: get_package_docs('zod', query='transform')

Documentation is cached for 24 hours — repeated calls for the same package+version are instant.

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

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

With only a single tool, there is no ambiguity whatsoever — get_package_docs has a clearly defined purpose of fetching version-specific npm package documentation. There are no overlapping tools to confuse.

Naming Consistency4/5

The single tool name 'get_package_docs' follows the conventional verb_noun pattern and is descriptive. However, with only one tool, there's no pattern to evaluate for consistency across a set.

Tool Count2/5

A single tool for package documentation is borderline thin. While it's a focused purpose, a fuller server might include tools for discovering packages, listing versions, or comparing docs — but the single tool does serve a coherent narrow scope.

Completeness3/5

The tool covers fetching docs with version, subpath, and symbol query options, which handles the core use case of retrieving accurate package API info. However, there are no companion tools for related operations like listing supported packages, listing available versions, or fetching type definitions separately, creating minor gaps.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources