Skip to content

MCP Connections

Overview

Model Context Protocol (MCP) connections enable WorkBuddy to interact with external services through natural language. This documentation provides isolated, service-specific guidance for each MCP connection, allowing teams across the organization to selectively adopt and configure the connections they need.

Available Connections

Connection Type Status Use Case
Odoo ERP Local Command (Python) ✅ Ready ERP operations, sales orders, inventory management
GitHub Remote MCP Server 🔧 Configuration Required Repository management, PR reviews, issue tracking
Notion Remote MCP Server 🔧 Configuration Required Knowledge base, documentation, project management
Cloudflare Local Command (npx) 🔧 Configuration Required DNS management, security configuration, analytics
Microsoft Teams Remote MCP Server 🔧 Configuration Required Team collaboration, meeting management
OneDrive Remote MCP Server 🔧 Configuration Required File storage and sharing
Tencent Docs Remote MCP Server 🔧 Configuration Required Collaborative document editing
WeCom Remote MCP Server 🔧 Configuration Required Enterprise messaging and workflows

Quick Start

1. Check Prerequisites

  • WorkBuddy Desktop with MCP support enabled
  • Appropriate service accounts and API keys
  • Network access to required endpoints

2. Choose Connection Type

Type A: Remote MCP Servers

Services like GitHub, Notion provide hosted MCP endpoints: - Configuration: Update mcp.json with service URL - Credentials: Typically use OAuth or API tokens via environment variables - Setup: Minimal installation required

Type B: Local Command MCP Servers

Services like Odoo, Cloudflare run locally via npm or Python: - Installation: Package installation required (pip install or npm install) - Configuration: Environment variables for credentials - Setup: Requires installing and configuring the MCP server package

3. Follow Connection-Specific Guide

Each connection has its own documentation with: - Step-by-step installation/configuration - Required credentials and permissions - Common operations and examples - Troubleshooting guidance

Connection Status Legend

  • ✅ Ready: Fully documented and tested
  • 🔧 Configuration Required: Documentation available, needs service-specific configuration
  • 🚧 In Progress: Documentation being developed
  • 📋 Planned: Connection planned for future implementation

Canonical Structure

All MCP connections follow our canonical MCP structures for consistency:

  1. Package/Endpoint Registration – Standardized installation or URL configuration
  2. Credential Management – Environment variables with SERVICE_* naming
  3. Configuration Templates – Template files with placeholder values
  4. Testing Protocol – Verification steps for each connection
  5. Documentation – Complete usage guide and troubleshooting

Organization Adoption

Selective Implementation

Teams can choose which connections to implement based on their needs: - Development Teams: GitHub, Notion, Cloudflare - Operations Teams: Odoo, Microsoft Teams - Documentation Teams: Tencent Docs, OneDrive - HR/Admin Teams: WeCom, Notion

Security Considerations

  • Each connection isolates its credentials and permissions
  • Environment variables prevent credential leakage
  • Service-specific API tokens with minimal required permissions
  • Regular credential rotation recommended

Maintenance

Updates

  • Check connection documentation for version-specific requirements
  • Review canonical structures for breaking changes
  • Test configuration after service updates

Support

  • Connection-specific troubleshooting in each guide
  • Common issues documented in canonical structures
  • Organization support channels for MCP-related questions

Contributing New Connections

To add a new MCP connection to this documentation:

  1. Review Existing Patterns – Follow the canonical structure
  2. Create Connection Directory – docs/mcp-connections/<service-name>/
  3. Write Comprehensive Guide – Include installation, configuration, usage, troubleshooting
  4. Update This Index – Add to the table with status and description
  5. Update Navigation – Add to mkdocs.yml under "MCP Connections"
  6. Test Documentation – Verify MkDocs builds without errors

Last Updated: 2026‑05‑19
Maintainer: Platform Team
Purpose: Isolated service documentation for selective organizational adoption