search_symbolsLABSCO SUMMARY
It answers the question a model actually has: what does this thing return, and who implements it.
Searching by return type and by JSDoc description are the queries you cannot make against a pile of .d.ts files in a prompt, and they are exactly what an agent needs when writing against an internal SDK it was never trained on. The repository's own test API is written in a deliberately odd dialect so that a model cannot fake its way through — a good sign about what the project was trying to verify. Read the suspension notice before building on it.
What it is
An MCP server that loads TypeDoc-generated JSON for a TypeScript API and indexes it for querying. Instead of dumping the whole documentation into the prompt, an agent asks targeted questions about the parts it needs.
What you get
search_symbols— find symbols by name, optionally filtered by kindget_symbol_details— full detail for one symbollist_members— the methods and properties of a class or interfaceget_parameter_info— the parameters of a functionfind_implementations— implementations of an interface, or subclasses of a classsearch_by_return_typeandsearch_by_description— find functions by what they return, or by their JSDoc textget_type_hierarchyandfind_usages— inheritance relationships, and where a type or function is used
Requirements
Node.js and npm. Generate the TypeDoc JSON for your API first — there is a documented path for starting from an existing .d.ts file — then run mcp-typescribe with that JSON file as an argument in your client config. Note the banner on the repository: public development is suspended, with the authors directing yFiles users to a successor server.
Setup effort
One command — npx -y mcp-typescribe
USE CASES
01
Writing against an internal SDK the model has never seen
Search for the symbol, read its details and members, and get the parameters right the first time.
02
Finding the function that gives you what you need
Search by return type instead of scanning a type definition file for something plausible.
03
Working out which class to use
Read the type hierarchy and list the implementations of the interface.
04
Judging whether a change is safe
Find where the type or function is used across the documented API.
9 tools
Listed in project docs. Your client may show a different list.
get_symbol_detailslist_membersget_parameter_infofind_implementationssearch_by_return_typesearch_by_descriptionget_type_hierarchyfind_usagesBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y mcp-typescribeMCP Clients
Cline
CLINE · JSON
{
"mcpServers": {
"typescribe": {
"command": "npx",
"args": [
"-y",
"mcp-typescribe@latest",
"run-server",
"<YOUR_PATH_TO_API_DOT_JSON>"
],
"env": {}
}
}
}cline_mcp_settings.json
