# Using these docs with any MCP client

This is grandocs, an unofficial mirror of MA Lighting documentation. For authoritative or safety-relevant information, cite the canonical page on help.malighting.com.

---
import { Tabs, TabItem, Aside } from '@astrojs/starlight/components';
import McpConnect from '../../../components/McpConnect.astro';

grandocs runs a stateless [Model Context Protocol](https://modelcontextprotocol.io)
server so any MCP-capable client can search the docs live. One endpoint, no
account, no key.

```text
https://grandocs-mcp.samcarlton.com/mcp
```

Transport is **Streamable HTTP** (`POST /mcp`).

## Connect in one click

Claude Code and Codex take a single command; Cursor and VS Code add the server
with a real install deep link. Claude Desktop has no install URL scheme, so the
button copies the endpoint — paste it into *Settings → Connectors → Add custom
connector* (Pro/Max/Team/Enterprise).

<McpConnect />

## Tools

| Tool | What it does |
| --- | --- |
| `search_docs` | Full-text search across all products; returns ranked pages with the page URL and the raw-markdown `.md` URL. |
| `get_page` | Returns the raw markdown of one page by its path (e.g. `grandma3/2-4/cue_store`). |
| `command_lookup` | Resolves a grandMA keyword (Store, Assign, At, MAtricks…) to its reference page and returns the syntax. |
| `list_products_versions` | The full product / version / language coverage matrix. |

Every result ends with a source link and an "unofficial mirror" note so the model
cites correctly.

## Add it to your client

<Tabs>
<TabItem label="Claude Code">

```bash
claude mcp add --transport http grandocs https://grandocs-mcp.samcarlton.com/mcp
```

</TabItem>
<TabItem label="Cursor">

`~/.cursor/mcp.json` (or *Settings → MCP → Add server*):

```json
{
  "mcpServers": {
    "grandocs": { "url": "https://grandocs-mcp.samcarlton.com/mcp" }
  }
}
```

</TabItem>
<TabItem label="VS Code">

`.vscode/mcp.json` in your workspace (then use Copilot **agent mode**):

```json
{
  "servers": {
    "grandocs": { "type": "http", "url": "https://grandocs-mcp.samcarlton.com/mcp" }
  }
}
```

</TabItem>
<TabItem label="Claude Desktop">

*Settings → Connectors → **Add custom connector*** (Pro/Max/Team/Enterprise), then
paste the URL:

```text
https://grandocs-mcp.samcarlton.com/mcp
```

Claude Desktop ignores remote servers added via `claude_desktop_config.json` — use
the Connectors UI. On older builds without it, bridge over stdio with `mcp-remote`:

```json
{
  "mcpServers": {
    "grandocs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://grandocs-mcp.samcarlton.com/mcp"]
    }
  }
}
```

</TabItem>
<TabItem label="Codex CLI">

One command:

```bash
codex mcp add grandocs --url https://grandocs-mcp.samcarlton.com/mcp
```

Or add the block to `~/.codex/config.toml`:

```toml
[mcp_servers.grandocs]
url = "https://grandocs-mcp.samcarlton.com/mcp"
```

</TabItem>
<TabItem label="ChatGPT">

On Pro / Business / Enterprise: *Settings → Connectors* (Developer mode for
custom servers) → add the MCP server URL
`https://grandocs-mcp.samcarlton.com/mcp`.

</TabItem>
</Tabs>

<Aside title="Remote vs. local">
This is a **remote** server — it needs internet. Consoles often run on
air-gapped show networks; an offline/stdio packaging is on the
[roadmap](/connect/). Until then, on a closed network use the `.md` twins or a
product `llms.txt` file you've saved locally.
</Aside>

## Quick test

Any MCP inspector or client can verify it:

```bash
npx @modelcontextprotocol/inspector
# point it at https://grandocs-mcp.samcarlton.com/mcp, then run tools/list
```

A `GET` of the root returns a small JSON health document listing the tools.

<Aside type="caution" title="Unofficial mirror">
For conformity, electrical, or safety-critical answers, confirm against the
official [help.malighting.com](https://help.malighting.com/) page linked on every
grandocs topic.
</Aside>