
Tree Hugger JS
Provides JavaScript and TypeScript code analysis through AST parsing. Enables automated code transformations, refactoring, and dependency management with safety previews.
Provides JavaScript and TypeScript code analysis through AST parsing for function extraction, scope analysis, identifier renaming, unused import removal, and code transformation with safety previews and history tracking.
What it does
- Parse JavaScript/TypeScript/JSX/TSX code into AST
- Find code patterns using CSS-like selectors
- Extract functions, classes, and imports with metadata
- Rename identifiers throughout codebase
- Remove unused import statements
- Transform code with preview capabilities
Best for
About Tree Hugger JS
Tree Hugger JS is a community-built MCP server published by qckfx that provides AI assistants with tools and capabilities via the Model Context Protocol. Tree Hugger JS offers advanced JavaScript and TypeScript code analysis, AST parsing, function extraction, and safe code It is categorized under developer tools. This server exposes 12 tools that AI clients can invoke during conversations and coding sessions.
How to install
You can install Tree Hugger JS in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
Tree Hugger JS is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Tools (12)
Parse JavaScript/TypeScript code from file or string and load it into the AST state. Must be called before using other analysis tools. Examples: • Parse a React component: parse_code('./src/UserProfile.jsx') • Parse code string: parse_code('function hello() { return "world"; }') • Parse with explicit language: parse_code('./config.js', language='javascript') • Analyze legacy code: parse_code('./old-script.js') then use other tools to understand structure • Code review prep: parse_code('./feature.ts') then get_functions() to review all functions
Find first node matching the specified pattern using tree-hugger-js intuitive syntax. Use for targeted searches when you need one specific match. Examples: • Find main function: find_pattern('function[name="main"]') • Find React component: find_pattern('function[name="UserProfile"]') • Find async functions: find_pattern('function[async]') • Find specific class: find_pattern('class[name="UserManager"]') • Find error handling: find_pattern('call[text*="catch"]') • Find JSX with props: find_pattern('jsx:has(jsx-attribute[name="className"])') • Debug specific calls: find_pattern('call[text*="console.log"]')
Find all nodes matching the specified pattern. Use for comprehensive analysis when you need all matches. Examples: • Audit all functions: find_all_pattern('function') • Find all TODO comments: find_all_pattern('comment[text*="TODO"]') • Security audit: find_all_pattern('call[text*="eval"]') • Performance review: find_all_pattern('call[text*="console.log"]') to find debug logs • API usage: find_all_pattern('call[text*="fetch"]') to find all API calls • React hooks: find_all_pattern('call[text*="use"]') for hooks usage • Error patterns: find_all_pattern('string[text*="error"]') for error messages • Database queries: find_all_pattern('string[text*="SELECT"]') for SQL • Event handlers: find_all_pattern('function[text*="onClick"]')
Get all functions with metadata including name, type, location, and async status. Includes class methods, arrow functions, and declarations. Examples: • Code review: get_functions() to see all functions in a file • Find async operations: get_functions({asyncOnly: true}) • API analysis: get_functions() then look for functions with 'fetch' or 'api' in names • Test coverage: get_functions() to identify functions needing tests • Refactoring prep: get_functions({includeAnonymous: false}) to focus on named functions • Performance audit: get_functions() to find large/complex functions by line count
Get all classes with comprehensive method and property analysis. Perfect for OOP code review. Examples: • Architecture review: get_classes() to understand class structure • API design: get_classes() to see public method interfaces • Inheritance analysis: get_classes() to identify class hierarchies • Method-only view: get_classes({includeProperties: false}) to focus on behavior • Property audit: get_classes({includeMethods: false}) to review state management • Testing prep: get_classes() to identify methods needing unit tests
Tree-Hugger-JS MCP Server
An MCP (Model Context Protocol) server that provides AI agents with powerful JavaScript/TypeScript code analysis and transformation capabilities using the tree-hugger-js library.
Features
🔍 Code Analysis
- Parse JavaScript, TypeScript, JSX, and TSX files or code strings
- Find patterns using intuitive syntax (e.g.,
function,class[name="MyClass"]) - Extract functions, classes, imports with detailed metadata
- Navigate AST nodes and analyze code structure
- Get nodes at specific positions
🔧 Code Transformation
- Rename identifiers throughout code
- Remove unused imports
- Chain multiple transformations
- Insert code before/after patterns
- Preview transformations before applying
📊 Code Intelligence
- Scope analysis and variable binding
- Pattern matching with CSS-like selectors
- Support for async functions, classes, methods
- TypeScript type import handling
Installation & Usage
🚀 Quick Start (Recommended)
Try immediately with npx - no installation required:
# Use with Claude Code or any MCP client
npx tree-hugger-js-mcp
📦 Global Installation
# Install globally for repeated use
npm install -g tree-hugger-js-mcp
# Then run anywhere
tree-hugger-js-mcp
🔧 Development Setup
# Clone and build from source
git clone https://github.com/qckfx/tree-hugger-js-mcp.git
cd tree-hugger-js-mcp
npm install
npm run build
npm start
MCP Client Configuration
Using with Claude Code
Add to your MCP client configuration:
{
"mcpServers": {
"tree-hugger-js": {
"command": "npx",
"args": ["tree-hugger-js-mcp"]
}
}
}
Alternative Configurations
{
"mcpServers": {
"tree-hugger-js": {
// If installed globally
"command": "tree-hugger-js-mcp"
// Or if built from source
"command": "node",
"args": ["/path/to/tree-hugger-js-mcp/build/index.js"]
}
}
}
Tools
Code Analysis Tools
parse_code
Parse JavaScript/TypeScript code from file or string.
Parameters:
source(string): File path or code string to parseisFilePath(boolean, optional): Whether source is a file path (auto-detected if not provided)language(string, optional): Language to use (javascript, typescript, jsx, tsx)
Example:
// Parse a file
await callTool("parse_code", {
source: "./src/app.js",
isFilePath: true
});
// Parse code string
await callTool("parse_code", {
source: "function hello() { console.log('world'); }"
});
find_pattern
Find first node matching a pattern.
Parameters:
pattern(string): Pattern to match using tree-hugger-js syntax
Examples:
// Find any function
await callTool("find_pattern", { pattern: "function" });
// Find async functions
await callTool("find_pattern", { pattern: "function[async]" });
// Find class by name
await callTool("find_pattern", { pattern: "class[name='MyClass']" });
find_all_pattern
Find all nodes matching a pattern.
Parameters:
pattern(string): Pattern to matchlimit(number, optional): Maximum matches to return
get_functions
Get all functions with details.
Parameters:
includeAnonymous(boolean, optional): Include anonymous functions (default: true)asyncOnly(boolean, optional): Only return async functions (default: false)
get_classes
Get all classes with methods and properties.
Parameters:
includeProperties(boolean, optional): Include class properties (default: true)includeMethods(boolean, optional): Include class methods (default: true)
get_imports
Get all import statements.
Parameters:
includeTypeImports(boolean, optional): Include TypeScript type-only imports (default: true)
Code Transformation Tools
rename_identifier
Rename all occurrences of an identifier.
Parameters:
oldName(string): Current identifier namenewName(string): New identifier namepreview(boolean, optional): Return preview only (default: false)
Example:
await callTool("rename_identifier", {
oldName: "fetchData",
newName: "fetchUserData",
preview: true
});
remove_unused_imports
Remove unused import statements.
Parameters:
preview(boolean, optional): Return preview only (default: false)
transform_code
Apply multiple transformations in sequence.
Parameters:
operations(array): Array of transformation operationspreview(boolean, optional): Return preview only (default: false)
Example:
await callTool("transform_code", {
operations: [
{ type: "rename", parameters: { oldName: "oldFunc", newName: "newFunc" } },
{ type: "removeUnusedImports" },
{ type: "replaceIn", parameters: { nodeType: "string", pattern: /localhost/g, replacement: "api.example.com" } }
],
preview: true
});
insert_code
Insert code before or after nodes matching a pattern.
Parameters:
pattern(string): Pattern to match for insertion pointscode(string): Code to insertposition(string): "before" or "after"preview(boolean, optional): Return preview only (default: false)
Navigation Tools
get_node_at_position
Get AST node at specific line and column.
Parameters:
line(number): Line number (1-based)column(number): Column number (0-based)
analyze_scopes
Analyze variable scopes and bindings.
Parameters:
includeBuiltins(boolean, optional): Include built-in identifiers (default: false)
Resources
The server provides three resources for accessing internal state:
ast://current
Current parsed AST state with metadata and statistics.
ast://analysis
Results from the most recent code analysis (functions, classes, imports).
ast://transforms
History of code transformations and available operations.
Pattern Syntax
Tree-hugger-js uses intuitive patterns instead of verbose tree-sitter node types:
Basic Patterns
function- Any function (declaration, expression, arrow, method)class- Class declarations and expressionsstring- String and template literalsimport/export- Import/export statementscall- Function callsloop- For, while, do-while loops
Attribute Selectors
[name="foo"]- Nodes with specific name[async]- Async functions[text*="test"]- Nodes containing text
CSS-like Selectors
class method- Methods inside classesfunction > return- Return statements directly in functions:has()and:not()pseudo-selectors
Examples
Basic Code Analysis
// Parse and analyze a React component
await callTool("parse_code", { source: "./components/UserProfile.jsx" });
// Get all functions
const functions = await callTool("get_functions", { asyncOnly: true });
// Find JSX elements
const jsxElements = await callTool("find_all_pattern", { pattern: "jsx" });
Code Refactoring
// Rename a function and remove unused imports
await callTool("transform_code", {
operations: [
{ type: "rename", parameters: { oldName: "getUserData", newName: "fetchUserProfile" } },
{ type: "removeUnusedImports" }
]
});
Pattern Matching
// Find all async functions that call console.log
await callTool("find_all_pattern", {
pattern: "function[async]:has(call[text*='console.log'])"
});
// Find classes with constructor methods
await callTool("find_all_pattern", {
pattern: "class:has(method[name='constructor'])"
});
Development
# Install dependencies
npm install
# Build the project
npm run build
# Watch mode for development
npm run dev
# Test with MCP inspector
npm run inspector
Error Handling
The server provides detailed error messages and suggestions:
- File not found errors for invalid file paths
- Parse errors with helpful context
- Pattern matching errors with suggestions
- Transformation errors with rollback capability
License
MIT
Alternatives
Related Skills
Browse all skillsUI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.
Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.
Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
Integrate Vercel AI SDK applications with You.com tools (web search, AI agent, content extraction). Use when developer mentions AI SDK, Vercel AI SDK, generateText, streamText, or You.com integration with AI SDK.
Use when building MCP servers or clients that connect AI systems with external tools and data sources. Invoke for MCP protocol compliance, TypeScript/Python SDKs, resource providers, tool functions.