Skip to content
Applivery logo

Applivery MCP server

Which servers in the official MCP registry are Applivery'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-16

← Back to Applivery

Whose server it is
  • Registry namecom.applivery.docs/mcpverified in the MCP registry

The registry name sits under applivery.com. 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-16
  • Stateanswerschecked 2026-10-16
  • Tools4
  • Server calls itselfapplivery-docs
  • Server version2.4.0
  • Protocol version2025-06-18

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

Tools it offers4 tools · read 2026-10-16
  • search_docs

    Search the Applivery documentation by keyword or phrase. Returns matching pages with title, canonical URL, a highlighted snippet, docType ('guides' or 'api'), platform, breadcrumb and in-page headings. Use this first to discover pages…

  • get_doc_page

    Fetch the full Markdown content of a documentation page. Pass either `url` (typically a URL returned by search_docs) or `slug` plus `locale`. Returns clean Markdown; very long pages are truncated at `maxChars` with a note.

  • get_api_endpoint

    Get the machine-readable OpenAPI definition of one Applivery REST API endpoint: method, path, baseUrl, security, parameters, requestBody and responses — fully dereferenced, no $refs. Pass the `url` or `slug` of an API reference page; find…

  • list_doc_sections

    List the top-level documentation sections and landing pages from the site's curated index (llms.txt). Use for orientation, then drill in with search_docs or get_doc_page.

How to connect

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

{
  "mcpServers": {
    "applivery": {
      "type": "http",
      "url": "https://docs.applivery.com/mcp"
    }
  }
}

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.