Ai

MCP Server

Connect your AI tools to EletroDS documentation with a native MCP server.

Connect your AI tools to EletroDS documentation with a native MCP server.

About MCP Servers

The Model Context Protocol (MCP) is an open protocol that creates standardized connections between AI applications and external services, like documentation.

EletroDS includes a built-in MCP server, preparing your content for the broader AI ecosystem where any MCP client (like Claude, Cursor, VS Code, and others) can connect to our documentation.

How MCP Servers Work

When an MCP server is connected to an AI tool, the LLM can decide to use your documentation tools during response generation:

  • The LLM can proactively search your documentation while generating a response, not just when explicitly asked.
  • The LLM determines when to use tools based on the context of the conversation and the relevance of your documentation.
  • Each tool call happens during the generation process, allowing the LLM to incorporate real-time information from your documentation into its response.

For example, if a user asks about how to use the MeButton component and the LLM determines that EletroDS documentation is relevant, it can search our docs and include accurate usage examples in the response without the user explicitly asking about our documentation.

Accessing Your MCP Server

The MCP server is automatically available at the /mcp path of the documentation URL.

https://eletro.design/mcp

Built-in Tools

EletroDS provides two tools out of the box that allow any LLM to discover and read our documentation:

list-pages

Lists all documentation pages with their titles, paths, and descriptions. AI assistants should call this first to discover available content.

ParameterTypeDescription
localestring (optional)Filter pages by locale

get-page

Retrieves the full markdown content of a specific documentation page.

ParameterTypeDescription
pathstring (required)The page path (e.g., /getting-started/installation)

Setup

The MCP server uses HTTP transport and can be installed in different AI assistants.

Cursor

Install in Cursor

Or manually create/update the .cursor/mcp.json file in your project root:

.cursor/mcp.json
{
  "mcpServers": {
    "eletrods": {
      "type": "http",
      "url": "https://eletro.design/mcp"
    }
  }
}
For local development, use http://localhost:3000/mcp instead.

Claude Code

Add the server using the CLI command:

Terminal
claude mcp add --transport http eletrods https://eletro.design/mcp

Visual Studio Code

Install in VS Code

Ensure you have GitHub Copilot and GitHub Copilot Chat extensions installed.

Or manually create/update the .vscode/mcp.json file:

.vscode/mcp.json
{
  "servers": {
    "eletrods": {
      "type": "http",
      "url": "https://eletro.design/mcp"
    }
  }
}

Windsurf

  1. Open Windsurf and navigate to Settings > Windsurf Settings > Cascade
  2. Click the Manage MCPs button, then select the View raw config option
  3. Add the following configuration:
.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "eletrods": {
      "type": "http",
      "url": "https://eletro.design/mcp"
    }
  }
}

Zed

  1. Open Zed and go to Settings > Open Settings
  2. Navigate to the JSON settings file
  3. Add the following context server configuration:
.config/zed/settings.json
{
  "context_servers": {
    "eletrods": {
      "source": "custom",
      "command": "npx",
      "args": ["mcp-remote", "https://eletro.design/mcp"],
      "env": {}
    }
  }
}

Usage Example

Once connected, you can ask your AI assistant questions about EletroDS and it will automatically search our documentation:

Example prompt: "How do I create a primary button with EletroDS?"The AI will automatically call list-pages to discover available content, then get-page to retrieve the button component documentation, and provide you with accurate usage examples.

Troubleshooting

Connection Issues

If you're having trouble connecting to the MCP server:

  1. Verify the URL - Make sure you're using the correct URL (https://eletro.design/mcp for production)
  2. Check your network - Ensure you have internet access and can reach the documentation site
  3. Restart your IDE - Some IDE's require a restart after adding MCP server configurations

Local Development

For local development, make sure the documentation server is running:

Terminal
cd docs
pnpm dev

Then update your MCP configuration to use the local URL:

.cursor/mcp.json
{
  "mcpServers": {
    "eletrods-local": {
      "type": "http",
      "url": "http://localhost:3000/mcp"
    }
  }
}

Next Steps

LLMs Integration

Learn about generating AI-ready content files using the Nuxt LLMs module.

Components

Explore all available EletroDS components.