Spiderbrain MCP Server

Spiderbrain is an MCP integration. Deterministic context layer for your codebase: change impact, blast radius, answers with receipts.

Hosted connection

The registry lists a streamable-http connection at https://mcp.spiderbrain.ai/mcp. The endpoint declares these request headers: Authorization.

Packages and local setup

The published npm package is spiderbrain, version 0.2.3. Its declared MCP transport is stdio.

The package declares SPIDERBRAIN_ROOT (required): Absolute path to the repository to serve, which must already contain a committed .spiderbrain/ folder. Set this: an MCP client's working directory is usually not your repository, and without it the server serves the working directory and reports that no understanding layer was found. Equivalent to passing --root.; SPIDERBRAIN_API_KEY: Optional. Enables the cloud why-layer used by the sb_ask tool. The structural tools work offline without it.; SPIDERBRAIN_REGISTRY: Optional. Base URL of the public brain registry this server consults on the first tool call when the repository has no committed .spiderbrain/ folder. Defaults to https://spiderbrain.ai/registry..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.2.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.