yWorks/mcp-typescribe
An MCP server implementation enabling LLMs to work with new APIs and frameworks
Platform-specific configuration:
{
"mcpServers": {
"mcp-typescribe": {
"command": "npx",
"args": [
"-y",
"mcp-typescribe"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
> [!CAUTION] > Public development is currently suspended as no active community formed. We are working on a follow-up project, specifically for the yFiles API. You can read more, here: yFiles MCP Server. yFiles developers can use the MCP to query API, development guides, source code snippets and recipes using those tools, instead. They work far better than the implementation in this repository.
[](https://www.npmjs.com/package/mcp-typescribe)
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.
While tools can be given source code access (when interacting with APIs for which the sources are available) or access to documentation files (e.g. typescript type definition files), this doesn't scale well for large APIs. LLMs need a more efficient way to learn more about an API. Putting all the documentation into context for every request is inefficient, unfeasible, and leads to poor results.
Larger new or internal APIs remain "invisible" to LLMs.
Developers must manually guide LLMs or provide example usage.
Innovation is slowed by the lag between an API’s release and its widespread understanding by AI tools.
This project is an open-source implementation of the Model Context Protocol (MCP)—a protocol designed to provide LLMs with contextual, real-time access to information. In this case it's the API documentation, and particularly for now in this project TypeScript definitions.
Parse Typ
Loading reviews...