EnineSites

EnineSites, direct to your AI.

Connect EnineSites to Claude, Cursor, or any MCP-compatible tool and access your CMS data directly in your AI workflow — no tab switching, no exports.

Get Connected →

What is MCP?

Model Context Protocol (MCP) is an open standard that lets AI tools connect to external data sources. Think of it as a universal plug — once an AI tool supports MCP it can connect to any MCP server with just a URL, and your AI can access EnineSites data natively without switching tabs.

Before you start

You'll need an EnineSites account. You will authenticate your AI tool using your existing EnineSites credentials via a secure OAuth2 flow.

How to Connect

1. Connect via Claude.ai (Web)

The simplest setup for teams and individual users.

For Individual Users:

  1. In Claude, go to Settings → Connectors.
  2. Click Add → Custom → Web.
  3. Name: EnineSites
  4. Remote MCP Server URL: https://mcp.eninesites.dev/sse
  5. Click Connect and follow the OAuth flow.

2. Connect via Claude Desktop

Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "EnineSites": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.eninesites.dev/sse"
      ]
    }
  }
}

Config file location (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json

3. Connect via Claude Code (CLI)

Add EnineSites to your current project:

claude mcp add eninesites --transport http https://mcp.eninesites.dev/sse

4. Other MCP Clients (Cursor, Windsurf, etc.)

Point any MCP-compatible tool to:

https://mcp.eninesites.dev/sse