The grid stays where it is in BitScale; what changes is who runs it. Discover the grid, ask what inputs it wants, run it, take the results — enrichment for a named company happens in the same thread as the outreach it feeds.
A server for a BitScale workspace, where the unit of work is a grid — an enrichment or research pipeline with defined inputs. It lists grids, describes their schema, hands back the exact input contract before anything runs, executes a grid in sync or async mode, and polls long runs by request_id.
- Workspace plan, credit balances, search limits and member counts
- All grids listed with search and pagination, returning their column definitions
- A grid's full schema — columns, settings and data sources
- A ready-to-use curl command and API contract for a grid, so the required inputs are known before it runs
- A grid run with input values, in sync or async mode
- The status of an async or timed-out run, polled by request_id
- The workspace API key rotated, which invalidates the current one
A BitScale account and its API key, set as BITSCALE_API_KEY. uv is installed once; uvx then fetches and runs the bitscale-mcp package on demand, so there is nothing to clone or pip install.
One command plus a key — uvx bitscale-mcp, then supply credentials