Integration Assistant MCP Server

The ByteBrew Integration Assistant is a remote Model Context Protocol (MCP) server that helps you integrate the ByteBrew SDK into your Unity project directly from your AI coding assistant. Connect any MCP-compatible tool to the assistant and ask it how to install, initialize, and use ByteBrew in your game. Answers are grounded in the official ByteBrew Unity documentation.

Overview

tag

The Integration Assistant MCP server exposes tools that walk your AI assistant through integrating the ByteBrew Unity SDK. Once connected, you can prompt your assistant with questions like "add ByteBrew to my Unity project" or "how do I track a custom event with ByteBrew?" and it will pull the correct, up-to-date integration steps.

Server Details

tag

The Integration Assistant is a remote MCP server over Streamable HTTP. There is nothing to install or run locally. Point your tool at the server URL below.

fiber_manual_record
Server URL: https://docs.bytebrew.io/mcp
fiber_manual_record
Transport: Streamable HTTP (remote)
fiber_manual_record
Authentication: None required. The server is public and free to use.

Claude Code

tag

Add the server with the claude mcp add command using the HTTP transport:

claude mcp add --transport http bytebrew-integration-assistant https://docs.bytebrew.io/mcp

Or add it to a project's .mcp.json file to share it with your team:

{
  "mcpServers": {
    "bytebrew-integration-assistant": {
      "type": "http",
      "url": "https://docs.bytebrew.io/mcp"
    }
  }
}

Run /mcp inside Claude Code to confirm the bytebrew-integration-assistant server is connected.

Cursor

tag

Add the server to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project root. Cursor uses the url field for remote Streamable HTTP servers:

{
  "mcpServers": {
    "bytebrew-integration-assistant": {
      "url": "https://docs.bytebrew.io/mcp"
    }
  }
}

Then open Settings → MCP & Integrations and verify bytebrew-integration-assistant shows a green status with its tools listed.

OpenAI Codex

tag

Use the Codex CLI to register the remote server:

codex mcp add bytebrew-integration-assistant --url https://docs.bytebrew.io/mcp

This writes an entry to ~/.codex/config.toml. You can also add it directly:

[mcp_servers.bytebrew-integration-assistant]
url = "https://docs.bytebrew.io/mcp"

Start a Codex session and run /mcp to confirm the server is connected and its tools are listed.

Google Antigravity

tag

In Antigravity, open Settings → Customizations and click Open MCP Config to edit mcp_config.json. Antigravity uses the serverUrl field for remote servers:

{
  "mcpServers": {
    "bytebrew-integration-assistant": {
      "serverUrl": "https://docs.bytebrew.io/mcp"
    }
  }
}

Save the file, then open the MCP Servers panel and refresh to load the bytebrew-integration-assistant tools.

Cursor Agent (CLI)

tag

The cursor-agent CLI automatically discovers the same mcp.json configuration used by the Cursor editor. Add the server to ~/.cursor/mcp.json or your project's .cursor/mcp.json:

{
  "mcpServers": {
    "bytebrew-integration-assistant": {
      "url": "https://docs.bytebrew.io/mcp"
    }
  }
}

In an interactive cursor-agent session, enable the server with the slash command:

/mcp enable bytebrew-integration-assistant

Gemini CLI

tag

Add the server to your Gemini CLI settings.json (global at ~/.gemini/settings.json or project-scoped at .gemini/settings.json). Gemini CLI uses the httpUrl field for Streamable HTTP servers:

{
  "mcpServers": {
    "bytebrew-integration-assistant": {
      "httpUrl": "https://docs.bytebrew.io/mcp"
    }
  }
}

Launch gemini and run the /mcp command to list the discovered server and its tools.

JetBrains AI Assistant

tag

In your JetBrains IDE, go to Settings → Tools → AI Assistant → Model Context Protocol (MCP) and click Add. Choose As JSON and paste the following. AI Assistant connects to remote servers over Streamable HTTP using the url field:

{
  "mcpServers": {
    "bytebrew-integration-assistant": {
      "url": "https://docs.bytebrew.io/mcp"
    }
  }
}

Apply the settings. The assistant's tools appear in the MCP section once the connection succeeds.

Visual Studio Code

tag

Create a .vscode/mcp.json file in your workspace. VS Code uses the servers root key and requires "type": "http" for remote servers:

{
  "servers": {
    "bytebrew-integration-assistant": {
      "type": "http",
      "url": "https://docs.bytebrew.io/mcp"
    }
  }
}

You can also add it from the command line:

code --add-mcp '{"name":"bytebrew-integration-assistant","type":"http","url":"https://docs.bytebrew.io/mcp"}'

Using the Assistant

tag

After connecting the server, prompt your AI assistant with integration tasks in natural language. The assistant calls the Integration Assistant tools to retrieve the correct ByteBrew Unity steps and applies them to your project. Use prompts such as:

fiber_manual_record
"Install the ByteBrew Unity SDK in my project and initialize it on startup."
fiber_manual_record
"Add remote configs to my app that let me customize the ad rate between stages."
fiber_manual_record
"Track a custom event when the player completes a level and pass the level number as an attribute."
fiber_manual_record
"Log an in-app purchase with ByteBrew when the player buys the starter pack."
fiber_manual_record
"Set up an A/B test in my game that changes the reward amount per group."
fiber_manual_record
"Configure my Unity build settings for ByteBrew on both iOS and Android."

FAQs

tag

MCP is an open standard that lets AI assistants connect to external tools and data sources. The ByteBrew Integration Assistant is an MCP server that gives your assistant direct access to ByteBrew Unity integration steps and documentation.

Confirm the server URL is exactly https://docs.bytebrew.io/mcp and that you used the correct field for your tool (url, httpUrl, or serverUrl). Confirm the transport is set to HTTP where your tool requires it. Restart your tool or refresh its MCP server list to reload the connection.

The Integration Assistant covers integrating the ByteBrew Unity platform SDK. For other engines, see the SDK Integration guides in the sidebar.

No. The Integration Assistant is a documentation and integration helper. It does not read or write your analytics, dashboard, or studio data.

No. The server is public and requires no authentication. Leave out any headers or token fields when configuring it.

Any MCP-compatible client that supports a remote Streamable HTTP server works. This page provides setup steps for Claude Code, Cursor, OpenAI Codex, Google Antigravity, Cursor Agent, Gemini CLI, JetBrains AI Assistant, and Visual Studio Code.