mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub token for accessing GitHub API | |
| TEAMS_CLIENT_ID | No | Client ID for Microsoft Graph | |
| TEAMS_TENANT_ID | No | Tenant ID for Microsoft Graph | |
| TEAMS_WEBHOOK_URL | No | Webhook URL for Microsoft Teams | |
| TEAMS_CLIENT_SECRET | No | Client secret for Microsoft Graph |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | Returns exactly the text you send |
| get_timeA | Returns the current server time in ISO format |
| github_statusA | Checks whether GitHub token is loaded and authentication works |
| github_authenticated_userA | Returns the currently authenticated GitHub account |
| github_list_reposC | Lists repositories for the authenticated GitHub user |
| github_create_issueC | Creates a GitHub issue in a repository |
| github_requestB | Sends a raw authenticated request to GitHub REST API. Use with caution. |
| teams_graph_statusA | Checks whether Microsoft Graph credentials are configured and working |
| teams_send_dmB | Sends a direct message (DM) to a specific Teams user by their email address |
| teams_send_messageB | Sends a plain text message to a Microsoft Teams channel via incoming webhook |
| teams_send_cardC | Sends a rich Adaptive Card message to a Teams channel (title + body + optional link) |
| github_list_issuesC | Lists open issues for a given repository |
| github_get_fileB | Reads a file from a GitHub repository and returns its content as text |
| github_create_pull_requestC | Opens a pull request on a GitHub repository |
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 14 tools
Each tool targets a distinct function: utilities (echo, get_time), GitHub operations (create, list, read, status), and Teams messaging (send, status). The raw github_request is a fallback, but its distinct purpose is clear.
Tools use three different prefixes (none, github_, teams_), and within each, naming is mixed: verb_noun (create_issue, send_message) vs. noun-like (authenticated_user, status). The pattern is not fully consistent.
14 tools cover three distinct domains (utilities, GitHub, Teams) without being overwhelming. Each tool serves a clear purpose, and the count feels well-scoped for a multi-service integration.
For GitHub, common operations are present but missing updates/deletes and PR merging. For Teams, only sending is available (no reading, listing). The utilities are minimal. Notable gaps exist, but core workflows are covered.