Which integrations are available for this server?

Provides tools for searching Confluence pages, reading articles, and writing content to pages. Provides tools for querying Jira tickets, filtering by testing status and team, searching with JQL, and generating testing summaries. Provides tools for interacting with Slack, including reading channel messages, analyzing auto test results, detecting blocking issues, sending messages to a restricted channel, and debugging bot messages.

How do I use MCP Servers for QA and Release Coordination?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Servers for QA and Release Coordination give me the release status overview for today" 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.

MCP Servers for QA and Release Coordination

by 1olegshev

Overview Schema Related Servers Score Discussions

TypeScript

Remote

MCP Servers

Model Context Protocol servers for Slack, Jira, Confluence, and release coordination. Built for QA workflows and daily release status reporting.

Quick Start

# 1. Install
git clone <repo> && cd mcp-servers
npm install

# 2. Configure credentials (see below)
cp env.example .env
# Edit .env with your tokens

# 3. Build & verify
npm run build
./test-servers.sh

Related MCP server: MCP Atlassian Node Server

Credentials Setup

All servers load credentials from .env in project root. Never put credentials in mcp.json.

Jira & Confluence

JIRA_BASE_URL=https://yourorg.atlassian.net
JIRA_EMAIL=your-email@company.com
JIRA_API_TOKEN=your-api-token

CONFLUENCE_BASE_URL=https://yourorg.atlassian.net
CONFLUENCE_EMAIL=your-email@company.com
CONFLUENCE_API_TOKEN=your-api-token

Get API tokens: https://id.atlassian.com/manage-profile/security/api-tokens

Slack (XOXC/XOXD Session Auth)

SLACK_MCP_XOXC_TOKEN=xoxc-your-session-token
SLACK_MCP_XOXD_TOKEN=xoxd-your-cookie-value

Extract tokens:

Open Slack in browser, log in
DevTools (F12) → Application → Cookies → https://app.slack.com
Find d cookie → this is XOXD (starts with xoxd-)
Network tab → reload → find api.slack.com request
In headers, find Authorization: Bearer xoxc-... → this is XOXC

See slack/README.md for detailed instructions.

MCP Configuration Files

This project includes multiple MCP configuration files for different purposes:

File	Purpose
`.vscode/mcp.json`	VS Code Claude extension - edit paths and restart VS Code
`.mcp.json`	Claude Desktop app configuration
`mcp_config.json`	Reference config with npm script commands

VS Code Setup:

cp .vscode/mcp.json.example .vscode/mcp.json
# Update paths in mcp.json to your project location
# Restart VS Code after changes

Documentation

Each server has its own README with tools, CLI testing, and troubleshooting:

Server	Purpose	Docs
Slack	Channel messages, auto test analysis, blocking issue detection	slack/README.md
Jira	Testing status, ticket queries, team filtering	jira/README.md
Confluence	Page search, article reading/writing	confluence/README.md
Release Coordinator	Orchestrates Jira+Slack into release reports	release-coordinator/README.md
Shared	Common utilities (env loading, errors, types)	shared/README.md

Slack Deep-Dive Docs

The Slack server is the most complex and has additional documentation:

Doc	Purpose
ARCHITECTURE.md	File structure, data flows, modification patterns
QUICK_REFERENCE.md	Copy-paste code snippets
SECURITY.md	Auth security, threat model
TESTING_DOCUMENTATION.md	Test coverage, Jest setup

Tool Quick Reference

Task	Tool	Server
Full release status report	`get_comprehensive_release_overview`	release-coordinator
Find blocking issues	`get_blocking_issues`	slack
Check auto test results	`get_auto_test_status`	slack
Get test manager decision	`get_test_manager_update`	slack
Count tickets by status	`get_testing_summary`	jira
List tickets in QA/Testing	`get_testing_remaining`	jira
Search Jira with JQL	`search_issues`	jira
Read Confluence page	`read_article`	confluence
Search Confluence	`search_pages`	confluence
Post to Slack	`send_message`	slack (restricted to #qa-release-status)
Debug bot messages	`find_bot_messages`	slack
Get full message details	`get_message_details`	slack

Architecture Invariants

These are intentional constraints - do not change without explicit request:

Constraint	Location	Reason
Slack writes only to `#qa-release-status`	`slack/src/auth/slack-auth.ts`	Prevents accidental posts
NoTest labels excluded by default	`jira/src/server.ts`	Matches testing board
Team query mappings are hardcoded	`jira/src/server.ts`	Business logic
Slack markdown (not standard)	All Slack output	`bold` not `bold`, `<url\|text>` not `[text](url)`
ESM imports need `.js` extension	All TypeScript	Required for ES modules

Running Servers

npm run dev              # All servers with auto-reload
npm run start            # All servers production mode
npm run start:slack      # Individual server
npm run start:jira
npm run start:confluence
npm run start:release-coordinator

Troubleshooting

Error	Fix
`Missing X configuration`	Check `.env` has required variables
`401 Unauthorized`	API token expired or invalid
`Cannot find module`	Run `npm run build`
`Write access restricted`	Slack writes only allowed to #qa-release-status
ESM/require errors	Imports must use `.js` extension

VS Code MCP Caching

After rebuilding a server, VS Code caches the old instance. MCP tools will use OLD code until you restart VS Code (Cmd+Shift+P → "Reload Window").

Project Structure

├── README.md                    # This file
├── .env                         # Credentials (gitignored)
├── env.example                  # Credential template
├── mcp_config.json              # MCP server definitions
├── mcp-servers/
│   ├── slack/                   # Slack MCP server
│   │   ├── README.md            # Slack docs
│   │   ├── docs/                # Deep-dive documentation
│   │   └── src/
│   ├── jira/                    # Jira MCP server
│   │   ├── README.md
│   │   └── src/
│   ├── confluence/              # Confluence MCP server
│   │   ├── README.md
│   │   └── src/
│   ├── release-coordinator/     # Orchestration server
│   │   ├── README.md
│   │   └── src/
│   └── shared/                  # Shared utilities
│       ├── README.md
│       └── src/
└── scripts/                     # Automation (cron jobs)
    └── README.md

This server cannot be installed

license - not found

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

–Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

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 Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

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/1olegshev/mcp-servers'

If you have feedback or need assistance with the MCP directory API, please join our Discord server