agentic-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTIC_SEARCH_ROOT | No | The folder the server is allowed to search. Paths are resolved against this search root; one server process serves one root. | the current working directory |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| readA | Read a text file and return numbered lines. Args: path: File path, absolute or relative to the search root. offset: Zero-based line number to start from (default 0). limit: Maximum number of lines to return (default 2000). |
| globA | Find files and directories matching a glob pattern. Args:
pattern: A pathlib-style glob, e.g. |
| grepA | Search file contents with a regular expression (or a literal string).
Set Args:
pattern: Regular expression (Python |
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 3 tools
The three tools map onto the classic, well-separated search primitives: file discovery (glob), content search (grep), and file inspection (read). There is no plausible way to confuse them, and the descriptions explicitly clarify boundaries (e.g. grep is regex, not shell grep; glob is for paths, not contents).
All names are short, lowercase, unprefixed, and drawn from established CLI vocabulary, so the set reads predictably. The only minor deviation is that 'read' is a bare verb while 'glob' and 'grep' are tool-name nouns, but this matches developer expectations rather than causing confusion.
Three tools is lean but deliberate for a focused read-only search server; each tool earns its place with no redundant overlap. It sits at the low end of the comfortable range, which is acceptable given how narrow the stated purpose is.
The surface covers the full read-only search lifecycle: find files, search their contents, then open and page through them, with filters and result caps that make each step composable. There are no write/edit or file-metadata operations, but those fall outside the implied search-and-read scope, so the gap is minor.