MCP server for Zephyr Squad Server/Data Center — drive ZAPI test management from an AI agent.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"zephyr-squad-server-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# zephyr-squad-server-mcp An [MCP](https://modelcontextprotocol.io) server that lets an AI agent drive **Zephyr for Jira — Server / Data Center (ZAPI)**, the test-management suite for Jira. It exposes the most common test-management operations (cycles, folders, executions, test steps, step results, ZQL search) as well-described tools over **stdio**, so it plugs into Claude Desktop, Claude Code, and any other MCP client. > This targets the **Server/DC** flavor (`/rest/zapi/latest`). It is **not** for > Zephyr Squad **Cloud**, which uses a different JWT-signed API. ## Install The server is published on PyPI and is easiest to run with [`uv`](https://docs.astral.sh/uv/): ```bash uvx zephyr-squad-server-mcp # run directly, no install # or uv tool install zephyr-squad-server-mcp # or, in a venv pip install zephyr-squad-server-mcp ``` ## Configuration The connection rides on your Jira instance's authentication (shared by ZAPI and the Jira core REST API). Configure via environment variables or a `.env` file (see [`.env.example`](.env.example)): | Variable | Required | Default | Description | |---|---|---|---| | `JIRA_URL` | ✅ | — | Jira base URL, e.g. `https://jira.company.com` (no `/rest` suffix). | | `JIRA_PERSONAL_TOKEN` | one of | — | Personal Access Token → `Authorization: Bearer …` (**recommended for DC**). | | `JIRA_USERNAME` + `JIRA_PASSWORD` | one of | — | Basic-auth fallback (password or API token). Used only if `JIRA_PERSONAL_TOKEN` is empty. | | `ZEPHYR_API_PATH` | | `/rest/zapi/latest` | ZAPI base path on the Jira host. | | `ZEPHYR_TIMEOUT` | | `30` | Per-request timeout (seconds). | | `ZEPHYR_VERIFY_SSL` | | `true` | Verify TLS certs. Set `false` only for trusted internal self-signed hosts. | The server fails fast with a clear error if the base URL or authentication is missing. ## Client configuration (stdio) Add to your MCP client config (e.g. Claude Desktop `claude_desktop_config.json` or Claude Code `.mcp.json`): ```json { "mcpServers"…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.