MCP OpsBridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port (default: 3002). | 3002 |
| TRANSPORT | No | Transport mode: stdio (default) or http. | stdio |
| SLACK_TOKEN | No | Slack bot token (xoxb-...). Required for Slack tools. | |
| DATABASE_URL | No | PostgreSQL connection string. Required for database tools. | |
| GITHUB_TOKEN | No | GitHub personal access token. Required for private repos and create_pr tool. | |
| CALENDAR_TOKEN | No | Google Calendar OAuth token. Required for Calendar tools. |
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 | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| github_search_issuesC | Search issues in a GitHub repository by query, state, and label |
| github_get_repo_statsB | Get repository statistics: stars, forks, open issues, recent commits |
| github_list_reposA | List repositories for the authenticated user with metadata |
| github_get_commitsB | Get commit history for a branch |
| github_get_pull_requestsB | Get pull requests in a repository with diff statistics |
| github_get_file_contentsB | Get contents of a file or directory from a repository |
| github_list_branchesB | List all branches in a repository |
| calendar_list_calendarsA | List all calendars accessible by the authenticated user |
| calendar_query_eventsA | List events in a date range from Google Calendar |
| calendar_get_event_detailsA | Get detailed information about a single event including attendees and description |
| calendar_find_free_slotsB | Find mutually available time slots across calendars |
| calendar_create_eventB | Create a calendar event with optional attendees (requires approval) |
| calendar_update_eventA | Update an existing calendar event (requires approval) |
| calendar_add_attendeeC | Add an attendee to an existing event (requires approval) |
| calendar_delete_eventA | Delete a calendar event (double approval required — irreversible) |
| db_execute_queryA | Execute a read-only SQL query against PostgreSQL |
| db_list_tablesB | List all tables in a database schema |
| db_describe_tableB | Show columns and types for a table |
| db_insert_rowA | Insert a new row into a table (auto-approved, logged) |
| db_update_rowsA | Update rows in a table matching a WHERE clause (auto-approved, logged) |
| db_delete_rowsA | Delete rows from a table matching a WHERE clause (requires approval) |
| db_truncate_tableA | Truncate a table — removes all rows (double approval required) |
| db_drop_tableA | Drop a table — permanently removes table and data (double approval required) |
| db_migrate_schemaA | Execute a schema migration (ALTER/CREATE/DROP) — structural change (double approval required) |
| slack_list_channelsC | List accessible Slack channels |
| slack_get_threadB | Retrieve messages in a thread |
| slack_get_channel_historyC | Get recent messages from a Slack channel |
| slack_send_messageB | Send a message to a Slack channel (requires approval) |
| slack_send_thread_replyA | Send a reply in a Slack thread (requires approval) |
| approve_actionA | Confirm or deny a pending action that requires user approval. Use this to respond to pending_approval or pending_approval_2 responses. |
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 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.