Testing Bank MCP
Offers tools to test the PagerDuty-Jira integration, including creating test incidents and verifying automatic Jira ticket creation.
Provides tools for managing PagerDuty services, creating test incidents, listing extensions/webhooks, and diagnosing integration issues with connected services.
Enables testing of the PagerDuty-Salesforce integration with tools for creating test incidents and diagnosing synchronization issues.
Provides capabilities to test the PagerDuty-Slack integration, such as sending test messages to Slack channels and verifying webhook configurations.
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., "@Testing Bank MCP PD incidents not appearing in Teams"
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.
Testing Bank MCP
A Model Context Protocol (MCP) router that connects to multiple PagerDuty sandbox environments for testing integrations.
Architecture
┌─────────────────────────────────┐
│ Testing Bank Router MCP │
│ (Orchestrator/Gateway) │
└───────────────┬─────────────────┘
│
┌───────────┼───────────┐
│ │ │
▼ ▼ ▼
┌────────┐ ┌────────┐ ┌────────┐
│PD+Teams│ │PD+Jira │ │PD+Slack│ ... more environments
└────────┘ └────────┘ └────────┘Related MCP server: pagerduty-mcp-community
Available Environments
Environment | Description |
| PagerDuty + Microsoft Teams |
| PagerDuty + Jira Cloud |
| PagerDuty + Salesforce |
| PagerDuty + Slack |
| PagerDuty + AWS CloudWatch/EventBridge |
Installation
cd testing-bank-mcp
npm installConfiguration
1. Set up environment files
Copy the example files and fill in your sandbox credentials:
# For PD + Teams
cp environments/pd-teams/.env.example environments/pd-teams/.env
# For PD + Jira
cp environments/pd-jira/.env.example environments/pd-jira/.env2. Configure your MCP client
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"testing-bank": {
"command": "node",
"args": ["router/index.js"],
"cwd": "/full/path/to/testing-bank-mcp"
}
}
}Usage
Smart Routing (Recommended)
Just describe the customer issue and the router will detect the right environment:
"Customer reports PagerDuty incidents are not posting to their Teams channel"The router will:
Detect this is a PD + Teams issue
Connect to the
pd-teamsenvironmentGive you access to all PD and Teams testing tools
Manual Environment Selection
1. List available environments: list_environments
2. Connect to specific environment: connect_environment("pd-jira")
3. Use environment tools: route_to_environment("pd-jira", "diagnose_integration")Router Tools
Tool | Description |
| List all available testing environments |
| Auto-detect environment from issue description |
| Connect to a specific environment |
| Disconnect from an environment |
| List currently connected environments |
| Send commands to a connected environment |
| Auto-detect and connect in one step |
Environment Tools (PD + Teams Example)
Tool | Description |
| List PagerDuty services |
| Create test incident |
| List webhooks/integrations |
| Send test message to Teams |
| Verify webhook configuration |
| Run full end-to-end test |
| Diagnose common issues |
Example Workflow
User: "Customer says PD incidents aren't creating Jira tickets"
AI uses: smart_route("PD incidents aren't creating Jira tickets")
→ Detects: pd-jira environment
→ Connects to PD + Jira sandbox
AI uses: diagnose_integration()
→ Checks PD API connection
→ Checks Jira API connection
→ Lists Jira extensions in PD
→ Returns recommendations
AI uses: test_full_integration(service_id="PXXXXXX")
→ Creates test incident in PD
→ Waits for Jira sync
→ Searches for created ticket
→ Reports resultsAdding New Environments
Create directory:
environments/pd-newservice/Copy template from existing environment
Modify API calls for the new service
Add environment to
ENVIRONMENTSinrouter/index.jsCreate
.env.examplewith required credentials
Security Notes
Never commit
.envfilesUse sandbox/test environments only
Rotate API keys regularly
Document which sandboxes are connected to production data (if any)
Available Tools
7 toolsconnect_environmentC
Connect to a specific testing environment sandbox
Inputs: environment_id (required).
detect_environmentB
Automatically detect which environment to use based on a customer issue description
Inputs: issue_description (required).
disconnect_environmentB
Disconnect from a testing environment
Inputs: environment_id (required).
get_active_environmentsB
Get list of currently connected environments
Inputs: no named parameters.
list_environmentsA
List all available testing environments in the Testing Bank
Inputs: no named parameters.
route_to_environmentB
Send a command to a connected environment. Use this to execute tools in the child environment.
Inputs: tool_name (required), environment_id (required), tool_args.
smart_routeA
Automatically detect the right environment from issue description and connect to it
Inputs: issue_description (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Tools are mostly distinct, but detect_environment and smart_route have overlapping purposes (detecting vs detecting+connecting), which could cause some confusion. Other tools clearly cover different actions.
Six tools follow verb_noun snake_case pattern (e.g., connect_environment, list_environments). smart_route deviates by starting with an adjective instead of a verb, breaking the pattern slightly.
With 7 tools, the set is well-scoped for managing testing environments: connect, detect, disconnect, list, route, and smart route cover essential operations without bloat.
The tool surface covers core lifecycle (connect, disconnect, list, interact) and adds detection features. Missing environment creation or modification, but those may be out of scope for a testing bank server.
Related MCP Connectors
One MCP endpoint for your company's tools, with per-person sign-in, policy and audit.
One MCP server for all your work accounts: Slack, Teams, Google Chat, Jira, ClickUp, digest, tasks.
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceA unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies.2,088 npm2,686Apache 2.0
- AlicenseAqualityCmaintenanceA community-maintained MCP server for interacting with PagerDuty accounts, enabling management of incidents, services, schedules, and event orchestrations through MCP-enabled clients.201Apache 2.0

pagerduty-mcpofficial
AlicenseBqualityFmaintenanceEnables management of PagerDuty incidents, services, schedules, and more directly from MCP-enabled clients, with embedded interactive UIs for incident command center, on-call management, and other features.6379Apache 2.0- AlicenseBqualityCmaintenanceUnified MCP server for DevOps engineers that provides real-time read and write access to Kubernetes, ArgoCD, Prometheus, and PagerDuty from any MCP-compatible AI agent.2199 npm4MIT