Skip to main content
Glama
enesjakozh
thirdstrandstudio

mcp-xpath

by thirdstrandstudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

XPath MCP サーバー

サードストランドスタジオ

XML コンテンツに対して XPath クエリを実行するための MCP サーバー。

画像

鍛冶屋のバッジ

ツール

  1. xpath

    • XPath式を使用してXMLコンテンツをクエリする

    • 入力:

      • xml (文字列): クエリするXMLコンテンツ

      • query (文字列): 実行するXPathクエリ

      • mimeType (オプション、文字列): MIME タイプ (例: text/xml、application/xml、text/html、application/xhtml+xml)

    • 戻り値: XPathクエリの結果を文字列として返します

  2. xpathwithurl

    • URL からコンテンツを取得し、XPath 式を使用してクエリを実行します。

    • 入力:

      • url (文字列): XML/HTMLコンテンツを取得するURL

      • query (文字列): 実行するXPathクエリ

      • mimeType (オプション、文字列): MIME タイプ (例: text/xml、application/xml、text/html、application/xhtml+xml)

    • 戻り値: XPathクエリの結果を文字列として返します

Related MCP server: Cleyrop MCP

インストール

Smithery経由でインストール

Smithery経由で Claude Desktop 用の mcp-xpath を自動的にインストールするには:

npx -y @smithery/cli install @thirdstrandstudio/mcp-xpath --client claude
# Install dependencies
npm install

# Build the package
npm run build

設定

Claude Desktopでの使用

claude_desktop_config.jsonに以下を追加します。

npx

{
  "mcpServers": {
    "xpath": {
      "command": "npx",
      "args": [
        "@thirdstrandstudio/mcp-xpath"
      ]
    }
  }
}

直接Node.js

{
  "mcpServers": {
    "xpath": {
      "command": "node",
      "args": [
        "/path/to/mcp-xpath/dist/index.js"
      ]
    }
  }
}

/path/to/mcp-xpathリポジトリへの実際のパスに置き換えます。

例

XMLコンテンツのクエリ

// Select all <item> elements from XML
const result = await callTool("xpath", {
  xml: "<root><item>value1</item><item>value2</item></root>",
  query: "//item/text()",
  mimeType: "text/xml"
});

HTMLコンテンツのクエリ

// Get all links from HTML
const result = await callTool("xpath", {
  xml: "<html><body><a href='link1.html'>Link 1</a><a href='link2.html'>Link 2</a></body></html>",
  query: "//a/@href",
  mimeType: "text/html"
});

クエリURLコンテンツ

// Get all links from a webpage
const result = await callTool("xpathwithurl", {
  url: "https://example.com",
  query: "//a/@href",
  mimeType: "text/html"
});

発達

# Install dependencies
npm install

# Start the server in development mode
npm start

ライセンス

このMCPサーバーはMITライセンスに基づいてライセンスされています。つまり、MITライセンスの条件に従って、ソフトウェアを自由に使用、改変、配布することができます。詳細については、プロジェクトリポジトリのLICENSEファイルをご覧ください。

Available Tools

2 tools
xpathC

Select query XML content using XPath

ParametersJSON Schema
NameRequiredDescriptionDefault
mimeTypeNoThe MIME type (e.g. text/xml, application/xml, text/html, application/xhtml+xml)text/html
queryYesThe XPath query to execute
xmlYesThe XML content to query

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Select query') but doesn't describe what the tool returns (e.g., nodes, values, errors), performance characteristics, or any constraints like input size limits. This leaves significant gaps in understanding the tool's behavior beyond basic functionality.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence: 'Select query XML content using XPath'. It's front-loaded with the core purpose, has zero waste, and is appropriately sized for a straightforward tool. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (XML querying with XPath), no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., extracted data, error handling), which is critical for an agent to use it correctly. The description should compensate for the lack of structured output information but fails to do so.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters (xml, query, mimeType) with clear descriptions. The description adds no additional meaning beyond what the schema provides, such as examples or usage notes for parameters. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Select query XML content using XPath'. It specifies the verb ('Select query') and resource ('XML content'), though it doesn't explicitly distinguish it from its sibling 'xpathwithurl', which likely handles URLs instead of direct XML input. The purpose is clear but lacks sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling 'xpathwithurl' or any other tools, nor does it specify prerequisites or exclusions. Usage is implied from the purpose but lacks explicit context or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

xpathwithurlC

Fetch content from a URL and select query it using XPath

ParametersJSON Schema
NameRequiredDescriptionDefault
mimeTypeNoThe MIME type (e.g. text/xml, application/xml, text/html, application/xhtml+xml)text/html
queryYesThe XPath query to execute
urlYesThe URL to fetch XML/HTML content from

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions fetching content and querying with XPath, but doesn't disclose important behavioral traits such as error handling, network timeouts, authentication needs, rate limits, or what happens with invalid URLs or queries. For a tool that performs network operations and data processing, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise and front-loaded, consisting of a single sentence: 'Fetch content from a URL and select query it using XPath'. Every word contributes directly to explaining the tool's purpose, with no unnecessary information or redundancy. It efficiently communicates the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (network fetching and XPath querying), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., query results, errors), behavioral aspects like performance or limitations, or how to interpret results. For a tool with no structured safety or output information, the description should provide more context to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, clearly documenting all three parameters (url, query, mimeType) with their purposes and types. The description adds minimal value beyond the schema, as it only implies the parameters indirectly ('Fetch content from a URL' hints at 'url', 'select query it using XPath' hints at 'query'). It doesn't provide additional context like examples or constraints, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Fetch content from a URL and select query it using XPath'. It specifies the verb ('fetch', 'select query'), resource ('content from a URL'), and method ('using XPath'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from its sibling tool 'xpath', which might have overlapping functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tool 'xpath' or any other tools, nor does it specify scenarios where this tool is preferred or should be avoided. The description only states what the tool does, not when to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.0
    • First observedxpath
    • First observedxpathwithurl
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 2 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness3/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches