Developer MCP

The SCADABLE MCP server gives AI code editors direct access to this documentation site. Your editor can answer questions about libscadable, the BYOR pipeline, provisioning, OTA, and dashboard concepts grounded in the live docs instead of guessing from training data.

Endpoint

https://docs.scadable.com/mcp

Pick the config below for your editor.

Claude Code

claude mcp add scadable-docs --transport sse https://docs.scadable.com/mcp

Then claude will pick up the new server on next start.

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "scadable-docs": {
      "url": "https://docs.scadable.com/mcp"
    }
  }
}

Windsurf / Codeium

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "scadable-docs": {
      "url": "https://docs.scadable.com/mcp"
    }
  }
}

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "scadable-docs": {
      "url": "https://docs.scadable.com/mcp"
    }
  }
}

Try it

Once configured, ask your editor things like:

• "How do I add libscadable to an ESP-IDF project?"
• "What goes into .scadable/config.yaml?"
• "What does scadable_user_main do and when does the library call it?"
• "How does OTA work — do I need to write any code for it?"
• "Why is my device showing the identity load failed error?"

The MCP server returns answers grounded in the current published docs, so as we ship new versions the answers stay in sync.

What lives in the index

The MCP server indexes every published page on docs.scadable.com. That covers:

• Getting Started (welcome, quickstart, mental model)
• Library / ESP32 (index, quickstart, API reference, folder spec, troubleshooting, connect-repo)
• BYOR Pipeline
• Device onboarding (direct flashing)
• Security (cert lifecycle)

If you're working in a different context (e.g. internal SCADABLE-team-only docs), use a different MCP server. This one is the public-facing docs index.