Provides tools for interacting with GitHub's API, enabling operations such as listing repositories, creating issues, managing pull requests, and accessing user or repository data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-server list my GitHub repositories"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
#MCP Server
Production-ready TypeScript Model Context Protocol (MCP) server exposing utility, GitHub, and Microsoft Teams tools over stdio.
Clean MCP server baseline for internal automation and integrations
GitHub and Microsoft Teams operational tooling in a single service
Strict TypeScript setup and minimal runtime surface
Related MCP server: Basic MCP Server
echo
get_time
github_status
github_authenticated_user
github_list_repos
github_create_issue
github_list_issues
github_get_file
github_create_pull_request
github_request
teams_send_message (webhook)
teams_send_card (adaptive card webhook)
teams_graph_status (Graph API)
teams_send_dm (Graph API)
Node.js 20+
npm 10+
cd mcp-server
npm install
copy .env.example .envPopulate .env before running.
GITHUB_TOKEN
TEAMS_WEBHOOK_URL
TEAMS_TENANT_ID
TEAMS_CLIENT_ID
TEAMS_CLIENT_SECRET
npm run dev — development mode with tsx
npm run build — compile to dist/
npm run start — run compiled server
npm run clean — remove dist/
npm run inspect — open MCP inspector
Development:
npm run devBuild + run:
npm run build
npm run startMCP stdio command:
node dist/index.jsDo not commit .env or secrets
Use least-privilege credentials for GitHub and Microsoft Graph
Review SECURITY.md before production use
See CONTRIBUTING.md and CODE_OF_CONDUCT.md.
Distributed under the MIT License. See LICENSE.
Returns exactly the text you send
Inputs: text (required).
Returns the current server time in ISO format
Inputs: no named parameters.
Returns the currently authenticated GitHub account
Inputs: no named parameters.
Creates a GitHub issue in a repository
Inputs: repo (required), owner (required), title (required), body.
Opens a pull request on a GitHub repository
Inputs: base (required), head (required), repo (required), owner (required), +2 more.
Reads a file from a GitHub repository and returns its content as text
Inputs: path (required), repo (required), owner (required), ref.
Lists open issues for a given repository
Inputs: repo (required), owner (required), state, per_page.
Lists repositories for the authenticated GitHub user
Inputs: page, per_page, visibility.
Sends a raw authenticated request to GitHub REST API. Use with caution.
Inputs: path (required), method (required), paramsJson.
Checks whether GitHub token is loaded and authentication works
Inputs: no named parameters.
Checks whether Microsoft Graph credentials are configured and working
Inputs: no named parameters.
Sends a rich Adaptive Card message to a Teams channel (title + body + optional link)
Inputs: body (required), title (required), link_url, link_label.
Sends a direct message (DM) to a specific Teams user by their email address
Inputs: message (required), recipient_email (required).
Sends a plain text message to a Microsoft Teams channel via incoming webhook
Inputs: text (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
A TypeScript MCP server for Home Assistant, enabling programmatic management of entities, automati…
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
A simple Typescript MCP server built using the official MCP Typescript SDK and smithery/cli. This…
