@towry/mcp

MCP (Model Context Protocol) server for fast semantic codebase search.

Installation

pnpm add @towry/mcp
# or
npm install @towry/mcp

Usage

As a CLI

pnpm dlx @towry/mcp

With Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "towry-mcp": {
      "command": "npx",
      "args": ["@towry/mcp"]
    }
  }
}

Available Tools

grep_fast

Fast semantic codebase search. It first narrows files by keywords and filePatterns, then runs sgrep on the filtered set.

Parameters:

• cwd (string, required): Working directory to search in
• keywords (string[], required): Specific grep patterns such as "login|signin"
• filePatterns (string[], required): Specific filename globs such as "*auth*"
• semanticQuery (string, required): Natural-language query for semantic search

Development

# Install dependencies
pnpm install

# Build
pnpm build

# Watch mode
pnpm dev

# Lint
pnpm lint

# Type check
pnpm typecheck

Debugging with MCP Inspector

The MCP Inspector is a browser-based tool for testing and debugging MCP servers.

Quick Start

# Using the package script (recommended)
pnpm inspect

# Or manually
pnpm dlx @modelcontextprotocol/inspector node dist/index.js

# Debug in watch mode (rebuild first, then run inspector)
pnpm build && npx @modelcontextprotocol/inspector node dist/index.js

Inspector Features

Once the inspector opens in your browser (default: http://localhost:6274):

1. Tools Tab: List all available tools, view their schemas, and execute them with test parameters
2. Resources Tab: Browse any resources exposed by the server
3. Prompts Tab: Test prompt templates
4. Notifications Pane: View real-time server notifications and logs

Development Workflow

# Terminal 1: Watch and rebuild on changes
pnpm dev

# Terminal 2: Run inspector (restart after rebuilds)
pnpm inspect

CLI Mode

For quick testing without the browser UI:

pnpm dlx @modelcontextprotocol/inspector --cli node dist/index.js

Debugging Tips

• Check tool schemas: Use the Tools tab to verify parameter types and descriptions
• Test edge cases: Try empty inputs, invalid types, missing required fields
• Monitor errors: Watch the Notifications pane for server-side errors
• Verify search flow: Test grep_fast with a small repository and focused keywords first

License

MIT