Skip to main content
Beta Feature — MCP Server is currently in beta. Core functionality is stable, but some behaviors and interfaces may change as we continue development. Contact support if you run into any issues.
PlayerZero can connect to any remote MCP-compatible server, extending what AI agents can access during Player sessions. This lets you bring in data from observability platforms, log providers, internal tools, and any other service that exposes an MCP server.

​
What Remote MCP Servers Enable

  • Extend agent capabilities — Give AI agents access to tools and data beyond your codebase, like monitoring dashboards, log search, or internal APIs
  • Auto-discover tools — PlayerZero automatically detects available tools from the connected MCP server. No manual configuration of individual tools is required.
  • Scoped access — Control which PlayerZero projects can use each connection
  • Multiple connections — Connect as many MCP servers as you need, each with its own authentication and project scope

​
Requirements

The external MCP server must be remote and hosted — PlayerZero connects via SSE (Server-Sent Events) or Streamable HTTP transport. Local stdio-based MCP servers (like those used by desktop AI assistants) are not supported.

​
Example Use Cases

Use CaseMCP ServerWhat It Enables
ObservabilityDatadogQuery monitors, search logs, retrieve dashboards and traces
Log analysisCoralogixSearch and analyze application logs during debugging
Internal toolsCustom MCP serverAccess internal APIs, runbooks, or proprietary data sources

​
Setup

  1. In PlayerZero, navigate to Settings → Ticketing
  2. Go to the Remote MCP Servers section and click New Connector
  3. Fill in the connection details:
    • Name — A descriptive name for this connection (must be unique within your organization)
    • Description — Optional context about what this server provides
    • MCP Server URL — The remote MCP server endpoint (e.g., https://mcp.example.com/sse)
  4. Under Project Access, choose which PlayerZero projects can use this connection:
    • All projects — Every project in your organization
    • Specific projects — Select individual projects
  5. Under Authentication, choose the method that matches your MCP server:

​
Authentication Methods

MethodWhen to UseWhat You Provide
Auth TokenServer requires a Bearer tokenA single access token, sent as Authorization: Bearer <token>
OAuthServer supports OAuth 2.0 with dynamic client registrationNothing — PlayerZero handles the OAuth flow automatically
CustomServer requires API keys or custom headers (e.g., Datadog)One or more key-value header pairs
No authenticationServer is publicly accessibleNothing
For Datadog, use Custom authentication with two headers: DD-API-KEY and DD-APPLICATION-KEY. See the Datadog setup guide for step-by-step instructions.
  1. Click Add
PlayerZero validates the connection by reaching out to the MCP server. If successful, tools from the server are automatically available in Player sessions for the selected projects. If the connection fails, you’ll see an error message. Common issues:
  • Authentication failed (401/403) — Verify your credentials are correct
  • Connection timed out — Check that the MCP Server URL is correct and the server is reachable
  • Could not resolve host — Verify the URL

​
Managing Connections

After setup, you can:
  • Edit project access — Add or remove projects that can use this connection
  • Update credentials — Change the authentication token or headers
  • Delete — Remove the connection entirely

​
Get Started

👉 Contact support