Lystbot vs Remnus
A side-by-side look at the Lystbot and Remnus MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Lystbot for workplace & productivity work as a local process; choose Remnus for workplace & productivity over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Lystbot when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_lists, get_list, create_list.
Choose Remnus when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
AUTH_SECRET. - You want tools like
prepare_context, search_workspace, list_workspace.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 57/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | AUTH_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 72 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 26 | 28 |
| Full listing | View Lystbot | View Remnus |
Tools & capabilities
Lystbot tools 26
list_listsGet all your listsget_listGet a specific list with itemscreate_listCreate a new listdelete_listDelete a listadd_itemsAdd natural strings or structured `{text, quantity?, unit?}` itemscheck_itemCheck off an itemuncheck_itemUncheck an itemremove_itemRemove an item from a listclear_checkedRemove all checked (completed) items from a listshare_listGenerate a share code for a listjoin_listJoin a shared list via codelist_categoriesList categories for a list- +14 more on the listing page
Remnus tools 28
prepare_contextBuild Context Pack v2 (BM25 + OKF metadata + graph) and return a short-lived `contextRunIdsearch_workspaceFull-text search across pages and databaseslist_workspaceList sidebar items with paginationget_pageGet a page, database row or dashboard (as its block spec) by IDget_pagesGet multiple pages/rows by ID in one call (batch `get_page`)get_database_schemaGet column schema of a databasequery_databaseQuery rows with filters and paginationlist_membersList workspace members with rolesquery_audit_logFiltered agent activity logget_changes_sinceCompact, chronological feed of what changed since a timestamp or cursorget_related_pagesA page's parent, children, outgoing links, backlinks, database siblings and source files — or, given a file path, the pages that rest on itget_statusCheck this connection: workspace, scope, when the token expires and what to do about it- +16 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Lystbot
{
"mcpServers": {
"lystbot": {
"command": "npx",
"args": [
"-y",
"lystbot"
]
}
}
}
Remnus
{
"mcpServers": {
"remnus": {
"url": "https://your-instance.com/api/mcp"
}
}
}
Frequently asked questions
Lystbot is categorized under Workplace & Productivity and uses a local stdio subprocess. Remnus belongs to Workplace & Productivity and uses a remote HTTP/SSE transport. Pick Lystbot for workplace & productivity work and Remnus for workplace & productivity.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Lystbot has no declared pricing — check the project's own site. Remnus has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add lystbot and remnus as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Lystbot has a quality signal of 57/100 (Good) with 1 views, 0 installs and 4 GitHub stars. Remnus has 56/100 (Good) with 1 views, 0 installs and 72 GitHub stars.