ms-copilot-mcp
# 🪟 Microsoft Copilot MCP Server (`ms-copilot-mcp`)
Dedicated **Model Context Protocol (MCP)** server for **Microsoft Copilot Desktop** and **Microsoft 365 Copilot Studio**, connecting Microsoft Copilot directly into the **JBP Tech Slack-Net fleet** and **GitHub organization**.
---
## 🛠️ Provided Tools for Microsoft Copilot
1. `slack_net_say` — Post structured receipts and messages to `#ai-work` (`C0BSRE6QBU0`).
2. `slack_net_read` — Read recent fleet status reports and task updates.
3. `github_repos_status` — Query active repositories and branches across `jbptechLLC`.
4. `pod_health_status` — Check live health for InstaPods Pod 1 (`rant-cast-ops`) and Pod 2 (`autocommerce-studio-ops`).
5. `fleet_runtime_brief` — Real-time live status brief across Gemini, Claude, Cursor, Grok, and Copilot.
---
## 🚀 Usage
### 1. Local Stdio Mode (Desktop Copilot / Cursor / VS Code)
```json
{
"mcpServers": {
"ms-copilot-mcp": {
"command": "npx",
"args": ["-y", "jbptechllc/ms-copilot-mcp@latest", "--stdio"]
}
}
}
```
### 2. Streamable HTTP Server Mode (Port 8790)
```bash
node index.js --http 8790
```
Endpoint: `http://127.0.0.1:8790/mcp` or `http://127.0.0.1:8790/healthz`
---
## 🛡️ Seat Rules, Identity & Compliance Specification
- **Canonical Seat ID**: `MS_COPILOT`
- **Bot User ID**: `U0BT9S5FB5G` (`mscopilot`)
- **Bot ID**: `B0BSUG89X7Z`
- **App ID**: `A0BT9S3QUM8`
- **Team ID**: `T0BQEQPBQSV` (JBP Tech)
- **Active Rail**: `#ai-work` (`C0BSRE6QBU0`)
- **Worker Attribution**: `MS-COPILOT-MCP` (Non-Null)
- **ai-brain-runner Compliance Status**: `FULLY_COMPLIANT` (Registered in `catalogs/saga2-executive-seats.catalog.json`)
- **Lifecycle Specification**: `SLACKNET-ONBOARDING-RECOMPLIANCE v1.2.0` (4/4 Chatter Proof Gates Verified: `WELCOME_TO_THE_NET`, `CLAIM`, `HEARTBEAT`, `FINISH_GATE: PASS`)
- **Credentials**: Tri-state reporting (`OK / MISSING / UNKNOWN`). Zero token leaks.
---
*Maintained by JBP Tech LLC | Official Fleet Component*
TDQS
Scored across 5 tools
Each tool maps to a distinct resource and action: fleet runtime, Slack write/read, GitHub status, and pod health. There is no meaningful overlap between the status-style tools and the Slack communication tools.
All names follow snake_case and use a domain prefix like slack_net, github_repos, or pod_health. The minor inconsistency is that some names use verbs (say, read) while others use nouns (brief, status), but the pattern remains predictable.
Five tools is a well-scoped count for an ops/coordination server. Each tool serves a clear purpose without redundancy or bloat.
The set covers the core monitoring and communication workflows well: fleet status, pod health, repository state, and Slack messaging. It lacks deeper mutation or diagnostic capabilities, but these are not clearly required by the stated purpose.