MCP integration

Overview

The Model Context Protocol (MCP) lets AI assistants and IDEs pull live context from external sources. Two ways to wire Revieve in:

1. Docs server — point an off-the-shelf docs MCP server at https://api.revieve.com. The assistant can then ground answers in the canonical docs without any custom code.
2. API server — generate an MCP server from the OpenAPI spec so the assistant can call the API itself, not just read about it.

Both are config-only; you don’t need to write code to set either up.

Docs server (read-only)

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "revieve-docs": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-fetch",
        "https://api.revieve.com/llms-full.txt"
      ]
    }
  }
}

Restart Claude Desktop. Claude will treat the docs as a queryable context source.

Continue

In ~/.continue/config.json:

{
  "contextProviders": [
    {
      "name": "url",
      "params": {
        "url": "https://api.revieve.com/llms-full.txt"
      }
    }
  ]
}

Cursor

Cursor reads docs from any URL via the @docs provider. Add https://api.revieve.com/llms-full.txt in Settings → Features → Docs.

API server (read + call)

Generate an MCP server from the OpenAPI spec and wire it into the same client config. Several open-source generators do this; one example using @modelcontextprotocol/openapi-mcp-server:

{
  "mcpServers": {
    "revieve-api": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/openapi-mcp-server",
        "--spec",
        "https://api.revieve.com/openapi/skin-analysis.yaml",
        "--base-url",
        "https://partner-test.revieve.com/api/3"
      ],
      "env": {
        "REVIEVE_PARTNER_ID": "jmlv6b2qtS"
      }
    }
  }
}

The MCP server exposes each OpenAPI operation as an MCP tool the assistant can call directly — no SDK install required.

Don't ship production credentials this way

The example above uses the public test Partner ID. For production, prefer a personal-machine config with your own ID, and never share that JSON.

What you get

• Grounded answers. The assistant cites specific doc pages when explaining components.
• Up-to-date code. The assistant generates calls against the current spec (3.29.1), not 2023’s pattern-matched suggestions.
• Live API exploration. With the API server, the assistant can run a real analyzeImage call against the test environment as part of an answer.

Discovery shortcuts

• https://api.revieve.com/.well-known/openapi.yaml redirects to the canonical spec.
• https://api.revieve.com/.well-known/ai-plugin.json is a manifest pointing to the spec.
• https://api.revieve.com/llms.txt is the page index in llmstxt.org format.
• https://api.revieve.com/llms-full.txt is every page concatenated.
• Every doc page has a markdown sidecar at <page>.md (for example, /guides/getting-started.md).