Heuresis
About
# @heuresis/mcp A Model Context Protocol (MCP) server that exposes a Heuresis workspace to any MCP-capable client (Claude Desktop, Claude Code, Cursor, Windsurf, custom agents). The server logs into the user's Heuresis account, talks to the same Supabase project the webapp talks to, and respects the same RLS. Webapp…
Details
- License
- AGPL-3.0
Explore
- 34 tools: 31 data tools and 3 operator tools
- Live sync via Supabase Realtime (no manual refresh)
- Device‑code login for personal machines
- Email/password authentication for headless/CI usage
- Respects workspace Row‑Level Security (RLS)
- All writes stamped with origin='mcp' for session audit
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
HeuresisCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
npm install -g @heuresis/mcp
npx -y @heuresis/mcp
> Package name vs. command name. The npm package is @heuresis/mcp; the
> command it installs is heuresis-mcp. A bare npx -y @heuresis/mcp (no
> subcommand) starts the MCP server fine, but npx @heuresis/mcp login can
> fail with heuresis-mcp: not found because npx derives the command name
> from the scope-stripped package name (mcp), which doesn't match. To run a
> subcommand reliably on every npm/OS, name the binary explicitly with -p:
>
>
> npx -y -p @heuresis/mcp heuresis-mcp login
> 34 tools total: 31 data tools against the cloud workspace, plus 3
operator tools that drive the same ideation operators the webapp uses.
Reads (10). get_workspace_summary, list_projects,
get_project_graph, list_concepts, list_edges, get_subtree,
get_concept, search_concepts, find_concepts,
list_recent_decisions. Most agent sessions start with
get_workspace_summary or list_projects.
Writes (21). Concepts: add_concept, update_concept,
bulk_add_concepts, set_parent, validate_concept, set_standing,
archive_concept, unarchive_concept, star_concept,
remove_concept. Edges: link_concepts, add_kref. Ideas:
create_idea, rename_idea, recolor_idea, set_idea_members,
add_to_idea, delete_idea. Projects: create_project,
update_project, delete_project. Every write stamps a row in
public.provenance with origin='mcp' so the webapp's session log
shows which surface made the change.
Operator runs (3). run_operator (generate candidates with
Branch / Matrix / ASIT / TRIZ / Combine / Free / Contradiction),
run_operator_and_commit (same, plus commit the result in one
round-trip), and expand_concept (recursive Branch, capped at depth ×
breadth ≤ 60).
Tool input shapes mirror their counterparts in the webapp's
src/agent/tools.ts, so an agent that uses both surfaces sees a
uniform contract.
Wave-shipping: find_in_files (in-browser embedding search) is in the
webapp but not yet on the MCP.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"heuresis": {
"heuresis": {
"command": "npx",
"args": [
"-y",
"@heuresis/mcp@latest"
]
}
}
}
}McpServers
{
"heuresis": {
"command": "npx",
"args": [
"-y",
"@heuresis/mcp@latest"
]
}
}A Model Context Protocol (MCP) server that exposes a Heuresis workspace
to any MCP-capable client (Claude Desktop, Claude Code, Cursor,
Windsurf, custom agents). The server logs into the user's Heuresis
account, talks to the same Supabase project the webapp talks to, and
respects the same RLS. Webapp and MCP are two front-ends to one cloud
workspace.
Current version: 1.0.0-rc.13.
Install
```bash
npm install -g @heuresis/mcp
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
