Developer · Local MCP server
Allure Testops MCP
Allure TestOps MCP - projects, launches, test cases, test results via REST API.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mshegolev/allure-testops-mcp- Version
- 0.9.3
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-08-06
- Updated
- 2026-08-06
- Publisher
- mshegolev (GitHub) · 7 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mshegolev) · how
- Repository
- github.com/mshegolev/allure-testops-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | allure-testops-mcp | 0.9.3 | stdio |
How to connect Allure Testops MCP
Allure Testops MCP runs locally from a Python package published to PyPI: allure-testops-mcp version 0.9.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx allure-testops-mcp. It reads these environment variables: ALLURE_URL (required), ALLURE_TOKEN (required, secret) and ALLURE_SSL_VERIFY; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"allure-testops-mcp": {
"command": "uvx",
"args": [
"allure-testops-mcp"
],
"env": {
"ALLURE_URL": "<value>",
"ALLURE_TOKEN": "<secret>",
"ALLURE_SSL_VERIFY": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from mshegolev (GitHub)
| Server | Runs |
|---|---|
| Gitlab Ci MCPGitLab CI/CD MCP - pipelines, jobs, schedules, MRs, files. Any GitLab (SaaS or self-hosted). | Local · stdio |
| Harbor Registry MCPHarbor Registry MCP - projects, repos, artifacts, storage reports, cleanup (with dry-run). | Local · stdio |
| Jaeger MCPJaeger MCP - search traces, inspect spans, map service dependencies (read-only). | Local · stdio |
| Kibana MCPKibana/Elasticsearch MCP - log search, aggregations, index discovery, dashboards. | Local · stdio |
| Prometheus MCPPrometheus MCP - query metrics, inspect alerts, and explore scrape targets (read-only). | Local · stdio |
| Sonarqube MCPSonarQube MCP - projects, metrics, quality gate, issues, worst-metric ranking. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Alex Llm Attack MCP ServerQuery and retrieve information about various adversarial tactics and techniques used in cyber atta… | Remote · HTTPLive check: ✗ no handshake |
| AlexandriaSearch, read, and cite across 152 libraries: 11 tools, 3 prompts, and a full-text resource. | Local · stdio |
| Algernon MCPFan a goal out to cheap parallel LLM workers on your own key or a free local Ollama. Keep your mind. | Local · stdio |
| Alibaba Cloud DashScope - QwenAlibaba Cloud DashScope MCP: Qwen chat, embeddings, and model discovery on your own account. | Local · stdio |
| AlmanacVerified ephemeris & WMM2025 geomagnetic compute: the physical numbers LLMs hallucinate, done right. | Local · stdio |
| Alpacacloud MCPConnect AI agents to Alpaca Cloud: Postgres, Auth, Storage, Sandboxes, and Workflows. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| AlpicManage your projects, debug deployments, and check analytics for any MCP server you host with Alpic. | Remote · HTTP, SSELive check: sign-in required |
| Alter OnboardingGuide developers from setup through a verified, policy-aware, audited Alter API call. | Remote · HTTPLive check: ✓ handshake |