Repository Analyzer MCP Server

What is Repository Analyzer MCP Server?

Repository Analyzer MCP Server is a Model Context Protocol server that provides tools for analyzing code repositories, with a special focus on Nostr-related projects. It allows AI assistants like Claude to inspect repository structure, search code, view git history, and access file contents from local directories.

How to use Repository Analyzer MCP Server?

Install the project, build it with npm run build, then configure the server in Claude Desktop's claude_desktop_config.json under mcpServers. Set the DEFAULT_REPO_PATH environment variable to specify a default repository, or override it per command with the repoPath parameter.

Key features of Repository Analyzer MCP Server

• Analyze code structure, components, dependencies, and changes
• Search repository code with pattern matching and file filtering
• View git history for entire repo or specific files
• Special tools for NDK (Nostr Development Kit) repos
• Special tools for Nostr Protocol implementations and NIPs
• Access file contents and directory listings via resources

Use cases of Repository Analyzer MCP Server

• Quickly understand the structure of any local codebase
• Debug or inspect Nostr-related repositories (NDK, NIPs)
• Search for patterns across multiple files in a repository
• View recent git changes for a project or specific file
• Analyze React component usage and dependency trees

FAQ from Repository Analyzer MCP Server

What is the difference between generic and specialized analysis tools?

Generic tools (analyze-repo, analyze-code, search-code) work on any repository. Specialized tools (analyze-ndk, analyze-ndk-files, analyze-nostr-protocol) require the repository to follow specific directory structures or naming conventions for NDK and Nostr projects.

How do I analyze multiple repositories?

You can pass a repoPath parameter with any analysis tool command to override the default path. This allows you to analyze different repositories without restarting the server.

What are the runtime dependencies?

You need Node.js to build and run the server. After building with npm run build, it runs as a stdio-based MCP server that Claude Desktop connects to.

Where does the data live?

The server accesses repositories on your local filesystem. You specify the path either via the DEFAULT_REPO_PATH environment variable or per-command with repoPath.

What transport is used?

The server communicates over stdio. It is configured in the Claude Desktop config under mcpServers using the "transport": "stdio" field.