"ts-node" matching MCP servers:

Enables AI agents to navigate JS/TS, HTML, and CSS code — symbol info, outlines, callers, implementations, definitions, references, hover, and diagnostics — through bundled Node language servers. It also builds a cross-file index answering where CSS custom properties and #id/.class selectors are defined and used across stylesheets, markup, and scripts.

MCP server for TypeScript type resolution and dependency graph analysis using ts-morph and madge.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Provides TypeScript and JavaScript code refactoring operations using ts-morph, allowing AST-based symbol renaming, file/folder renaming, reference searching, and path alias removal when integrated with editor extensions like Cursor.

A production-ready template for building Model Context Protocol servers in TypeScript. It provides an example tool, resource, and prompt with a clean separation of transport, registration, and domain logic.

Enables AI agents to search and retrieve jam-nodes documentation, including node info, API references, and guides, via MCP tools without loading everything into context.

Provides real-time TypeScript diagnostics with intelligent caching for AI agents, enabling instant queries instead of running tsc repeatedly.

Provides AI agents with offline access to OPC UA companion specification types, dependencies, and engineering units for industrial modeling.

Deterministic code-graph (GraphRAG) over your repo for LLM agents — local-first, git-native, zero-infra, served via MCP. Python, TS/JS, Rust, Go, Java, C#.

Just to be clear about the final JSON: the MCP server is named herdr-inbox, and it enables Claude Code agents in herdr to ask questions asynchronously without stalling, with all open questions answered from one popup and answers routed back to the asking agent.

Executes Python code in isolated rootless containers while proxying MCP server tools, reducing context overhead by 95%+ and enabling complex multi-tool workflows through sandboxed code execution.

Enables AI coding agents to fetch live MDN Web Docs pages, TypeScript handbook content, and npm package metadata as clean markdown, with local search, caching, and polite throttling.

Enables searching and accessing Dash documentation directly, with tools to list docsets, search snippets, load pages, and enable full-text search.

A lightweight MCP server that provides 40 tools for TypeScript/JavaScript refactoring and code intelligence, directly mapping to TypeScript's tsserver protocol commands for accurate structural changes and workspace analysis.

A Model Context Protocol server that wraps the official Obsidian CLI to allow AI agents to read, write, search, and manage notes within an Obsidian vault. It provides 16 specialized tools for comprehensive vault interaction, including note management, task tracking, and metadata manipulation.

Enables AI coding agents to interact with TypeScript projects through compiler-level code intelligence, providing tools for navigation, type information, diagnostics, refactoring, and semantic search.

MCP server that routes Claude Desktop chat into Claude Code, enabling headless execution and terminal handoff with session continuity.

An MCP server that enables AI agents to move TypeScript files and directories while automatically updating all affected imports using a persistent tsserver instance. This ensures atomic, error-free refactoring that maintains project integrity without manual intervention or wasted tokens.

Scaffolds new MCP servers for the OpenSIN-Code ecosystem with templates for Python, Node, Go; provides tools to add tools, test, validate, register, publish, and audit servers.

Indexes any TypeScript / React / Next.js repo into a queryable code graph and exposes 13 MCP tools — who-renders, who-calls, find-references, blast-radius, find-cycles, dead-code orphans, and local semantic search — so agents query structure instead of reading whole files. Built on ts-morph, so edges are resolved, not grepped.