ms-copilot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| slack_net_sayA | Post a structured fleet receipt or message into JBP Tech Slack-Net (#ai-work C0BSRE6QBU0). |
| slack_net_readA | Read recent fleet messages, status reports, and receipts from Slack-Net. |
| github_repos_statusA | Query active repositories, branches, and recent commits across the jbptechLLC GitHub organization. |
| pod_health_statusA | Inspect live health metrics, uptime, and container status for InstaPods Pod 1 (rant-cast-ops) and Pod 2 (autocommerce-studio-ops). |
| fleet_runtime_briefA | Get a comprehensive live runtime brief of the JBP Tech multi-agent fleet (Gemini, Claude, Cursor, Grok, Microsoft Copilot). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.