MCP server for ReportPortal
MCP server for ReportPortal. That is what the reportportal mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The ReportPortal MCP Server is a bridge between your ReportPortal instance and AI chat assistants (such as Claude Desktop, GitHub Copilot, Cursor). In simple terms, it lets you ask questions in plain English about your test runs and get answers directly from ReportPortal. It follows the official MCP guidelines.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: RP_API_TOKEN, RP_HOST, RP_PROJECT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Before setting up the MCP server, you need the following information from your ReportPortal instance:
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by reportportal; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against ReportPortal's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"reportportal": {
// paste your chosen configuration here
}
}
}Configuration as documented by the project. Restart the client after saving.
Before setting up the MCP server, you need the following information from your ReportPortal instance:
| Variable | Description | Required |
|---|---|---|
| RP_API_TOKEN | Credential the server authenticates with. | Yes |
| RP_HOST | Endpoint or connection string the server talks to. | Optional |
| RP_PROJECT | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.