This MCP server connects to a Discord bot and provides tools to retrieve messages from Discord channels, sanitize them for privacy, and store them in a vector database (ChromaDB) for semantic search and analysis. It offers a Python-based workflow including a message retriever, a privacy processor for PII detection and redaction, and a processor that converts messages into embeddings for vector storage. The server also includes a CLI for end-to-end usage: fetch messages, prepare them for the vector database, and perform semantic searches. Users can opt out of processing via the opt-out registry, and data minimization is enforced by default.

Prerequisites:

• Python 3.8+ installed on your system
• Virtual environment support (venv) or your preferred environment manager
• Access to a Discord bot with appropriate permissions and a Discord bot token
• Optional: a running ChromaDB instance or accessible ChromaDB endpoint

Steps:

1. Clone the repository: git clone https://github.com/yourusername/discord_vector_db.git cd discord_vector_db

2. Create and activate a virtual environment: python -m venv venv

   macOS/Linux

   source venv/bin/activate

   Windows

   venv\Scripts\activate

3. Install dependencies: pip install -r requirements.txt

4. Configure environment variables (example): export DISCORD_BOT_TOKEN="your_discord_bot_token" export CHROMA_DB_DIR="./chromadb" export CHROMA_DB_URI="http://localhost:7700" export PII_REDACTION_ENABLED="true" export OPTOUT_REGISTRY_URL="https://example.com/opt-out-registry"

5. Run the server: python -m discord_vector_db

6. Optional: verify connectivity to ChromaDB and Discord by running basic CLI commands provided by the project (see CLI in README).

Tips:

• Ensure the Discord bot has access to the channels you intend to scan.
• If PII redaction is enabled, test with sample messages to validate redaction rules.
• Use the opt-out registry to respect user preferences; ensure the registry URL is reachable.
• Monitor logs (LOG_LEVEL) to troubleshoot connectivity or processing errors.
• For large volumes, consider enabling checkpointing and circuit-breaker settings if available in the config.

Common issues:

• Invalid or missing DISCORD_BOT_TOKEN: check token and bot permissions.
• ChromaDB connection failures: verify CHROMA_DB_URI and that the service is running.
• File permission errors writing to CHROMA_DB_DIR: ensure write access to the directory.