ts-docs-mcp
An MCP server that gives AI coding agents accurate, version-aware API documentation for any npm package — straight from the source.
README
ts-docs-mcp
An MCP server that gives AI coding agents accurate, version-aware API documentation for any npm package — straight from the source.
⚡
npx ts-docs-mcp— works with Cursor, Claude Code, VS Code Copilot, and any MCP-compatible client.
The Problem
When you ask an AI coding agent (Claude Code, Cursor, Copilot) to write code using an npm package, the model relies on its training data — which is often months or years out of date.
The result:
// ❌ Model hallucinates — Express 4 syntax, but you have Express 5 installed
import bodyParser from 'body-parser';
app.use(bodyParser.json());
// ❌ Wrong API — Zod v3 pattern, but Zod v4 changed the API
const schema = z.object({ name: z.string() });
schema.parse(data); // Zod v4 requires schema.parse({...}) with options
Models know about libraries, but they don't know which version you have installed or what the current API looks like.
The Solution
ts-docs-mcp provides documentation sourced from the actual package source code — not training data.
The pipeline:
npm registry → GitHub .ts (JSDoc) → npm tarball (.d.ts) → DefinitelyTyped (@types/)
- Resolves the exact version from the npm registry
- Reads TypeScript source from GitHub, including JSDoc,
@param,@returns - Follows re-exports to find actual declarations (BFS, parallel fetches)
- Falls back to
.d.tsfrom the npm tarball if GitHub source is insufficient - Falls back to DefinitelyTyped for JS-only packages (express, etc.)
- Returns clean Markdown — full signatures, parameters, deprecation notices, examples
Before vs After
| Package | Before (v0.1.0) | After (v0.4.1) |
|---|---|---|
| zod | 31 symbols | 577 |
| axios | 0 | 83 |
| uuid | 0 | 23 |
| chalk | 19 | 32 |
| fastify | 51 | ~100+ |
| express | 0 | 13 (via @types/express) |
How It Works
┌──────────────────┐ ┌──────────────────────────────────────────────┐
│ AI Coding Agent │ ◄──── │ ts-docs-mcp │
│ (Cursor, Claude │ MCP │ (MCP Server via stdio) │
│ Code, etc.) │ │ │
└──────────────────┘ │ get_package_docs("zod") │
│ │ ↓ │
│ "Here is the │ 1. npm registry → package metadata │
│ full API │ 2. GitHub raw → JSDoc from .ts source │
│ documentation"│ 3. BFS re-export resolution (parallel) │
▼ │ 4. npm tarball → .d.ts parsing (no JSDoc?) │
Writes correct code │ 5. @types/{name} fallback (JS-only) │
│ 6. Merge + dedup → Markdown │
│ 7. XDG cache (24h TTL) │
└──────────────────────────────────────────────┘
Tools
| Tool | Description |
|---|---|
get_package_docs |
Get API docs for any npm package. Optional query, version, subpath. |
Examples
# Latest version
get_package_docs("zod")
# Specific version
get_package_docs("zod", version="3.23.8")
# Subpath export (e.g. zod/v4/classic)
get_package_docs("zod", subpath="v4/classic")
# Query a specific symbol
get_package_docs("zod", query="transform")
Fallback chain
GitHub .ts (JSDoc + declarations)
→ BFS re-export resolution (depth=2, concurrency=5)
→ merge: GitHub .d.ts (from tarball, with re-export following)
→ if 0 symbols: DefinitelyTyped (@types/{name})
→ merge all results, dedup by name (GitHub takes priority)
What the model gets
## findByEmail (function)
> Find a user by their email address.
> @param email — The email to search for
> @returns The user object or null
```typescript
export function findByEmail(email: string, includeDeleted?: boolean): User | null;
Parameters:
email — The email to search forincludeDeleted — Whether to include deleted users
Returns: The user object or null
Full signatures, no truncation. `@param`, `@returns`, `@deprecated`, `@example` are preserved.
### Cache
Documentation is cached in `~/.cache/ts-docs-mcp/` (XDG-compatible), keyed by `package@version`. TTL is 24 hours. Old entries are cleaned up after 7 days.
---
## Usage
### Quick start
Add to your MCP configuration:
```json
{
"mcpServers": {
"ts-docs-mcp": {
"command": "npx",
"args": ["-y", "ts-docs-mcp"]
}
}
}
Cursor: Settings → MCP → Add Server → paste the config above.
Claude Code: claude mcp add ts-docs-mcp -- npx -y ts-docs-mcp
VS Code / Copilot: .vscode/mcp.json → add the entry.
Requirements
- Node.js 20+
- Internet access (fetches from npm registry, GitHub, npm tarballs)
- Package must be on npm with a public GitHub repository (or have @types/ types)
Examples
Get the full API overview:
You → "Show me the axios API"
Agent → calls get_package_docs("axios")
→ gets 83 symbols: types, interfaces, classes, functions
Find a specific symbol:
You → "How do I use Zod's transform method?"
Agent → calls get_package_docs("zod", query="transform")
→ gets ZodEffects.transform with full signature + JSDoc
Why not just use the README / training data?
| Source | Coverage | Version-aware | Freshness |
|---|---|---|---|
| Training data | Variable | ❌ | 6-24 months stale |
| README | ~20% of API | ❌ | Often stale |
| ts-docs-mcp | All exports | ✅ Exact version | ✅ Real-time |
TypeScript .d.ts files + GitHub source are the canonical source of truth — they always reflect the exact installed version.
Development
git clone https://git.827482.xyz/xvantz/ts-docs-mcp.git
cd ts-docs-mcp
npm install
npm run build
npm test # 43 unit tests (5 test files)
npm run test:integration # network tests (skipped in CI)
Project structure
src/
├── registry.ts — npm package metadata + HTTP helpers
├── github.ts — GitHub raw source fetching (BFS, parallel)
├── tarball.ts — .d.ts extraction from tarball + DefinitelyTyped
├── parser.ts — Two-phase JSDoc + declaration parser
├── format.ts — Markdown output (summary + detail)
├── throttle.ts — Per-endpoint token-bucket rate limiter
├── cache.ts — XDG file cache with 24h TTL
├── types.ts — PublicSymbol, PackageInfo interfaces
└── index.ts — MCP server (thin handler)
License
MIT
Built because AI coding agents deserve better than hallucinated APIs.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
E2B
Using MCP to run code via e2b.