Back to .md Directory

🤖 MCP Server for AI Tools

Documents how to start and connect an MCP server that exposes 11 AI-accessible tools and 9 read-only resources for a component library.

May 2, 2026
0 downloads
0 views
ai prompt mcp claude cursor
View source

What this file does

Documents how to start and connect an MCP server that exposes 11 AI-accessible tools and 9 read-only resources for a component library.

When to use it

  • You maintain a component library and want AI assistants to browse and generate components
  • You need to add an MCP endpoint to a Phoenix router
  • You want to configure Claude, Cursor, or Claude Desktop to interact with your library
  • You are setting up an HTTP-to-stdio proxy for editors that lack HTTP transport support

Assumes this stack

ElixirPhoenixMCPClaudeCursorVS Code

🤖 MCP Server for AI Tools

Model Context Protocol (MCP) integration for Mishka Chelekom - Connect your favorite AI tools directly to the component library.

Mishka Chelekom includes a built-in MCP server that enables AI assistants like Claude Code, Cursor, and Claude Desktop to browse components, generate code, and access documentation seamlessly.


🚀 Quick Start

Option 1: Standalone Server

Start the MCP server independently:

mix mishka.mcp.server

📍 Server runs at http://localhost:4003/mcp

Options:

OptionAliasDescriptionDefault
--port-pHTTP port to listen on4003

Example:

mix mishka.mcp.server --port 5000

Option 2: Integrate with Phoenix

Add the MCP endpoint directly to your Phoenix router:

mix mishka.mcp.setup

📍 Adds endpoint at /mcp on your Phoenix port (default http://localhost:4000/mcp)

Options:

OptionAliasDescriptionDefault
--path-pCustom MCP endpoint path/mcp
--dev-onlyOnly enable in developmenttrue
--yesSkip confirmation promptsfalse

Examples:

# Custom path
mix mishka.mcp.setup --path /api/mcp

# Enable in all environments
mix mishka.mcp.setup --dev-only=false

# Skip prompts
mix mishka.mcp.setup --yes

🔌 Connect Your AI Tools

Important: Use the correct URL based on your setup:

  • Standalone server: http://localhost:4003/mcp
  • Phoenix integration: http://localhost:4000/mcp (your Phoenix port)

Claude Code

# For standalone server
claude mcp add --transport http mishka-chelekom http://localhost:4003/mcp

# For Phoenix integration
claude mcp add --transport http mishka-chelekom http://localhost:4000/mcp

Cursor / VS Code

Create .mcp.json in your project root:

{
  "mcpServers": {
    "mishka-chelekom": {
      "type": "http",
      "url": "http://localhost:4003/mcp"
    }
  }
}

For Phoenix integration, change port to 4000 (or your Phoenix port).

Cursor / VS Code (via MCP Proxy)

If your editor doesn't support HTTP transport directly, use mcp_proxy_rust to bridge stdio and HTTP:

{
  "mcpServers": {
    "mishka-chelekom": {
      "command": "mcp-proxy",
      "args": ["--transport", "http", "http://localhost:4003/mcp"]
    }
  }
}

💡 Install the proxy with: cargo install mcp-proxy or download from releases

Claude Desktop

Add to your Claude Desktop configuration:

{
  "mcpServers": {
    "mishka-chelekom": {
      "type": "http",
      "url": "http://localhost:4003/mcp"
    }
  }
}

For Phoenix integration, change port to 4000 (or your Phoenix port).


🛠️ Available Tools (11)

Tools are actions the AI can perform on your behalf.

ToolDescription
generate_componentGenerate mix command for a single component
generate_componentsGenerate mix command for multiple components
get_component_infoGet component configuration options (variants, colors, sizes)
get_exampleGet HEEx code examples with usage patterns
get_js_hook_infoGet JavaScript hook documentation
get_mix_task_infoGet mix task documentation
search_componentsSearch components by name or functionality
uninstall_componentGenerate uninstall command
update_configUpdate project configuration settings
validate_configValidate configuration file for errors
get_docsFetch documentation from mishka.tools

📚 Available Resources (9)

Resources are read-only data the AI can access.

ResourceDescription
list_componentsList all available components with categories
list_colorsList color variants with CSS variables
list_variantsList style variants (default, outline, shadow, etc.)
list_sizesList size options (small, medium, large, etc.)
list_spacesList spacing options
list_scriptsList JavaScript hooks (Carousel, Clipboard, etc.)
list_dependenciesList component dependencies
list_css_variablesList all CSS custom properties
get_configGet current project configuration

💡 Example Usage

Once connected, you can ask your AI assistant things like:

  • "Show me all available button variants"
  • "Generate a modal component with primary color"
  • "What JavaScript hooks does the carousel need?"
  • "Search for form-related components"
  • "Show me an example of the alert component"

⚠️ Note for AI Tools

AI assistants may initially try incorrect resource URIs before discovering the correct ones. This is normal behavior - the AI will automatically recover by listing available resources and using the correct URIs.


📖 Learn More

What's inside

3 setup options, 4 AI tool connection configs, 11 tools table, 9 resources table, 5 example prompts, 1 proxy bridge section

Change this for your project

  • Replace mishka-chelekom in connection commands with your own MCP server name
  • Replace http://localhost:4003/mcp with your own server URL
  • Replace http://localhost:4000/mcp with your own Phoenix integration URL
  • Replace mishka.tools in the docs link with your own documentation domain

Where it goes

Keep it in your repository where the agent or team that needs it will read it.

Worth borrowing

  • Provide both standalone and Phoenix-integrated startup options so users can choose
  • Offer a proxy workaround for editors that do not support HTTP transport natively
  • List all tools and resources in tables so AI assistants can discover capabilities quickly

Related Documents