antientropy-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| antientropy_globA | Find articles matching a glob pattern. Pattern matches against the virtual path: {category_path}/{slug} Examples: '/gdpr', 'policy', 'Governance/*', '**' (all) Returns matching articles with titles and category paths. |
| antientropy_grepA | Search article content with a regex pattern. Returns matches formatted like ripgrep: slug:line_number:matching_line |
| antientropy_readA | Read an article's content by slug. Returns content with line numbers (cat -n format). Use antientropy_glob or antientropy_grep to discover slugs. |
| antientropy_categoriesB | List the category tree of the AntiEntropy Resource Portal. |
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 4 tools
Each tool has a clearly distinct purpose: antientropy_categories lists the category tree, antientropy_glob finds articles by path pattern, antientropy_grep searches article content with regex, and antientropy_read retrieves article content by slug. There is no overlap or ambiguity between these functions.
All tool names follow a consistent 'antientropy_' prefix with descriptive suffixes (categories, glob, grep, read) in snake_case. This pattern is uniform throughout the set, making the tools easily identifiable and predictable.
With 4 tools, the count is reasonable for a resource portal server, covering browsing (categories, glob), searching (grep), and reading (read). It is slightly lean but well-scoped, as each tool serves a distinct and necessary function without redundancy.
The tool set provides a complete workflow for discovering and accessing articles: listing categories, finding articles by path or content, and reading content. Minor gaps might include operations like creating or updating articles, but for a read-only portal, the coverage is sufficient for typical agent tasks.