prepare_contextLABSCO SUMMARY
Built for headless and CI agents first, which shows in the token model and the audit log.
Scoped personal access tokens, a queryable agent activity log and an explicit confirm on deletes are the things you want when an agent is writing into your notes unattended. The context-first design is the other half: in strict mode a write is refused unless the same agent first built a context pack, which is a real guard against an agent editing a page it never read.
What it is
An open-source workspace — pages, databases, table, kanban and calendar views — with a first-class MCP server built in. Most editors connect with one-click OAuth; Windsurf, Continue, Antigravity, Cline and headless agents use a scoped personal access token.
What you get
- 21 tools split into read and write scopes, over stateless Streamable HTTP
- Reading:
search_workspace,list_workspace,get_page,get_pages,get_database_schema,query_database,list_members,query_audit_log - Change tracking:
get_changes_sincereturns a chronological feed from a timestamp or cursor, andget_related_pagesreturns parents, children, links, backlinks and database siblings - Writing:
create_page,update_page,bulk_update_pages,move_item, anddelete_pagewhich requires an explicit confirm - Databases:
create_database,update_database_schema, and view management throughcreate_database_view,update_database_viewanddelete_database_view prepare_contextbuilds a token-budgeted context pack ranked by relevance, freshness and trust, and returns a run id the stricter policy mode requires before any write
Requirements
A Remnus workspace. The configurations on this page connect to the hosted one at remnus.com. To self-host instead, clone and run with npm after filling in AUTH_SECRET and OAuth credentials, or bring it up with Docker Compose, which persists the SQLite database in a volume; the first account to sign up becomes admin. Claude Code, Cursor, VS Code, Codex and Zed connect over OAuth with nothing to paste, and so does Claude Desktop through the mcp-remote bridge. Windsurf, Continue, Antigravity and Cline do not run that flow yet, so they, like CI and headless agents, send a scoped read or write token as a bearer header; a workspace owner mints it under AI Agents → Connect editor → Advanced. Licensed AGPL-3.0.
Setup effort
One command — claude mcp add --transport http --scope user remnus https://www.remnus.com/api/mcp
USE CASES
Giving a coding agent the project context before it starts
Build one token-budgeted context pack for the task rather than dumping the whole workspace into the prompt.
Catching up on what changed overnight
Pull the chronological feed since your last cursor instead of re-reading the workspace.
Filing a batch of results into a database
Read the schema first, then write the rows in one call instead of one page at a time.
Tracing what an agent did in your workspace
Filter the activity log by agent and time, and see every mutation it made.
Finding everything connected to one page
Pull its parent, children, outgoing links, backlinks and database siblings in a single call.
21 tools
Listed in project docs. Your client may show a different list.
search_workspacelist_workspaceget_pageget_pagesget_database_schemaquery_databaselist_membersquery_audit_logget_changes_sinceget_related_pagescreate_pageupdate_pagebulk_update_pagesdelete_pagemove_itemcreate_databaseupdate_database_schemacreate_database_viewupdate_database_viewdelete_database_viewBEFORE YOU INSTALL
What to know first
Tools you get
21 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Server setup
claude mcp add
Claude Code
claude mcp add --transport http --scope user remnus https://www.remnus.com/api/mcpHosted endpoint
https://www.remnus.com/api/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Claude Desktop
{
"mcpServers": {
"remnus": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://www.remnus.com/api/mcp"
]
}
}
}Cursor
{
"mcpServers": {
"remnus": {
"url": "https://www.remnus.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}<YOUR_TOKEN> is a token. Mint one in Remnus under AI Agents → Connect editor → Advanced (workspace owners only; pick the workspace and a read or write scope, and copy the token, which is shown once). Cursor can also sign in over OAuth with no token: pick Cursor in that same Connect editor panel for a one-click link.
Codex
codex mcp add remnus --url https://www.remnus.com/api/mcp
codex mcp login remnusWindsurf
{
"mcpServers": {
"remnus": {
"serverUrl": "https://www.remnus.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Windsurf does not run the OAuth flow yet, so it needs a token: mint one in Remnus under AI Agents → Connect editor → Advanced (workspace owners only; pick the workspace and a read or write scope, and copy the token, which is shown once).
Continue
{
"mcpServers": {
"remnus": {
"url": "https://www.remnus.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Continue does not run the OAuth flow yet, so it needs a token: mint one in Remnus under AI Agents → Connect editor → Advanced (workspace owners only; pick the workspace and a read or write scope, and copy the token, which is shown once).
Antigravity
{
"mcpServers": {
"remnus": {
"serverUrl": "https://www.remnus.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Antigravity does not run the OAuth flow yet, so it needs a token: mint one in Remnus under AI Agents → Connect editor → Advanced (workspace owners only; pick the workspace and a read or write scope, and copy the token, which is shown once).
Cline
{
"mcpServers": {
"remnus": {
"type": "streamableHttp",
"url": "https://www.remnus.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Cline does not run the OAuth flow yet, so it needs a token: mint one in Remnus under AI Agents → Connect editor → Advanced (workspace owners only; pick the workspace and a read or write scope, and copy the token, which is shown once).
Zed
{
"context_servers": {
"remnus": {
"url": "https://www.remnus.com/api/mcp"
}
}
}Claude Desktop — Smithery
npx -y smithery@latest mcp add ranorkk/remnus --client claudeAny MCP client
{
"mcpServers": {
"remnus": {
"url": "https://www.remnus.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}If your client runs the MCP OAuth flow, leave out the headers and approve the consent screen on first connect. Otherwise mint a token in Remnus under AI Agents → Connect editor → Advanced (workspace owners only; pick the workspace and a read or write scope, and copy the token, which is shown once).