Model Context Protocol

The Applivery docs, inside your AI assistant

Connect Claude, Cursor, VS Code or any MCP client to the Applivery documentation — the guides and the full REST API reference. Your assistant reads the same pages you browse here and answers with sources.

https://docs.applivery.com/mcp
  • Read-only
  • No API key
  • Nothing to install

What your assistant can do

Five focused tools — the guides and the whole REST API reference, in machine-readable form.

Docs
search_docs

Search the documentation by keyword or phrase. Returns matching pages with titles, snippets, and links.

Try asking

“How do I enroll Android devices with zero-touch?”

Docs
get_doc_page

Read the full Markdown of a specific page, by its URL or by locale and slug.

Try asking

“Read the Getting started guide and summarize it.”

Docs
list_doc_sections

List the top-level documentation sections to get oriented before drilling in.

Try asking

“What areas do the Applivery docs cover?”

API
list_api_endpoints

Browse the REST API catalog — filter by product, group or HTTP method to map the whole API surface.

Try asking

“Which endpoints manage Android web apps?”

API
get_api_endpoint

Get the machine-readable OpenAPI definition of one endpoint: method, path, auth, parameters and schemas.

Try asking

“Build the request to delete a web app.”

Set up your client

A hosted endpoint — pick your client, paste the config and start asking. Nothing runs locally.

  1. Pick your client

    Claude Code, Cursor, VS Code, Cline, Windsurf or Claude.ai.

  2. Add the endpoint

    Paste one line of config — no API key, no account.

  3. Ask away

    Your assistant now searches and cites these docs.

One-click setup
or
Manual configuration
{
  "mcpServers": {
    "applivery-docs": {
      "url": "https://docs.applivery.com/mcp"
    }
  }
}

Add to ~/.cursor/mcp.json

Manual configuration
{
  "servers": {
    "applivery-docs": {
      "type": "http",
      "url": "https://docs.applivery.com/mcp"
    }
  }
}

Add to .vscode/mcp.json

Manual configuration
{
  "mcpServers": {
    "applivery-docs": {
      "url": "https://docs.applivery.com/mcp"
    }
  }
}

Add to ~/.cline/mcp_settings.json

Manual configuration
{
  "mcpServers": {
    "applivery-docs": {
      "url": "https://docs.applivery.com/mcp"
    }
  }
}

Add to ~/.windsurf/mcp.json

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

Add to ~/.claude/settings.json

Remote MCP server URL
https://docs.applivery.com/mcp

Paste in Settings → Connectors → Add custom connector → Remote MCP server URL

How it works

A thin, stateless adapter between your assistant and the published documentation.

Your assistant calls a tool

It picks one of the five tools — from search_docs to get_api_endpoint — and sends the request to the endpoint.

The server reads the public docs

It queries the documentation search, fetches published Markdown pages, and reads the section index and the machine-readable API catalog.

You get answers with sources

Results link back to the exact pages on this site, so every claim is easy to verify.

It never connects to the Applivery dashboard or any private system.

Frequently asked questions

Do I need an API key or an account?

No. The server is read-only and reads only the public documentation, so no API key, token, or account is required.

Which assistants and editors are supported?

Any MCP-compatible client that supports remote (HTTP) servers — Claude Code, Cursor, VS Code, Cline, Windsurf, and Claude.ai — by adding the URL above.

What can it access?

Only the published, public documentation — the guides and the REST API reference, the same pages on this site. It cannot reach private content, dashboards, or the CMS.

Do I need to install anything?

No. It is a hosted endpoint — add the URL above in your client and you are done; nothing runs locally.

Give your assistant the whole manual

One URL, two minutes of setup — every Applivery answer, right where you work.