Bitburner MCP Server
MCP server and local HTTP API bridge for the Bitburner Remote API.
Features
- WebSocket listener for Bitburner Remote API
- REST API for remote method calls and file helpers
- MCP stdio server with one tool per remote API method
- MCP Streamable HTTP server
- Local dashboard for connection status and events
Requirements
- Node.js 20+
- Bitburner Remote API configured to connect to this server:
- Host:
localhost - Port:
12525 - TLS/WSS: disabled (
ws)
- Host:
Install
npm install
npm run build
Run
# REST API + dashboard
npm run start:api
# MCP stdio transport
npm run start:mcp
# MCP Streamable HTTP transport
npm run start:mcp:http
MCP Client Setup
For stdio clients, point your MCP config to:
dist/mcp-server.js
For Streamable HTTP clients, use:
http://localhost:3003/mcp
Environment Variables
BB_WS_HOSTdefault:0.0.0.0BB_WS_PORTdefault:12525BB_API_PORTdefault:3001BB_API_BASE_URLdefault:http://localhost:3001BB_DASHBOARD_HOSTdefault:127.0.0.1BB_DASHBOARD_PORTdefault:3002BB_MCP_HTTP_HOSTdefault:127.0.0.1BB_MCP_HTTP_PORTdefault:3003BB_MCP_HTTP_PATHdefault:/mcpBB_API_TOKENoptional bearer token for API and MCP endpoints
API Overview
Health and dashboard:
GET /healthGET /dashboardGET /api/dashboard/eventsGET /api/dashboard/statusGET /api/docs/remote-apiGET /api/docs/globals
Remote API proxy endpoints:
POST /api/remote/pushFilePOST /api/remote/getFilePOST /api/remote/deleteFilePOST /api/remote/getFileNamesPOST /api/remote/getAllFilesPOST /api/remote/calculateRamPOST /api/remote/getDefinitionFilePOST /api/remote/getSaveFilePOST /api/remote/getAllServers
Convenience file endpoints:
GET /api/file/:filename?server=homePOST /api/file/writePOST /api/file/appendPOST /api/file/uploadDELETE /api/file/:filename?server=homeGET /api/files?server=home&path=.
Docs
docs/ARCHITECTURE.mddocs/MCP_AI_GUIDE.mddocs/REMOTE_API_TOOLS.md