Allows interaction with GitHub repositories, including searching issues, retrieving repository statistics, and creating pull requests.
Enables querying events, creating events, and finding free time slots on Google Calendar.
Provides database operations for PostgreSQL, such as executing queries, listing tables, and describing table schemas.
Facilitates sending messages, listing channels, and retrieving thread conversations on Slack.
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 OpsBridge show me today's calendar events"
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.
Production MCP (Model Context Protocol) server exposing 30 DevOps tools for AI agents with a user approval system that prevents unauthorized write/destructive operations.
Exposes 29 tools + 1 approve_action tool across 4 services, guarded by a risk-based permission gate:
Service | Tools | Read (Auto) | Write (Gated) | Destructive (Double Approval) |
GitHub | 7 | All 7 | — | — |
Calendar | 8 | 4 ( | 3 ( | 1 ( |
Database | 9 | 3 ( | 2 auto + 1 gated ( | 3 ( |
Slack | 5 | 3 ( | 2 ( | — |
Related MCP server: mcp-github-server
The permission gate intercepts medium+ risk tool calls and returns pending_approval instead of executing. The agent presents a structured request to the user, who confirms via the approve_action tool.
Low risk → Auto-execute (reads)
Medium/High → Single approval required
Critical → Double approval required (two separate confirms)
Timeout → Stale approvals auto-expire after 5 minutes
┌──────────────────────────────────────────────────┐
│ CLIENTS │
│ Claude Desktop (stdio) │ Custom Client (HTTP) │
└────────────┬─────────────────────┬───────────────┘
│ │
▼ ▼
┌──────────────────────────────────────────────────┐
│ MCP SERVER │
│ ┌────────────────────────────────────────────┐ │
│ │ Transport: stdio | Streamable HTTP │ │
│ │ Rate Limiter: 100 req/min user, 1000/hr IP│ │
│ │ Permission Gate: Risk → Pending/Execute │ │
│ │ Validation: Zod schemas on all inputs │ │
│ └────────────────────────────────────────────┘ │
└────────────┬─────────────────────┬───────────────┘
│ │
▼ ▼
┌──────────────────────────────────────────────────┐
│ EXTERNAL APIs │
│ GitHub │ Google Calendar │ PostgreSQL │ Slack │
└──────────────────────────────────────────────────┘npm install
npm run dev # stdio mode (default)
TRANSPORT=http PORT=3099 npm run dev # HTTP modeAdd to claude_desktop_config.json:
{
"mcpServers": {
"opsbridge": {
"command": "npx",
"args": ["tsx", "src/cli.ts"],
"env": {
"GITHUB_TOKEN": "ghp_...",
"DATABASE_URL": "postgresql://...",
"SLACK_TOKEN": "xoxb-...",
"CALENDAR_TOKEN": "ya29..."
}
}
}
}cp .env.example .env
# Edit .env with your tokens
docker compose up -dVariable | Required | Description |
| No* | GitHub token (*required for private repos; public repos work without) |
| No* | PostgreSQL connection string (*required for DB tools) |
| No* | Slack bot token ( |
| No* | Google Calendar OAuth token (*required for Calendar tools) |
| No |
|
| No | HTTP port (default: 3002) |
Permission gate: Risk-based approval for write/destructive operations; critical ops require double approval
Read-only database: PostgreSQL session set to READ ONLY + write keyword blocklist
Rate limiting: LRU cache, 100 requests/minute per user, 1000/hour per IP
Scoped tokens: Each service requires its own token
Input validation: All tool inputs validated with Zod schemas
No secrets in code: All tokens loaded from environment variables
5-minute approval timeout: Stale pending approvals auto-expire
npm run build # Compile TypeScript
npm run dev # Start dev server (stdio)
npm test # Run Vitest (71 tests)
npm run lint # Type check
npm run format # Prettier formatTypeScript 5.5+
@modelcontextprotocol/sdk v1.29 (MCP protocol)
Zod (input validation)
@octokit/rest (GitHub API)
pg (PostgreSQL)
lru-cache (rate limiting + approval store)
Vitest (testing)
MIT
Confirm or deny a pending action that requires user approval. Use this to respond to pending_approval or pending_approval_2 responses.
Inputs: decision (required), approval_id (required), reason.
Add an attendee to an existing event (requires approval)
Inputs: email (required), event_id (required), calendar_id.
Create a calendar event with optional attendees (requires approval)
Inputs: summary (required), end_time (required), start_time (required), attendees, +2 more.
Delete a calendar event (double approval required — irreversible)
Inputs: event_id (required), calendar_id.
Find mutually available time slots across calendars
Inputs: time_max (required), time_min (required), calendar_ids, duration_minutes.
Get detailed information about a single event including attendees and description
Inputs: event_id (required), calendar_id.
List all calendars accessible by the authenticated user
Inputs: no named parameters.
List events in a date range from Google Calendar
Inputs: time_max (required), time_min (required), calendar_id, max_results.
Update an existing calendar event (requires approval)
Inputs: event_id (required), summary, end_time, start_time, +2 more.
Delete rows from a table matching a WHERE clause (requires approval)
Inputs: table (required), where (required), params (required).
Show columns and types for a table
Inputs: table (required), schema.
Drop a table — permanently removes table and data (double approval required)
Inputs: table (required), if_exists.
Execute a read-only SQL query against PostgreSQL
Inputs: query (required), params.
Insert a new row into a table (auto-approved, logged)
Inputs: data (required), table (required).
List all tables in a database schema
Inputs: schema.
Execute a schema migration (ALTER/CREATE/DROP) — structural change (double approval required)
Inputs: query (required).
Truncate a table — removes all rows (double approval required)
Inputs: table (required), cascade.
Update rows in a table matching a WHERE clause (auto-approved, logged)
Inputs: data (required), table (required), where (required), params (required).
Get commit history for a branch
Inputs: repo (required), limit, branch.
Get contents of a file or directory from a repository
Inputs: path (required), repo (required), branch.
Get pull requests in a repository with diff statistics
Inputs: repo (required), limit, state.
Get repository statistics: stars, forks, open issues, recent commits
Inputs: repo (required).
List all branches in a repository
Inputs: repo (required), limit.
List repositories for the authenticated user with metadata
Inputs: sort, type, limit.
Search issues in a GitHub repository by query, state, and label
Inputs: repo (required), query (required), limit, state.
Get recent messages from a Slack channel
Inputs: channel (required), limit, cursor.
Retrieve messages in a thread
Inputs: ts (required), channel (required), limit.
List accessible Slack channels
Inputs: limit, cursor.
Send a message to a Slack channel (requires approval)
Inputs: text (required), channel (required), thread_ts.
Send a reply in a Slack thread (requires approval)
Inputs: text (required), channel (required), thread_ts (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 30 tools
Every tool is clearly namespaced by service (github_, calendar_, db_, slack_) and performs a distinct action. No two tools have overlapping purposes; even similar actions like calendar_query_events and calendar_get_event_details are clearly differentiated.
All tool names follow a consistent snake_case pattern of domain_verb_noun (e.g., github_search_issues, db_execute_query, slack_send_message). The standalone approve_action still fits the verb_noun convention. No naming style mixing.
At 30 tools, the server exceeds the 25+ threshold for 'too many'. While the tools are grouped by service, the overall count is heavy for a single MCP server and could overwhelm agents. Splitting into separate domain servers would be more appropriate.
Calendar, database, and Slack domains have full lifecycle coverage (CRUD and actions). However, the GitHub domain is read-only—no create/update/merge operations—which is a notable gap for an ops bridge. Also missing some actions like Slack message deletion or calendar availability beyond free slots.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Hosted MCP server to manage a restaurant menu from AI agents - 39 tools over the DuckHub API.
