Use with AI

Let AI coding tools (Cursor, Claude Code, VS Code + Copilot/Cline, Windsurf, etc.) read this API documentation while writing your integration code.

Option 1 — Plain-text docs (no setup)

Every page of this site is available as raw Markdown for AI consumption:

/llms.txt — index of all documentation pages
/llms-full.txt — the entire documentation in one file
The machine-readable OpenAPI spec: /openapi/artguru-open-api.json

Point your AI tool at any of these URLs — no installation required.

Option 2 — MCP server

For richer integration (endpoint listing, per-endpoint schema lookup, optional real API invocation), add an MCP server backed by this site's OpenAPI spec. Add the following to your tool's MCP configuration (e.g. .cursor/mcp.json, claude mcp add, or your IDE's MCP settings):

{
  "mcpServers": {
    "artguru-api-docs": {
      "command": "npx",
      "args": ["-y", "@ivotoby/openapi-mcp-server@1.16.1"],
      "env": {
        "API_BASE_URL": "https://api.artguru.ai",
        "OPENAPI_SPEC_PATH": "https://docs.artguru.ai/openapi/artguru-open-api.json",
        "TOOLS_MODE": "dynamic"
      }
    }
  }
}

This exposes three tools to your AI assistant: list-api-endpoints, get-api-endpoint-schema, and invoke-api-endpoint.

Node.js >= 18 must be installed.

Read-only by default

With the configuration above, the AI can only read the API documentation — it cannot call the Artguru API on your behalf. To allow real API calls (invoke-api-endpoint), additionally provide your key:

"env": {
  "API_HEADERS": "x-api-key:<your_api_key>"
}

Only do this if you want the AI to execute real, credit-consuming requests.

Supply-chain note

@ivotoby/openapi-mcp-server is a community-maintained package. The version is pinned above on purpose — avoid @latest so that an unreviewed release cannot run on your machine automatically.

Option 1 — Plain-text docs (no setup)​

Option 2 — MCP server​

Option 1 — Plain-text docs (no setup)

Option 2 — MCP server