czlabs-discord-mcp

Local MCP (Model Context Protocol) server that acts as a bridge to a Discord backend on Heroku.
Allows MCP-compatible editors/LLMs (e.g. Cursor) to use CZLabs Discord private data analysis without exposing private keys.

🚀 Installation

npm i -g czlabs-discord-mcp

⚙️ Cursor Configuration

Add to your configuration:

{
  "mcpServers": {
    "discord-mcp": {
      "command": "discord-mcp",
      "args": [],
      "env": {
        "DISCORD_API_URL": "https://<your-discord-app>.herokuapp.com",
        "DISCORD_MCP_AUTH_TOKEN": "<rotatable-discord-token>"
      }
    }
  }
}

• DISCORD_API_URL: your private Discord endpoint on Heroku.
• DISCORD_MCP_AUTH_TOKEN: rotatable token to validate access to private data.

▶️ Usage

1. Restart Cursor.
2. Verify that the ping tool appears.
3. Execute ping → should respond pong.
4. Execute Discord tools like intelligent_search, server_info, etc.

🔐 Security

• Your private keys (MongoDB, OpenAI) live only on Heroku.
• The local MCP never requires private keys.
• Use rotatable tokens to control access to sensitive data.
• INTERNAL CZLabs USE ONLY - contains private Discord data.

❓ FAQ

Do I need Heroku?
Yes, to expose your Discord API and keep private keys secure. The MCP is just the local bridge.

Does it work outside Cursor?
Yes, with any MCP client via stdio (other editors or apps that support MCP).

Why is there a ping tool?
To confirm that the MCP is working before using the Discord tools.

What data can it access?
Only CZLabs Discord data: users, channels, projects, activity analysis.

🛠️ Troubleshooting

• "No tools or prompts": check that there are no stdout logs and that the token is configured.
• 401 errors on Heroku: check that DISCORD_MCP_AUTH_TOKEN is in your Cursor config.
• Rate limit exceeded: maximum 50 queries/day for the entire organization.

🔗 Links

• MCP Documentation
• Cursor MCP Setup

Developed by CzLabs 🚀
⚠️ PRIVATE DATA - Internal authorized use only