
Heuresis
io.github.ToremLabsPublished by GitHub account ToremLabsv1.0.0-rc.9Updated Oct 24, 2026
Read & write your Heuresis idea graph and run TRIZ/C-K/ASIT operators from your AI assistant.
Overview
Connects an AI assistant to a Heuresis idea graph so it can read, search and edit concepts, edges, ideas and projects, and run ideation operators.
- What you can do
- Read the workspace: summary, projects, project graphs, concepts, edges, subtrees, recent decisions, plus concept search and lookup
- Write concepts: add, update, bulk add, set parent, validate, set standing, archive, unarchive, star, remove
- Manage edges, ideas and projects: link concepts, add krefs, create/rename/recolor/delete ideas, set idea members, create/update/delete projects
- Run ideation operators (Branch, Matrix, ASIT, TRIZ, Combine, Free, Contradiction), optionally committing results, and recursively expand a concept
- Receive live sync notifications when workspace rows change, unless disabled
- When to use it
- Useful when your thinking or product work lives in a Heuresis workspace and you want an assistant to browse it, keep it updated, or generate and commit new idea candidates without switching to the webapp.
- Requirements
- Runs locally via npm package @heuresis/mcp (Node.js, npx). Needs a Heuresis account: either device pairing via the heuresis-mcp login command, which writes credentials to ~/.heuresis/credentials.json, or headless sign-in with HEURESIS_EMAIL, HEURESIS_PASSWORD and HEURESIS_ANON_KEY (optional HEURESIS_SUPABASE_URL). Network access to the Heuresis Supabase backend. A deprecated read-only mode uses HEURESIS_SNAPSHOT pointing at a JSON export.
Installation
In SourceWeft
- Open Heuresis in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@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 and MCP are two front-ends to one cloud workspace.
Current version: 1.0.0-rc.13.
Install
Package name vs. command name. The npm package is
@heuresis/mcp; the command it installs isheuresis-mcp. A barenpx -y @heuresis/mcp(no subcommand) starts the MCP server fine, butnpx @heuresis/mcp logincan fail withheuresis-mcp: not foundbecause 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:
Quickstart
1. Link this machine to your Heuresis account
The CLI prints a device code and a one-click URL of the form
https://heuresis.app/device?code=XXXX-XXXX. Open it in your browser,
sign in if you aren't already, and confirm the device. The CLI polls
in the background and writes credentials to
~/.heuresis/credentials.json (chmod 600 on POSIX) the moment you
confirm. Subsequent runs of the MCP are silent.
The login flow rides three Supabase Edge Functions:
mcp-device-init, mcp-device-grant, and mcp-device-poll.
To unlink a machine: npx -y -p @heuresis/mcp heuresis-mcp logout, or open
Settings ▸ Connected devices in the webapp to revoke remotely.
npx -y -p @heuresis/mcp heuresis-mcp whoami confirms which account a machine
is currently linked to.
2. Point your MCP client at it
Claude Desktop. Edit
~/Library/Application Support/Claude/claude_desktop_config.json on
macOS, or %APPDATA%/Claude/claude_desktop_config.json on Windows:
Claude Code / Cursor / Windsurf. Drop a .mcp.json in the
workspace root:
Restart the client. The Heuresis tools appear in the tool menu.
3. CLI subcommands
Headless mode (CI, cloud agents, disposable containers)
Device pairing writes a refresh token to disk. That works great on a personal machine, but it does not survive disposable/ephemeral environments (CI runners, cloud agent containers, "Claude Code on the web"): the filesystem is wiped between runs, and a Supabase refresh token is single-use under rotation — so a token baked into config dies after the first session.
For those environments, skip pairing and let the server sign in fresh on every boot from your account email + password (a password is not consumed on use, so it works forever with no re-pairing). Set three env vars:
When HEURESIS_EMAIL + HEURESIS_PASSWORD are present they take precedence
over any credentials.json, and the MCP server authenticates per boot — no
device link required. Requirements:
- Email + password sign-in must be enabled for the Supabase project, and the account must have a password set (passwordless / magic-link-only accounts need a password added first).
- Treat
HEURESIS_PASSWORDas a secret. Prefer a dedicated account if your environment can only expose env vars that are visible to its users.
Live sync
When the MCP boots in cloud mode it subscribes to the workspace over
Supabase Realtime and notifies the client whenever a nodes, edges,
projects, or ideas row changes. Edits made in the webapp show up
in the agent's view without a manual refresh, and writes from one
MCP-connected client reach any other connected client the same way.
Pass --no-realtime to disable the subscription (useful if the
chatter is noisy or the client logs every notification). The
preference is saved to ~/.heuresis/config.json so the flag only
needs to be passed once.
Tools
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.
Legacy snapshot mode (deprecated)
The original read-only snapshot reader still works as a fallback while
users migrate to cloud auth. With no ~/.heuresis/credentials.json
and the HEURESIS_SNAPSHOT env var set, the server reads a JSON
export from disk and exposes the original read-only tool set
(get_workspace_summary, list_projects, search_concepts,
get_concept, get_subtree, get_project_graph,
list_recent_decisions).
This path is deprecated and will be removed in a later release. It is here so existing setups keep working through the migration to cloud auth.
License
AGPL-3.0-or-later.
Source: README.md at commit 3ac8ac5
Tools
0Version history
1- v1.0.0-rc.9LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts