Krep

High-performance string search MCP server with automatic CPU core scaling

javascript

1

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "bmorphism-krep-mcp-server": {
      "command": "node",
      "args": [
        "/path/to/krep-mcp-server/src/index.js"
      ],
      "env": {
        "DEBUG": "true",
        "KREP_PATH": "/path/to/krep-native/krep",
        "CLAUDE_MCP": "true",
        "KREP_TEST_MODE": "true",
        "KREP_SKIP_CHECK": "true"
      }
    }
  }
}

You have a high-performance string search capability that integrates with models and assistants through a Model Context Protocol. This MCP server wraps a fast pattern-matching tool and exposes its functionality in a single, unified interface for file and string searches, with options for counting results and multi-threaded processing.

How to use

You interact with the server through an MCP client by sending a single, unified search request. This server accepts a pattern to locate, a target to search (a file path or a string), and a mode that controls whether you search in a file, search in a string, or count occurrences. You can enable or disable case sensitivity and let the server automatically utilize all available CPU cores for faster results.

How to install

Prerequisites: you need Node.js installed on your machine. You also need the krep binary built and available.

# Build the krep binary if you have the source available
cd /path/to/krep-native
make

# Create or update the MCP config to run the server locally

Follow these steps to set up and run the MCP server locally using a stdio (local) server configuration shown in the example.

# Example MCP configuration (stdio) to run krep MCP server locally
{
  "mcpServers": {
    "krep": {
      "command": "node",
      "args": ["/path/to/krep-mcp-server/src/index.js"],
      "env": {
        "CLAUDE_MCP": "true",
        "KREP_PATH": "/path/to/krep-native/krep",
        "DEBUG": "true"
      },
      "description": "High-performance string search utility with unified interface",
      "disabled": false,
      "autoApprove": ["krep"]
    }
  }
}

Additional sections

Configuration and environment variables provide the runtime behavior of the MCP server. The server runs in MCP mode when CLAUDE_MCP is set to true, and it uses the krep binary path you specify to perform the searches. If you run the server in standard HTTP mode, it exposes a health endpoint and search endpoints for programmatic usage.

Environment variables shown for the server include CLAUDE_MCP, KREP_PATH, and DEBUG. You can also enable test mode with KREP_TEST_MODE and skip binary checks with KREP_SKIP_CHECK when needed.

Security note: run the MCP server with appropriate access controls and avoid exposing the search endpoints to untrusted networks. When deploying publicly, consider putting the server behind authentication and rate limiting.

Available tools

krep

Core high-performance string search function exposed through MCP with unified interface for file and string searches and counting capabilities.

krepSearch

Search a target for a pattern within the MCP server flow.

krepMatch

Match occurrences of a pattern in the given input via MCP.

krepCount

Count occurrences of the pattern in the input, returning a numeric tally.