mcp-xpath
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| xpathC | Select query XML content using XPath |
| xpathwithurlC | Fetch content from a URL and select query it using XPath |
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: 'xpath' operates on provided XML content, while 'xpathwithurl' fetches content from a URL before applying XPath. There is no overlap or ambiguity between them.
Both tool names follow a consistent pattern: they start with 'xpath' and use descriptive suffixes ('withurl') without mixing conventions. The naming is straightforward and predictable.
With only 2 tools, the server feels thin for an XPath utility domain, as it lacks operations like validating XPath expressions, handling different input formats, or providing transformation capabilities. However, it covers basic use cases.
The tools cover core XPath querying on local and remote content, but there are notable gaps: no support for XML validation, error handling, or output formatting. The surface is functional but minimal for a full-featured XPath toolset.