Ctrlk
SolidRunCommunitySupportShop
For the complete documentation index, see llms.txt. This page is also available as Markdown.

MCP Server for AI Coding Tools

Connect AI coding tools (Claude Code, Cursor, Windsurf, Continue.dev) to the SolidRun developer documentation via the GitBook MCP server endpoint at https://dev.solid-run.com/~gitbook/mcp.

The SolidRun developer documentation is available to AI coding assistants through an MCP (Model Context Protocol) server. Point a supported tool at the endpoint below and your assistant can read the full developer center: hardware user manuals, BIOS and firmware notes, BSPs, HowTo guides, and reference designs. Once connected, it can answer questions and write code with knowledge of SolidRun boards, SoMs, and platforms instead of guessing. The endpoint serves the same public content as dev.solid-run.com and requires no authentication.

The endpoint

https://dev.solid-run.com/~gitbook/mcp

Use this URL anywhere a tool asks for an MCP server. It is read-only and serves only public documentation.

Setup per tool

Claude Code (CLI)

The Claude Code command-line agent. Add the server with a single command:

claude mcp add solidrun-dev https://dev.solid-run.com/~gitbook/mcp

Verify the connection by asking:

Using solidrun-dev, find the BIOS reset procedure for Bedrock R8000

If the server is connected, the answer cites SolidRun documentation.

Cursor

The Cursor IDE. Add the server to Cursor's MCP configuration:

{
  "mcpServers": {
    "solidrun-dev": {
      "url": "https://dev.solid-run.com/~gitbook/mcp"
    }
  }
}

The config file lives at ~/.cursor/mcp.json (or open Cursor Settings and go to the Model Context Protocol section). After saving, confirm solidrun-dev appears in the MCP server list, then ask your assistant a SolidRun-specific question to verify.

Windsurf

The Windsurf IDE. Add the same server entry to Windsurf's MCP configuration:

Edit it through Windsurf Settings in the MCP section (or the mcp_config.json it points to). Confirm solidrun-dev shows as connected, then ask a SolidRun-specific question to verify.

Continue.dev

The Continue.dev extension for VS Code and JetBrains uses a dedicated file for MCP servers. Create .continue/mcpServers/solidrun-dev.yaml in your workspace (note the plural mcpServers folder):

MCP servers only work in Continue's Agent mode. Switch to Agent mode before testing the connection.

Example queries

Once connected, ask your assistant questions like:

  • "Find the recommended kernel boot parameters for LX2160A on Debian"

  • "Show me the I2C pinout for the i.MX8M Plus SoM"

  • "What are the validated SO-DIMM modules for Bedrock R8000?"

  • "Walk me through flashing UEFI on a HoneyComb LX2"

  • "Compare power consumption between HummingBoard Hailo-15 and i.MX8M Plus SOM under typical AI workload"

How it works

  • The MCP endpoint exposes the same content as dev.solid-run.com itself.

  • It is read-only - connecting a tool cannot modify any documentation.

  • Documentation updates are reflected immediately in MCP responses; there is no rebuild step.

  • The endpoint is public and serves only published content - no authentication is required and no private or draft pages are exposed.

Troubleshooting

  • Tool says the MCP endpoint isn't responding - Verify the URL is exactly https://dev.solid-run.com/~gitbook/mcp, including the tilde (~).

  • Your assistant says it can't find SolidRun docs - Restart the tool; some tools cache their MCP server list at startup.

  • You get results for the wrong product - Be specific in the query: name the product (for example "HummingBoard Hailo-15", not "the board").

Related resources

The developer center also publishes its content as plain markdown for AI and scripting use:

  • /llms.txt - index of all developer documentation pages.

  • /llms-full.txt - full content of all developer documentation in a single file.

  • Per-page markdown - append .md to any documentation page URL to get its raw markdown.

PreviousTooling

Last updated