runx MCP server

Which servers in the official MCP registry are runx's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-12

← Back to runx

Whose server it is

Registry nameai.runx/runxverified in the MCP registry

The registry name sits under runx.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-12

Stateanswerschecked 2026-10-12
Tools2
Server calls itselfrunx
Server version1.0.0
Protocol version2025-06-18

On 2026-10-12 the server answered initialize and tools/list without a sign-in. First answer in 148 ms.

Tools it offers2 tools · read 2026-10-12

search_skills
Find runx skills by what they do. Returns each match with its skill id, owner, description, latest version, and trust tier, so a caller can pick one and then read it in full with get_skill.
get_skill
Read one runx skill in full before running it: its manifest, the authority it asks for, its publisher and trust signals, and the exact command to install and run it through the runx CLI. Everything needed to decide whether to trust a…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "runx": {
      "type": "http",
      "url": "https://api.runx.ai/mcp"
    }
  }
}

OpenAPI spec

107 paths, read 2026-10-12. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.