Bitscale MCP Server

Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) and add:. The bitscale mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

Everything the assistant can do here goes through one of these:

• get_workspace_details — Get workspace plan, credit balances, search limits, and member counts
• list_grids — List all grids with optional search & pagination, returns column definitions
• get_grid_details — Get a grid's full schema — columns, settings, and data sources
• get_grid_curl — Get a ready-to-use curl command and API contract for running a grid — call this first to discover required inputs
• run_grid — Run a grid by providing input values, supports sync and async modes
• get_run_status — Poll the status of an async or timed-out grid run by request_id
• rotate_api_key — Rotate the workspace API key (irreversible, invalidates current key)
• Endpoint — Method

Configuration

You will need one environment variable: BITSCALE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the bitscale mcp mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Bitscale MCP's toolset — get_workspace_details, list_grids, get_grid_details and 5 more — is a fair guide to whether it matches your workflow. It is maintained by featherflow; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.