regex-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| regex_testA | Test a regex pattern against input text. Returns all matches with positions and capture groups. |
| regex_explainB | Get a human-readable, token-by-token explanation of a regex pattern. |
| regex_validateB | Check if a regex pattern is syntactically valid and describe the flags used. |
| regex_replaceB | Find and replace text using a regex pattern. Supports capture group references ($1, $2, etc.) in the replacement string. |
| regex_debugA | Debug a regex pattern against input text. Shows match positions, visual markers, context, and hints when no match is found. |
| regex_generateA | Generate a regex pattern from a natural language description. Supports common patterns like email, URL, IP, phone, date, UUID, and more. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool serves a distinct regex operation (debug, explain, generate, replace, test, validate) with clear descriptions that prevent confusion. Even the similar tools regex_debug and regex_test are differentiated by debug's additional detail.
All tools follow a consistent 'regex_verb' naming pattern with snake_case, making it predictable and easy for an agent to infer functionality from the name alone.
With 6 tools, the server is well-scoped for a regex utility, covering the most common tasks without being bloated or too sparse.
The tool set covers core regex operations, though a potential gap like regex_split is missing. However, the existing tools handle most use cases effectively.