Skip to content

Documentation MCP

Connect Claude, Cursor, VS Code, and other AI tools directly to Rhombus API documentation using the Model Context Protocol (MCP) server.

On this page

The Model Context Protocol (MCP) is an open standard that creates standardized connections between AI applications and external services. Rhombus provides an MCP server that gives AI tools like Claude Code, Cursor, and Claude Desktop instant access to our complete API documentation.

Info

Quick Access

Rhombus Developer Documentation MCP Server: https://developer.rhombus.com/mcp

Why use the Documentation MCP?

Instant Documentation Access

AI assistants can search and retrieve relevant documentation without leaving your workflow

Always Up-to-Date

Automatically synced with the latest Rhombus API documentation

Context-Aware Assistance

AI tools understand your API and provide accurate, documentation-backed responses

Faster Development

Get answers about endpoints, parameters, and examples instantly while coding

What's included

The Rhombus Documentation MCP provides:

  • Search Tool: Query the complete Rhombus API documentation
  • Endpoint Information: Details about all available API endpoints
  • Code Examples: Access to implementation examples and best practices
  • Authentication Guide: Information about API keys and authentication methods
  • Integration Patterns: Video player implementations and advanced use cases

Setup instructions

Choose your AI tool below for setup instructions:

Add MCP to Claude Code

Claude Code makes it simple to add MCP servers with a single command.

  1. Open Terminal

    Open your terminal or command prompt

  2. Run MCP Add Command

    Execute the following command:

    bash
    claude mcp add --transport http rhombus-docs https://developer.rhombus.com/mcp

    This adds the Rhombus documentation MCP with the name rhombus-docs.

  3. Verify Installation

    The MCP will be immediately available in Claude Code. You can verify by asking:

    "Search the Rhombus documentation for camera endpoints"

    Claude Code will now use the MCP to retrieve accurate documentation.

Using the MCP in Claude Code

Once configured, Claude Code will automatically:

  • Search documentation when you ask API-related questions
  • Reference specific endpoints when building integrations
  • Provide code examples from the documentation
  • Suggest best practices based on official guides

Example queries:

  • "How do I authenticate with the Rhombus API?"
  • "Show me camera endpoints for retrieving video"
  • "What parameters does the access control API accept?"
  • "How do I implement the video player?"

Available tools

The Rhombus Documentation MCP provides the following tools to AI assistants:

search_rhombus_developer

Search the complete Rhombus documentation

This tool allows AI assistants to search through all documentation pages, including:

  • API endpoint references
  • Authentication guides
  • Implementation examples
  • Video player documentation
  • Best practices and tutorials

Example Usage:

Tool: search_rhombus_developer
Query: "camera video streaming endpoints"

Results: Returns relevant documentation snippets with links to full pages. Pass an optional language code (for example es) to search a translated version.

query_docs_filesystem_rhombus_developer

Read documentation pages and OpenAPI specs directly

Runs read-only, shell-like commands against an in-memory filesystem that contains every documentation page (as .mdx) and the OpenAPI specs:

  • ls / tree to explore the documentation structure
  • cat / head to read a full page
  • rg for exact keyword or regex matches

This is how AI assistants read a complete page — there is no separate "get page" tool.

Example Usage:

Tool: query_docs_filesystem_rhombus_developer
Command: head -200 /api-reference/overview.mdx

Results: Returns the raw page content or search matches from the documentation filesystem.

Example workflows

Building a video integration

  1. Ask About Video Endpoints
    "What endpoints do I need to stream video from a Rhombus camera?"

    The MCP will search documentation and provide relevant endpoints with descriptions.

  2. Get Implementation Details
    "Show me how to implement the DashJS video player"

    Retrieves the complete video player implementation guide with code examples.

  3. Ask About Authentication
    "How do I authenticate for video streaming?"

    Provides federated token authentication details and code samples.

  4. Request Specific Examples
    "Give me a complete JavaScript example for streaming video"

    Returns working code examples from the documentation.

Exploring access control

  1. Discover Endpoints
    "List all access control endpoints in the Rhombus API"

    MCP searches and returns comprehensive list of access control endpoints.

  2. Understand Parameters
    "What parameters does createAccessGrant accept?"

    Retrieves detailed parameter documentation for the specific endpoint.

  3. See Examples
    "Show me an example of creating an access grant"

    Provides code examples and usage patterns from documentation.

Best practices

Be Specific in Queries

Ask targeted questions about specific endpoints or features for better results

Reference by Name

Mention "Rhombus API" or specific endpoint names to get focused documentation

Request Code Examples

Explicitly ask for code examples when you need implementation help

Follow Up Questions

Ask follow-up questions to drill deeper into specific topics

Troubleshooting

MCP Not Responding

Possible causes:

  • MCP server URL is incorrect
  • Network connectivity issues
  • Tool needs to be restarted

Solutions:

  1. Verify the URL: https://developer.rhombus.com/mcp
  2. Check your internet connection
  3. Restart your AI tool
  4. Re-add the MCP configuration
No Results Found

Try these approaches:

  • Rephrase your question more specifically
  • Use exact endpoint names or feature names
  • Break complex questions into simpler queries
  • Check if you're asking about a feature that exists in Rhombus API
Outdated Information

The MCP server automatically syncs with the latest documentation. If you suspect outdated information:

  • The documentation may have been recently updated
  • Try rephrasing to get different results
  • Verify against the online documentation
Configuration Not Loading

For command-line tools:

bash
# Remove and re-add the MCP
claude mcp remove rhombus-docs
claude mcp add --transport http rhombus-docs https://developer.rhombus.com/mcp

For GUI tools:

  • Remove the MCP configuration
  • Restart the application
  • Re-add the configuration
  • Verify the URL is exactly: https://developer.rhombus.com/mcp

Privacy & security

Info

Data Privacy

The MCP server only provides access to public Rhombus API documentation. No private data, API keys, or user information is transmitted through the MCP.

What the MCP provides:

  • Public API documentation
  • Code examples
  • Integration guides
  • Best practices

What the MCP does NOT provide:

  • Your API keys or credentials
  • Customer-specific data
  • Private account information
  • Unreleased features or internal documentation

Additional resources

Feedback

Have suggestions for improving the Documentation MCP?