Rootr

What the Rootr MCP server does

The Rootr MCP server gives an AI agent access to a Rootr workspace while applying the permissions associated with the selected account or workspace credentials. Rootr stores team documents, structured records, and other workspace resources; the MCP interface lets an agent inspect, search, create, update, and query those resources.

The package supports two connection models. Rootr hosts a remote endpoint at https://rootr.io/mcp for clients that support MCP connectors. Alternatively, the rootr-cli package starts a local stdio server with rootr mcp. The local option is useful for command-line agents and environments where credentials and process startup are managed in an MCP client configuration.

How it works

The CLI communicates with the Rootr REST API using a workspace identifier and API key. A path beginning with / is resolved as a workspace path; other targets are treated as node IDs. Tools that accept a workspace can use the configured workspace when one is not supplied explicitly.

Document changes include controls for concurrent editing. rootr_append adds content without rewriting the document, while rootr_write can use an ETag with --if-match. The edit operation rejects missing or ambiguous matches unless replacement of all matches is requested. Non-successful API responses are reported on stderr, with distinct handling for authentication failures, conflicts, and stale document versions.

Setup and configuration

The Rootr MCP server requires Node.js 18 or newer for the local installation. Install the package globally with npm install -g rootr-cli, then configure an API key and workspace:

rootr config --api-key rootr_xxxx --workspace ws_xxx
rootr mcp

Configuration can also come from ROOTR_API_KEY, ROOTR_WORKSPACE, and ROOTR_BASE_URL. Environment variables take precedence over ~/.rootr/config.json; the default API base URL is https://rootr.io/api/v1. The configuration file is created with restrictive permissions, and displayed API keys are masked.

Workspace keys cover most workspace operations. Account keys are needed for account-level actions such as creating a workspace with the required workspaces:create scope.

Tools and capabilities

The Rootr MCP server exposes more than 80 tools across these areas:

• Documents, search, versions, deletion, duplication, publishing, and comments
• Workspaces and workspace scaffolding
• Databases, spreadsheets, whiteboards, and forms
• CRM companies, contacts, deals, activities, tasks, and CSV import
• Presentations and slide operations
• LOG datastores and issue trackers
• Webhooks and GraphRAG questions with citations
• Image generation and background removal

The standalone CLI also provides ls, read, write, append, edit, search, ask, ws, and config commands.

Limitations and notes

The local server is a pure ESM Node.js application with no build step. API scope matters: using a workspace key for an account-only operation returns a permission error. Agents should prefer append and edit for safer document updates; full replacement through write can overwrite content. The hosted connector uses OAuth and workspace selection, while the local process requires API-key configuration.