An MCP server that answers questions about TypeScript APIs using TypeDoc JSON documentation
If you already use MCP Typescribe, the mcp typescribe mcp server is the piece that lets your assistant work with it directly. An MCP server that answers questions about TypeScript APIs using TypeDoc JSON documentation.
Large Language Models (LLMs) have made incredible strides in code generation and developer productivity. However, they face a key limitation: they can only reliably use APIs and libraries they’ve seen during training. This creates a bottleneck for adopting new tools, SDKs, or internal APIs — LLMs simply don’t know how to use them effectively.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Prerequisites — The Prerequisites tool exposed by this serverInstallation — 1. Clone the repository 2. Install dependencies: bash npm installUsage — If you (only) have an existing.d.ts file, you can create an api json file like so:Building — The Building tool exposed by this servertypedoc on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Typescribe's toolset — Prerequisites, Installation, Usage and 1 more — is a fair guide to whether it matches your workflow. It is maintained by yWorks; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | 1. Clone the repository 2. Install dependencies: bash npm install |
| Usage | If you (only) have an existing.d.ts file, you can create an api json file like so: |
| Building | The Building tool exposed by this server. |
{
"mcpServers": {
"typescribe": {
"command": "npx",
"args": [
"-y",
"mcp-typescribe@latest",
"run-server",
"<PATH_TO_API_DOT_JSON>"
],
"env": {}
}
}
}Configuration as documented by the project. Restart the client after saving.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.