CyberQP

● Active

io.github.WYRE-AI/cyberqp-mcp

MCP server for CyberQP's privileged access management API.

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "cyberqp-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/cyberqp-mcp:v1.0.3"
      ],
      "env": {
        "CYBERQP_ACCESS_TOKEN": "<your CYBERQP_ACCESS_TOKEN>",
        "MCP_TRANSPORT": "stdio",
        "AUTH_MODE": "env",
        "LOG_LEVEL": "info"
      }
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --env CYBERQP_ACCESS_TOKEN='<your CYBERQP_ACCESS_TOKEN>' --env MCP_TRANSPORT=stdio --env AUTH_MODE=env --env LOG_LEVEL=info --transport stdio cyberqp-mcp -- docker run -i --rm ghcr.io/wyre-ai/cyberqp-mcp:v1.0.3
OpenAI Codex CLI
codex mcp add cyberqp-mcp --env CYBERQP_ACCESS_TOKEN='<your CYBERQP_ACCESS_TOKEN>' --env MCP_TRANSPORT=stdio --env AUTH_MODE=env --env LOG_LEVEL=info -- docker run -i --rm ghcr.io/wyre-ai/cyberqp-mcp:v1.0.3
VS Code
code --add-mcp '{"name":"cyberqp-mcp","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/wyre-ai/cyberqp-mcp:v1.0.3"],"env":{"CYBERQP_ACCESS_TOKEN":"<your CYBERQP_ACCESS_TOKEN>","MCP_TRANSPORT":"stdio","AUTH_MODE":"env","LOG_LEVEL":"info"}}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

Environment variables
  • CYBERQP_ACCESS_TOKENrequiredsecretCyberQP OAuth2 access token (authorization_code flow, offline_access scope). Exchanged and refreshed upstream of this server - it only ever holds a live bearer token.
  • MCP_TRANSPORTTransport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
  • AUTH_MODECredential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
  • LOG_LEVELLog verbosity: debug, info, warn, error

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Other
Version
1.0.3
Registry
active
Published
11/20/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: CyberQP is maintained.

Maintained
Active
Last commit 9 days ago (Nov 12, 2026), 2 open issues.
Official registry
Active
Published as io.github.WYRE-AI/cyberqp-mcp in the official MCP registry, version 1.0.3.
Source
No licence found
Public repository, but GitHub reports no recognised licence (0 stars). Check the README before shipping it in a product.
Runs
On your machine
A local Docker package started by your client; it can reach whatever your user account can.
Credentials
1 required
Declared environment variables: CYBERQP_ACCESS_TOKEN. They stay on your machine; the config on this page shows where each goes.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 17, 2026
Stars
0
Forks
0
Last push
Nov 12, 2026
License
Other

TypeScript

From the README

CyberQP MCP Server MCP server for CyberQP's (formerly QuickPass Cybersecurity) privileged access management (PAM) API - customer/account metadata, the tenant event log, and JIT (Just-In-Time) account status/policy visibility, for AI assistants and the WYRE Conduit gateway. Authentication CyberQP authenticates with OAuth2 authorizationcode flow (offlineaccess scope, refreshtoken-backed) - not clientcredentials. This connector never performs the OAuth dance itself: the WYRE Conduit gateway owns the authorize/exchange/refresh legs, and this server only ever receives a live bearer access token, sent as Authorization: Bearer to CyberQP's API. In gateway mode the token arrives per-request via the X-CyberQP-Access-Token header; in local/stdio mode it's read once from CYBERQPACCESSTOKEN. Configuration Copy .env.example and set the variables below. The stdio transport reads CYBERQPACCESSTOKEN and does not use CONDUITS2SSECRET. /health stays unauthenticated and does not read credentials. HTTP authentication With MCPTRANSPORT=http and CONDUITS2S_SECRET set, every /mcp request must include X-Gateway-S2S: v1 is the lowercase hex HMAC-SHA256 of the ASCII message t= , keyed by CONDUITS2SSECRET. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns 401 before any vendor credential is read. The secret is never written to logs or error bodies. In AUTHMODE=gateway, /mcp also requires X-CyberQP-Access-Token.…

Read the full README on GitHub →

The most-starred Other servers in the index, with their live-check result.

ServerStarsLast pushLive check
Labelhead Artist Momentum114,594Nov 2026Working
World Monitor91,002Nov 2026Needs sign-in
Tldraw51,470Nov 2026Working
OpenSEO28,515Nov 2026Needs sign-in
Windows MCP11,833Nov 2026Local / not checked

CyberQP: questions people ask

Is CyberQP a remote or a local MCP server?
According to its entry in the official MCP registry, CyberQP ships as a local package (Docker) that your client starts on your machine.
Does CyberQP need an API key?
Its registry entry declares one required environment variable: CYBERQP_ACCESS_TOKEN. The config on this page shows where each goes.
Is CyberQP safe to use?
Mostly fine: CyberQP is maintained. In detail — maintained: Active; official registry: Active; source: No licence found; runs: On your machine; credentials: 1 required. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is CyberQP still maintained?
Active: the repository's last commit 9 days ago. Last push Nov 12, 2026, 0 GitHub stars, Other licence. Read from GitHub on Nov 17, 2026.
How do I add CyberQP to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. AutotaskMCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.★ 64
  2. ConnectWise ManageMCP server for ConnectWise Manage PSA — companies, tickets, projects, time entries, and more.★ 32
  3. NinjaOneMCP server for NinjaOne RMM — devices, organizations, alerts, and tickets.★ 32
  4. IT GlueMCP server for IT Glue — organizations, configurations, passwords, flexible assets, and documents.★ 18
Browse all Other →

Add the badge to your site

Show visitors that CyberQP is listed here — it’s also the link we check for a free listing.

CyberQP — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-wyre-ai-cyberqp-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="CyberQP — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![CyberQP — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-wyre-ai-cyberqp-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-wyre-ai-cyberqp-mcp) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-wyre-ai-cyberqp-mcp) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-wyre-ai-cyberqp-mcp)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-wyre-ai-cyberqp-mcp"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-wyre-ai-cyberqp-mcp"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-wyre-ai-cyberqp-mcp"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).