ts-docs-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ts-docs-mcpGet the API documentation for lodash version 4.17.21"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 optionsModels know about libraries, but they don't know which version you have installed or what the current API looks like.
Related MCP server: @particle-academy/docs-mcp
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,@returnsFollows re-exports to find actual declarations (BFS, parallel fetches)
Falls back to
.d.tsfrom the npm tarball if GitHub source is insufficientFalls 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 API docs for any npm package. Optional |
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, functionsFind 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 + JSDocWhy 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.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/xvantz/ts-docs-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server