MCPServer
MCPpedia last refreshed this data
Developer Ops MCP is an MCP server that MCPServer. Its tool list has not been published yet over stdio, requires no API key, and scores 31/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"developer-ops-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server that integrates GitHub data into Claude, enabling natural language queries for development and operations workflows.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
deja-vu: local memory over the session histories of forty-three coding agents.
专门为 agent 打造的 agent 搜索工具,具备多语言搜索能力,覆盖中文/英文/学术/代码/购物/金融/新闻/百科。
Searchable football data provider documentation for AI coding agents. Like Context7 for football data.
Create a Scandit account, get trial license keys and set up the Scandit SDK in your app.
MCP Security Weekly
Get CVE alerts and security updates for Developer Ops MCP and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that integrates GitHub data into Claude, enabling natural language queries for development and operations workflows.
Instead of manually navigating GitHub, you can ask Claude directly:
"Show me the last 10 commits in this repository."
"What issues are currently open?"
"What files changed in this commit?"
"Give me an overview of this repository."
Claude selects the appropriate tool, calls the GitHub API, and returns the results in a readable format.
Claude / MCP Client
│ JSON-RPC over stdio
▼
Developer Ops MCP Server
│
├── index.ts — Tool registration & routing
├── schemas/ — Zod parameter validation
├── tools/github/ — Business logic per tool
├── clients/ — GitHub API client (axios)
└── utils/ — Error handling & logging
│
└── GitHub REST API
Why this layer separation?
Keeping API calls in clients/ and response shaping in tools/ makes it straightforward to add new data sources (deployment logs, error monitoring, database) without rewriting existing tools.
| Language | TypeScript |
| Runtime | Node.js |
| MCP SDK | @modelcontextprotocol/sdk |
| HTTP Client | axios |
| Validation | zod |
| Environment | dotenv |
| Tool | Description |
|---|---|
get_repository | Repository metadata — stars, forks, language, default branch |
get_recent_commits | Recent commit list with SHA, message, author, date |
get_issues | Open/closed issue list with labels and comments count |
get_pull_requests | PR list with branch info, state, and draft status |
get_commit_diff | Changed files and diff for a specific commit |
git clone https://github.com/ilminkwon/developer-ops-mcp.git
cd developer-ops-mcp
npm install
cp .env.example .env
Edit .env and add your GitHub Personal Access Token:
GITHUB_TOKEN=your_token_here
The token needs repo scope. Create one at GitHub → Settings → Developer settings → Personal access tokens.
npm run build
claude mcp add developer-ops \
-e GITHUB_TOKEN=your_token_here \
-- node /absolute/path/to/dist/index.js
Then open Claude Code from the project directory and start asking questions.