Remnus: a workspace with MCP for agents
Remnus
An open-source workspace with pages, databases and kanban where Claude and Cursor read and write through MCP
- 75 ★ on the repository
- Last commit
Extended access
Why this level
- Write tools create, change and delete workspace pages and database rows
- An access token opens the whole workspace within its scope
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/remnusDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Write tools create, change and delete workspace pages and database rows
- An access token opens the whole workspace within its scope
This is third-party code. Review the repository files before installing.
What it does
Remnus is a workspace for people and AI agents built around MCP. Markdown pages with nested subpages, databases with table, kanban and calendar views, and dashboards are open to an agent through a built-in MCP server: 28 tools, 7 resources and 7 prompts over stateless Streamable HTTP. Editors connect with one click through OAuth 2.1 with PKCE and dynamic client registration, while CI and headless agents get personal tokens with read or write scopes. The `prepare_context` tool builds a context pack for a task: pages are ranked by BM25, metadata, links and freshness. Strict mode requires a short-lived `contextRunId` before any MCP edit. The workspace is installed on your own server from source or with Docker Compose, and data lives in SQLite. There are shared workspaces with owner, member and viewer roles, a Tauri desktop app and Capacitor mobile shells.
Who it is for. Teams that want to keep tasks and documents in a self-hosted workspace that a coding agent can handle just as freely.
Good fit when
- Tasks run on a kanban board and an agent should pick up and close cards on its own
- You need a shared context source for Claude Code, Cursor and Codex with BM25 search
- A CI pipeline must write release status to a page with a write-scoped token
- You want to replace cloud Notion with your own hosting that has MCP out of the box
Not a fit when
- You only need agent access to an existing Notion: separate servers exist for that
- You have no server for Next.js and SQLite: the workspace is installed by you
- You need control of local files, a shell or Git: the Remnus MCP server does not do that
Example request
Find the Remnus pages about release 2.1, build a context pack from them and move the Update docs card to the In progress column.MCP
- Transport
- http
- Authentication
- OAuth
Environment variables
AUTH_SECRETrequired, secret- Session signing secret of a self-hosted instance
Limitations
Remnus is a whole application that includes the server: it must be deployed (`npm run dev` or `docker compose up -d`) and `.env` filled with `AUTH_SECRET` and OAuth credentials. The first registered user becomes the admin. The MCP address depends on your instance: `https://your-host/api/mcp`.
Tokens have read and write scopes, but write tools change and delete workspace content. Strict mode with `contextRunId` guards edits through MCP, while local files, a shell and Git are outside the server control. For those the repository ships `AGENTS.md` and `CLAUDE.md` snippets.
How to disable. Revoke the tokens in the AI Agents panel, remove the server from client settings and stop the container (`docker compose down`).
FAQ
How do I connect Remnus to Claude Code or Cursor?
Open the AI Agents panel, click Connect editor and pick your editor. Or run `npx -y smithery@latest mcp add ranorkk/remnus --client claude`.
Is a token needed to connect?
Not for editors: approval in OAuth 2.1 is enough. A read or write scoped token is for CI and headless agents.
What does prepare_context do?
It builds a Context Pack v2 for the task from pages ranked by BM25, metadata, links and freshness.
Where is the data stored?
In SQLite on your server: Docker Compose keeps the database in a volume.
Which editors does Remnus support?
Cursor, VS Code, Claude Code, Codex, Windsurf and others: the Connect editor wizard shows steps for each.
Discussion
No questions or reviews yet.
Related
MCP serversThe MCP endpoint of a Salt workspace on your server: an agent creates pages, databases and comments with a person rights.
An MCP server and Mac app that keeps one local index of repos, agent sessions and tickets, with semantic search and work threads
A self-hosted task manager for human and agent collaboration through MCP
An agent searches, reads and writes a Roam Research graph through the desktop app's local API, with a CLI and a syntax skill
A macOS menu bar app writes the text of your focused windows into markdown, and its MCP server serves that record to agents
A team wiki living in Git with a 51-tool MCP server: agents read and edit pages, tables and boards.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Remnus: a workspace with MCP for agents (this card) | no | OAuth | 75 | |
| notion-skills | no | 79 | skills for cloud Notion; Remnus itself serves as a workspace with MCP | |
| Anytype API skill | no | 115 | works with local Anytype through its API; Remnus gives a whole workspace with OAuth and roles |
README in short
The README presents Remnus as an open workspace for people and agents, describes features, self-hosted installation with Node and Docker Compose, editor connection and a table of MCP tools by access scope.