Self-hosting the MCP server

Run the open-source Brixus365 MCP server yourself, with your own API key.

When to self-host

Reach for self-hosting when you want to:

• Audit the code before running it against your account.
• Pin a specific version rather than tracking the hosted server.
• Run inside a private network (air-gapped / VPC) where the agent can’t reach a public URL.
• Point at a staging environment via a custom API base URL.

For everything else, the hosted server is faster and has nothing to maintain.

Prerequisites

• Node.js 18 or newer.
• A Brixus365 API key. The email-only widget on the developers page is the fastest path to a bx_preview_… key for testing — for a production-ready bx_live_… key, see Creating API keys.

Build from source

The server is open source — Brixus-Technologies/brixus365-mcp. Clone and build it:

git clone https://github.com/Brixus-Technologies/brixus365-mcp.git
cd brixus365-mcp
npm install && npm run build

This produces dist/index.js — the entrypoint your client will run.

Configuration

The self-hosted server reads its configuration from environment variables.

Environment variable		Default	Description
BRIXUS365_API_KEY	required	—	Your Brixus365 API key — free key (bx_preview_…) or full account key (bx_live_…).
BRIXUS365_API_BASE_URL	optional	https://app.brixus365.com/api/v1	Override for staging or self-hosted Brixus365 environments.

Connect your client

Point your MCP client at the built entrypoint and pass the key in the environment.

Claude Code:

claude mcp add brixus365 -- env BRIXUS365_API_KEY=bx_live_your_key_here node /path/to/brixus365-mcp/dist/index.js

Claude Desktop, Cursor, Cline — add this under mcpServers (point command at node and the built file):

{
  "mcpServers": {
    "brixus365": {
      "command": "node",
      "args": ["/path/to/brixus365-mcp/dist/index.js"],
      "env": {
        "BRIXUS365_API_KEY": "bx_live_your_key_here"
      }
    }
  }
}

Replace /path/to/brixus365-mcp with the absolute path to where you cloned the repo. Restart your client — you should see the 16 Brixus365 tools appear.

Troubleshooting

Error code	Cause	Fix
missing_api_key / invalid_api_key	Env var not set or the value is wrong	Re-copy the key from Settings → API Keys in the Brixus365 app
Tools not found	The build path is wrong or the build step didn’t run	Confirm dist/index.js exists and the path in your config is absolute
rate_limit_exceeded	Too many calls per minute	Wait 60 seconds and retry

See also

• MCP Server Quickstart — the hosted (OAuth) setup
• Tools reference — all 16 tools