erm-github-mcp
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., "@erm-github-mcp Ping the server and show its server info"
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.
erm-github-mcp
A barebones Model Context Protocol (MCP) server written in TypeScript. Designed to be built from source, containerized with Docker, and deployed to IBM Code Engine.
Table of Contents
Related MCP server: My Awesome MCP
Overview
This server supports two transports:
Transport | When it's used | How to activate |
stdio | Local development / Bob desktop | Default (no env var needed) |
HTTP Streamable | Docker / Code Engine |
|
The HTTP transport exposes a /health endpoint at GET /health for liveness probes.
Project Structure
.
├── src/
│ └── index.ts # Server entry point — add tools here
├── build/ # Compiled output (git-ignored)
├── .github/
│ └── workflows/
│ └── build-push.yml # CI: typecheck → build → push to GHCR
├── Dockerfile # Multi-stage build (builder + runtime)
├── docker-compose.yml # Local container testing
├── tsconfig.json
└── package.jsonTools
Tool | Description |
| Health-check — returns |
| Returns server name, version, transport, Node version, and uptime |
Local Development
Prerequisites
Node.js 20+
npm 10+
Install and build
npm install
npm run buildRun in stdio mode (for use with Bob desktop)
node build/index.jsRun in HTTP mode locally
MCP_TRANSPORT=http PORT=3000 node build/index.jsTest the health endpoint:
curl http://localhost:3000/healthRunning with Docker
Build the image
docker build -t erm-github-mcp .Run the container
docker run -p 3000:3000 erm-github-mcpUsing Docker Compose
docker compose up --buildGitHub Actions CI/CD
The workflow at .github/workflows/build-push.yml runs on every push to main and on version tags (v*):
TypeScript build —
npm ci+tsc(fails fast on type errors)Docker build & push — multi-platform image (
linux/amd64,linux/arm64) pushed to the GitHub Container Registry (GHCR)
The image is published as:
ghcr.io/<your-github-username>/erm-github-mcp:<tag>No secrets need to be configured — the workflow uses the built-in GITHUB_TOKEN.
Making the package public
After the first push, go to GitHub → Packages → erm-github-mcp → Package settings and set visibility to Public so Code Engine can pull it without credentials.
Deploying to IBM Code Engine
Prerequisites
IBM Cloud CLI with the Code Engine plugin:
ibmcloud plugin install code-engineAn IBM Cloud account and a Code Engine project
Steps
1 — Target your project
ibmcloud ce project select --name <your-project-name>2 — Deploy the application
Replace <tag> with the image tag you want to deploy (e.g. main or v0.1.0):
ibmcloud ce application create \
--name erm-github-mcp \
--image ghcr.io/<your-github-username>/erm-github-mcp:<tag> \
--port 3000 \
--min-scale 0 \
--max-scale 5 \
--env MCP_TRANSPORT=http \
--env PORT=30003 — Get the public URL
ibmcloud ce application get --name erm-github-mcp --output url4 — Update after a new image push
ibmcloud ce application update \
--name erm-github-mcp \
--image ghcr.io/<your-github-username>/erm-github-mcp:<new-tag>Environment variables
Variable | Default | Description |
|
| Set to |
|
| HTTP port the server listens on |
Connecting to Bob (IBM Bob Desktop)
HTTP (remote — after deploying to Code Engine)
Add the following to your Bob mcp.json:
{
"mcpServers": {
"erm-github-mcp": {
"url": "https://<your-code-engine-url>"
}
}
}stdio (local — for development)
{
"mcpServers": {
"erm-github-mcp": {
"command": "node",
"args": ["/absolute/path/to/erm-github-mcp/build/index.js"]
}
}
}Extending the Server
Add new tools in src/index.ts using server.tool():
server.tool(
"my_tool",
"Description shown to the AI",
{
input_field: z.string().describe("What this field does"),
},
async ({ input_field }) => ({
content: [{ type: "text", text: `Result: ${input_field}` }],
})
);Then rebuild:
npm run buildLicense
Available Tools
2 toolsget_server_infoA
Returns metadata about this running MCP server instance.
Inputs: no named parameters.
pingA
Health-check tool. Returns 'pong' and echoes the optional message back.
Inputs: message.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools serve clearly distinct purposes: ping is a health check, while get_server_info provides instance metadata. There is zero overlap between them.
Both tools follow a consistent verb_noun naming pattern (ping, get_server_info) with snake_case, matching the expected convention.
With only two generic tools and a server name indicating GitHub integration, the count is severely inadequate. The tools are trivial and unrelated to the apparent domain, representing an extreme mismatch.
The server name implies GitHub functionality, but the tool surface offers only health check and server info. No GitHub operations exist, leaving obvious and critical gaps.
Maintenance
Related MCP Connectors
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
An MCP server for Arcjet - the runtime security platform that ships with your AI code.
The official MCP Server from Mia-Platform to interact with Mia-Platform Console
Related MCP Servers
- FlicenseBqualityNot gradedmaintenanceA minimal reference implementation of an MCP server that responds with "Hello, World" via Streamable HTTP. Serves as a baseline for integration testing and MCP client development with production-ready features including health checks, metrics, and containerized deployment.351,670 npm-
- -licenseNot gradedqualityNot gradedmaintenanceA basic MCP server built with FastMCP framework that provides example tools including message echoing and server information retrieval. Supports both stdio and HTTP transports with Docker deployment capabilities.-
- -licenseNot gradedqualityNot gradedmaintenanceA basic MCP server built with FastMCP framework that provides example tools for echoing messages and retrieving server information. Supports both stdio and HTTP transports with Docker deployment capabilities.-
- -licenseNot gradedqualityNot gradedmaintenanceA basic MCP server built with FastMCP framework that provides simple utility tools including message echoing and server information retrieval. Supports both stdio and HTTP transports with Docker deployment capabilities.-