Britive MCP Server

Britive's MCP Server enables AI agents and users to interact with the Britive platform. Britive's MCP server exposes several tools that enable users and AI agents to interact with the Britive platform for dynamic access, query configurations, reporting, and access activity.  

To learn more about MCPs, see Get Started with MCP. 

Prerequisites

• Python version 3.10 or higher. Download from Python downloads.
• Ensure you have the latest version of Git installed and access to the repository. Download git from the git downloads.
• Any MCP client. For example, Claude desktop and VS Code Copilot.

Setting up the Britive MCP Server

1. Clone the GitHub repository that has the MCP server. 
   ShellShell

   git clone https://github.com/britive/mcp-server.git

2. heChange directory to mcp-server.

   cd mcp-server

3. Create a virtual environment: 

   python -m venv <virtual_env_name>

4. Activate virtual environment: 
   1. Windows:

      <virtual_env_name>\Scripts\activate

   2. macOS/Linux:
      

      ShellShell

      source <virtual_env_name>/bin/activate

5. Install Python packages (dependencies):
   

   ShellShell

   pip install -r requirements.txt

Configuring your MCP client and Authentication

Authentication to the Britive platform can be performed using the Britive CLI or a Static Token:

• Option 1: CLI login using PyBritive (Recommended):
  1. Install the PyBritive CLI if it is not already installed. For more information, see PyBritive Documentation.
  2. Configure the tenant, if it has not already been configured, using the following command. To find out more about how to enter the tenant name, see PyBritive: Tenant selection logic.
     ShellShell

      pybritive configure tenant

  3. Log in to pyBritive:l
     

     ShellShell

     pybritive login

  4. Log in using the following command if you have multiple tenants: 
     ShellShell

     pybritive login --tenant=<your_tenant_name>

  5. Log in directs you to the Britive login page, where you can enter your credentials.
  6. Modify your MCP JSON file to configure the Britive MCP. The MCP JSON file may be located at different locations depending on your MCP client and how it was installed. 
     • Windows: If you are using the Claude desktop as your MCP client, the JSON file might be at this location: %APPDATA%\Claude\claude_desktop_config.json.
       ShellShell

       {
         "servers": {
           "britive": {
             "command": "C:\\Users\\YourName\\mcp-server\\venv\\Scripts\\python.exe",
             "args": [
               "C:\\Users\\YourName\\mcp-server\\britive_mcp_tools\\core\\mcp_runner.py"
             ],
             "env": {
               "PYTHONPATH": "C:\\Users\\YourName\\mcp-server",
               "BRITIVE_TENANT": "your_tenant_name",
             }
           }
         }
       }

     • macOS/Linux: If you are using the Claude desktop on macOS as your MCP client, the JSON file might be at this location: ~/Library/Application Support/Claude/claude_desktop_config.json.
       ShellShell

       {
         "servers": {
           "britive": {
             "command": "/user/local/bin/python",
             "args": [
               "/Users/YourName/mcp-server/britive_mcp_tools/core/mcp_runner.py"
             ],
             "env": {
               "PYTHONPATH": "/Users/YourName/mcp-server",
               "BRITIVE_TENANT": "your_tenant_name",
             }
           }
         }
       }

     • where:

       • command: Full path to the Python executable
       • args: Full path to the britive_mcp_tools\core\mcp_runner.py
       • PYTHONPATH: Set the Python path to the mcp-server directory (repository)
       • BRITIVE_TENANT: Your tenant on Britive. This tenant name must match the name used in the PyBritive CLI
• Option 2: Log in using a static token:
  1. Generate a static token from the Britive UI. For more information, see API Tokens.
  2. Copy the token to use in the MCP JSON file.
  3. Modify your MCP JSON file to configure the Britive MCP.  The MCP JSON file may be located at different locations depending on your MCP client and how it was installed.
     • Windows:  If you are using the Claude desktop as your MCP client, the JSON file might be at this location: %APPDATA%\Claude\claude_desktop_config.json

       {
         "servers": {
           "britive": {
             "command": "C:\\Users\\YourName\\mcp-server\\venv\\Scripts\\python.exe",
             "args": ["C:\\Users\\YourName\\mcp-server\\britive_mcp_tools\\core\\mcp_runner.py"
             ],
             "env": {
               "PYTHONPATH": "C:\\Users\\YourName\\mcp-server",
               "BRITIVE_TENANT": "your_tenant_name",
               "BRITIVE_STATIC_TOKEN": "your_static_token_here"
             }
           }
         }
       }

     • macOS/Linux: If you are using the Claude desktop on macOS as your MCP client, the JSON file might be at this location: ~/Library/Application Support/Claude/claude_desktop_config.json.

       {
         "servers": {
           "britive": {
             "command": "/user/local/bin/python",
             "args": [
               "/Users/YourName/mcp-server/britive_mcp_tools/core/mcp_runner.py"
             ],
             "env": {
               "PYTHONPATH": "/Users/YourName/mcp-server",
               "BRITIVE_TENANT": "your_tenant_name",
               "BRITIVE_STATIC_TOKEN": "your_static_token_here"
             }
           }
         }
       }

     • where:

       • command: Full path to the Python executable
       • args: Full path to the britive_mcp_tools\core\mcp_runner.py module
       • PYTHONPATH: Set the Python path to the mcp-server directory (repository)
       • BRITIVE_TENANT: Your tenant on Britive. Do not use the entire FQDN for the subdomain. For example, for https://super-customer.test.aws.britive-corp.com, use super-customer.test.aws as a tenant subdomain.
       • BRITIVE_STATIC_TOKEN: Static token created in the previous step

• Connecting to the MCP server using a client application

  For more information, see Connect to Local MCP Servers.