Skip to main content
Glama
agentic-search-mcp

agentic-search-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENTIC_SEARCH_ROOTNoThe 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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. **/*.py or src/**/*.ts. path: Directory to search within (absolute or root-relative, default root). max_results: Cap on returned matches (default 1000).

grepA

Search file contents with a regular expression (or a literal string).

pattern is a Python re regular expression matched against each line with re.search -- it is not a shell grep command. Use | to combine alternatives, .* for wildcards, and groups/quantifiers such as (foo|bar) or \w+. \| matches a literal pipe character, so do not escape | to mean "or" (GNU grep basic-regex syntax is not used). For example::

grep(pattern="def (load|save)_config|class .*Settings|TODO.*(refactor|migrate)", glob_filter="*.py")

Set literal=True to match plain text with no regex interpretation. Use ignore_case for case-insensitive matching and max_results to cap output; there is no shell pipeline to pipe into head.

Args: pattern: Regular expression (Python re syntax), or literal text when literal is true. Combine alternatives with unescaped |. path: File or directory to search (absolute or root-relative, default root). glob_filter: Optional filename filter, e.g. *.py. literal: Treat pattern as plain text instead of a regex (default false). ignore_case: Case-insensitive matching (default false). max_results: Cap on returned matches (default 100).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

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).

Naming Consistency4/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues