> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hellozelo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Access Zelo from Claude, Cursor, and other AI tools via the Model Context Protocol

## Overview

The Zelo MCP Server lets you connect any MCP-compatible AI tool to your Zelo feedback intelligence platform. Query customer insights, explore feedback themes, and surface issues — all without leaving your workflow.

## Available Tools

The MCP server exposes the following tools:

* **`get_insights`** — Search and filter customer feedback insights by priority, type, date range, source, and more. Returns insight summaries with volume, urgency, and revenue impact.
* **`get_insight_details`** — Drill into a specific insight to see individual customer quotes (snippets), source attribution, and detailed urgency scoring.
* **`get_available_filters`** — Retrieve the available filter options (themes, sources, feedback types) for your workspace.

## Use Cases

* **Product planning** — Ask your AI assistant what customers are requesting most, filtered by revenue impact or priority.
* **Bug triage** — Surface critical issues from support tickets and app reviews without leaving your IDE.
* **Sales enablement** — Pull real customer quotes and sentiment data into proposals and decks.
* **Sprint planning** — Query feedback trends from the last week to inform what to build next.
* **Competitive intelligence** — Find competitor mentions across all feedback channels.

## Installation

<Tabs>
  <Tab title="Claude Code">
    Run this command in your terminal:

    ```bash theme={null}
    claude mcp add --transport http Zelo https://hellozelo.com/mcp
    ```

    Verify the connection:

    ```bash theme={null}
    claude mcp list
    ```

    You should see `Zelo: https://hellozelo.com/mcp - Connected` in the output.
  </Tab>

  <Tab title="Claude Desktop / Claude.ai">
    Go to **Settings > MCP Servers** and add a new server with the URL:

    ```
    https://hellozelo.com/mcp
    ```

    Alternatively, add it to your Claude Desktop configuration file:

    ```json theme={null}
    {
      "mcpServers": {
        "Zelo": {
          "url": "https://hellozelo.com/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="Cursor">
    Add the following to your `.cursor/mcp.json` file:

    ```json theme={null}
    {
      "mcpServers": {
        "Zelo": {
          "url": "https://hellozelo.com/mcp"
        }
      }
    }
    ```

    Restart Cursor to pick up the new server.
  </Tab>

  <Tab title="VS Code">
    Add the following to your `.vscode/mcp.json` file:

    ```json theme={null}
    {
      "mcpServers": {
        "Zelo": {
          "url": "https://hellozelo.com/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="Windsurf">
    Add the following to your Windsurf MCP configuration file (`~/.codeium/windsurf/mcp_config.json`):

    ```json theme={null}
    {
      "mcpServers": {
        "Zelo": {
          "serverUrl": "https://hellozelo.com/mcp"
        }
      }
    }
    ```
  </Tab>
</Tabs>

## Best Practices

* **Be specific with date ranges** — When asking about recent feedback, specify a time window (e.g., "last 7 days") to get the most relevant results.
* **Filter by source** — Narrow results to specific channels. Use "sales calls" for Gong/Salesforce/Clari Copilot data, "support tickets" for Intercom/Zendesk, or "app reviews" for App Store/Play Store feedback.
* **Use priority filters** — Focus on critical and high-priority insights when triaging issues.

<Note>
  The MCP server respects your workspace permissions. You'll only see insights and feedback that your account has access to.
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Connection timeout or refused">
    Ensure your network allows outbound HTTPS connections to `hellozelo.com`. If you're behind a corporate proxy, configure your MCP client's proxy settings accordingly.
  </Accordion>

  <Accordion title="No tools appearing in the client">
    Some clients require a restart after adding a new MCP server. Close and reopen your editor or AI tool, then check again.
  </Accordion>

  <Accordion title="Empty results when querying insights">
    Make sure your Zelo workspace has connected integrations with synced data. Check your [Integrations settings](/integrations/overview) to verify connectors are active.
  </Accordion>

  <Accordion title="VS Code not detecting the MCP server">
    Ensure the configuration file is located at `.vscode/mcp.json` in your workspace root (not in your user settings). VS Code requires workspace-level MCP configuration.
  </Accordion>
</AccordionGroup>