Overview

The Ticket House support site includes an MCP server that exposes its documentation articles as resources. Once connected, your AI agent can look up support articles on demand — it calls resources/list to see what’s available, then resources/read to get the content.

The easiest way to connect is via URL — no cloning or local setup required.

The MCP server is hosted at:

https://ticket-house-support.anvil.el-gato-labs.com/mcp

Claude Code

Run this in any project directory:

claude mcp add --transport http ticket-house-support https://ticket-house-support.anvil.el-gato-labs.com/mcp

Or add it to .claude/settings.json:

{
  "mcpServers": {
    "ticket-house-support": {
      "type": "url",
      "url": "https://ticket-house-support.anvil.el-gato-labs.com/mcp"
    }
  }
}

Gemini CLI

Add to .gemini/settings.json:

{
  "mcpServers": {
    "ticket-house-support": {
      "url": "https://ticket-house-support.anvil.el-gato-labs.com/mcp"
    }
  }
}

Other MCP Clients

Any MCP client that supports Streamable HTTP transport can connect using the URL above.

Connect via stdio (Local Development)

If you’re working on the support site itself, you can run the MCP server locally over stdio.

Prerequisites

  • Node.js 22+ installed
  • The support site repository cloned locally

Install

From the repository root:

cd mcp-server
npm install

Claude Code

claude mcp add ticket-house-support -- npx tsx mcp-server/src/index.ts .

Or add to .claude/settings.json:

{
  "mcpServers": {
    "ticket-house-support": {
      "command": "npx",
      "args": ["tsx", "mcp-server/src/index.ts", "."]
    }
  }
}

Gemini CLI

Add to .gemini/settings.json:

{
  "mcpServers": {
    "ticket-house-support": {
      "command": "npx",
      "args": ["tsx", "mcp-server/src/index.ts", "."]
    }
  }
}

Other Clients

The stdio command is:

npx tsx mcp-server/src/index.ts <path-to-site-root>

The <path-to-site-root> argument defaults to .. relative to the mcp-server/ directory if omitted.

Verify

Start your agent in the project. You should see “ticket-house-support” listed as a connected MCP server. Ask the agent to look up a support article to confirm it can read the resources.

What Gets Exposed

The MCP server scans the site for pages with Jekyll front matter and exposes each one as a resource. Each resource has:

  • URI — support:// followed by the page path (e.g. support://getting-started/project-configuration)
  • Name — the page title from front matter
  • Description — the page summary from front matter
  • Content — the article text with HTML tags stripped, returned as plain text

Hub pages (like category index pages) are included as well, providing navigation context.

Next Steps

The MCP server gives your agent access to documentation on demand. To go further, you can install a Claude Code skill that gives Claude persistent knowledge about Ticket House workflows — worktrees, hooks, configuration, and best practices — loaded automatically at the start of every conversation.

See Claude Code Skill for Ticket House for the ready-to-use skill file.