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 "Install 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 MCPPD 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: Gateway MCP Server (mcpware)
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)
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/RFH-PDTest/testing-bank-router-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server