everything-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| everything_searchB | Search files via Everything |
| everything_countC | Count matching files |
| everything_healthC | Check Everything status |
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
Each tool has a clearly distinct purpose: search returns files, count returns a count, and health checks service status. There is no overlap or ambiguity between them.
All tool names follow a consistent 'everything_verb' pattern, using snake_case throughout. The naming is predictable and uniform.
Three tools is an appropriate scope for a simple Everything integration, covering the essential operations without unnecessary bloat.
For a search-focused tool, the set covers the core capabilities of searching, counting results, and checking server health. There are no obvious missing operations.