concierge-mcp

Local MCP server for Concierge — the Discord-native customer support platform.

Plug your AI agent (Claude Desktop, Cursor, Cline, or any MCP-compatible client) into your Concierge support server and operate the entire support stack via natural language. 200+ tools cover ticket lifecycle, AI configuration, knowledge base, panels, automations, analytics, billing, Discord communication, and more.

What you can do

"Set up Concierge for my SaaS — deploy the panel in #support, give @Mod and @Admin agent access, and configure SLA to 30 minutes for high-priority tickets."

"Show me a CSAT report for the last 30 days, then suggest a reply for ticket #142."

"Bulk-close every ticket older than 7 days that has no agent response, and DM the customer a transcript."

"Snooze ticket #88 until tomorrow 9am ET, and flag the customer as VIP."

Install

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "concierge": {
      "command": "npx",
      "args": ["-y", "concierge-mcp"],
      "env": {
        "CONCIERGE_GUILD_ID": "YOUR_DISCORD_GUILD_ID",
        "CONCIERGE_MCP_KEY": "YOUR_MCP_API_KEY"
      }
    }
  }
}

Restart Claude Desktop. You should see "concierge" in the MCP servers list, with all 200+ tools available.

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "concierge": {
      "command": "npx",
      "args": ["-y", "concierge-mcp"],
      "env": {
        "CONCIERGE_GUILD_ID": "YOUR_DISCORD_GUILD_ID",
        "CONCIERGE_MCP_KEY": "YOUR_MCP_API_KEY"
      }
    }
  }
}

Cline / other MCP clients

Use the same command/args/env shape — every MCP client supports stdio servers.

Getting your credentials

1. Open your Concierge dashboard at conciergetickets.net/dashboard
2. Open any panel → Advanced → MCP Settings
3. Toggle MCP Enabled ON — this generates an API key
4. Copy the API key (set as CONCIERGE_MCP_KEY)
5. Your Guild ID is the Discord server ID — found in the URL or via right-click → Copy Server ID (developer mode required)

How it works

This package is a thin stdio proxy. When your MCP client launches it, it:

1. Connects to the Concierge MCP server at https://api.conciergetickets.net/api/v1/guilds/{GUILD_ID}/mcp
2. Authenticates with your API key
3. Fetches the live tool catalog (so new tools released by Concierge appear automatically without re-installing)
4. Forwards every tool call to the remote server

The local binary is small and stateless. Your guild's data stays on Concierge's infrastructure.

Tool categories

• Tickets — full lifecycle (claim, snooze, reopen, complete, transfer, lock, merge, split, etc.) plus bulk operations
• AI — summarize tickets, analyze sentiment, suggest replies, regenerate responses, translate
• Knowledge base — full CRUD + search + GitBook import
• Customers — profiles, notes, VIP toggle, blacklist with optional expiry
• Panels — create/deploy/redeploy with full embed customization
• Configuration — every setting on TicketPanel and Guild via update_panel_config / update_guild_config
• Discord — send messages, DMs, react, post announcements, look up channels/roles/members
• Webhooks — full CRUD + test, redeliver, stats
• Analytics — overview, peak hours, agent leaderboard, CSV export
• CRM — test, sync, pull from Salesforce/HubSpot/Zendesk/Freshdesk
• Cron triggers — run SLA scan, auto-close, escalation check on demand
• Team — invite, remove, set workload/schedule/status/skills

Run npx -y concierge-mcp and call tools/list to see the full live catalog.

Discovery endpoints (for non-MCP integrations)

• GET https://api.conciergetickets.net/api/v1/public/openapi.json — full OpenAPI 3.1 spec for the REST API
• GET https://api.conciergetickets.net/api/v1/public/schema.json — parsed Prisma schema (every model, field, enum)

Links

• Concierge: https://conciergetickets.net
• Documentation: https://conciergetickets.net/docs
• Model Context Protocol: https://modelcontextprotocol.io

License

MIT