Repository Analyzer MCP Server

A Model Context Protocol (MCP) server for analyzing code repositories with special tools for the Nostr protocol and NDK.

Local serverstdio

What is the Repository Analyzer MCP server?

A Model Context Protocol (MCP) server for analyzing code repositories with special tools for the Nostr protocol and NDK. The repository analyzer mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.

What it actually does

  • Analyze code structure, components, dependencies, and recent changes
  • Search through repository code with pattern matching
  • View git history for the entire repository or specific files
  • Access file content and directory listings
  • Special tools for analyzing NDK (Nostr Development Kit) repositories
  • Analyze Nostr Protocol implementations and NIPs (Nostr Implementation Possibilities)

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

Everything the assistant can do here goes through one of these:

  • Troubleshooting — If Claude Desktop fails to start or the MCP servers don't appear:

Configuration

You will need 2 environment variables: DEFAULT_REPO_PATH, DEBUG. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the repository analyzer mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Repository Analyzer's toolset — Troubleshooting — is a fair guide to whether it matches your workflow. It is maintained by DocNR; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
TroubleshootingIf Claude Desktop fails to start or the MCP servers don't appear:

How to install the Repository Analyzer MCP server

2. Add the server configuration:
```json
{
  "mcpServers": {
    "repo-analyzer": {
      "command": "node",
      "args": [
        "/absolute/path/to/repo-analyzer-mcp/dist/index.js"
      ],
      "transport": "stdio",
      "env": {
        "NODE_ENV": "production",
        "DEFAULT_REPO_PATH": "/path/to/default/repository"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
DEFAULT_REPO_PATHFilesystem location the server is allowed to use.Optional
DEBUGConfiguration value read at startup.Optional

Example prompts to try

  • Use Repository Analyzer to Troubleshooting.

Frequently asked questions

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.