Greply MCP Server
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 |
|---|---|
| greply.searchC | Run the greply CLI to search files with optional context and flags. |
| greply.helpA | Runs greply with no args to print usage. |
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 2 tools
The two tools have clearly distinct purposes: one for displaying usage/help and one for performing searches. There is no overlap in functionality.
Both tools follow a consistent 'greply.<action>' naming pattern, which is predictable and clearly indicates the tool's purpose.
With only two tools, the server is minimal. While a help tool and a search tool cover the basic operations for a CLI wrapper, the low count may leave agents wanting for more functionality.
The tool surface lacks essential operations beyond help and search, such as configuration management, result filtering, or output formatting. Agents may find the server inadequate for complex search tasks.