​
Prerequisites

  • Active PlayerZero account with project access
  • Editor or Owner permissions in that project
  • An MCP-compatible AI assistant (VS Code, Copilot, Cursor, etc.)

​
Step 1: Create an MCP Token

  1. Open Project Settings
  2. Generate Token
    • Click New Token
    • Give it a descriptive name, e.g. Cursor MCP or Claude Desktop
    • Click Create Token
    • Copy & store the token immediately – it won’t be shown again.
  3. Token details
    • Expires in 90 days
    • Scoped to one project
    • Create multiple tokens for different tools or teammates

​
Step 2: Configure Your MCP Client

Use the following syntax: 
{
    "mcp": {

        "inputs": [
            {
                "id": "api-key",
                "type": "promptString",
                "description": "Your API key for the MCP server"
            }
        ],
        "servers": {
            "playerzero": {                      
                "url": "https://playerzero.ai/api/mcp", 
                "headers": {
                    "Authorization": "Bearer [ENTER TOKEN HERE]",
                },
            }
        }
    },
    "chat.mcp.discovery.enabled": true
}

​
Step 3: Available Tools

playerzero_status: Tests your connection to PlayerZero. 
Use the playerzero_status tool to check if PlayerZero is working.
Response:
  • “true” if connection is successful
  • Error message if there are authentication or connection issues
ask_playerzero: Query your codebase using PlayerZero’s AI. Parameters:
  • query (required): Your question about the codebase
  • playerId (optional): Continue existing conversation
  • lastMessageId (optional): Resume from specific message Usage Examples:
Use ask_playerzero to find all authentication-related files in the codebase.

Use ask_playerzero to explain how the user registration process works.

Use ask_playerzero to identify potential security vulnerabilities in the API routes.

​
Step 4: Best Practices

​
Security Considerations

  • Token Security: Store MCP tokens securely and never commit them to version control
  • Project Scope: Tokens only provide access to the specific project they were created for
  • Audit Trail: All MCP interactions are logged in your PlayerZero project
  • Expiration: Tokens automatically expire after 90 days for security