Heuresis

Name: Heuresis
Author: ToremLabs

by ToremLabsversion 1.0.0-rc.9i★ –iRuns on your computer

Registry nameio.github.ToremLabs/heuresis

Install

Overview

Description from the maker (original English)

Read & write your Heuresis idea graph and run TRIZ/C-K/ASIT operators from your AI assistant.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "heuresis": {
      "command": "npx",
      "args": [
        "-y",
        "@heuresis/mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add heuresis -- npx -y @heuresis/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "heuresis": {
      "command": "npx",
      "args": [
        "-y",
        "@heuresis/mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "heuresis": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@heuresis/mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account ToremLabs, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32583 servers in this category
Published to the registry more recently than 11% of the other 32583 servers in this category
Basic checks equal to or better than 100% of the other 32583 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Heuresis safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0-rc.9) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, sync. labs

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

sync. labs

by synchronicity-labs

Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@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

npm install -g @heuresis/mcp

or on demand without installing:

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:

`bash

npx -y -p @heuresis/mcp heuresis-mcp login

`

Quickstart

1. Link this machine to your Heuresis account

npx -y -p @heuresis/mcp heuresis-mcp login

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:

"mcpServers": { "heuresis": { "command": "npx", "args": ["-y", "@heuresis/mcp"] } } }

Claude Code / Cursor / Windsurf. Drop a .mcp.json in the workspace root:

"mcpServers": { "heuresis": { "command": "npx", "args": ["-y", "@heuresis/mcp"] } } }

Restart the client. The Heuresis tools appear in the tool menu.

3. CLI subcommands

npx -y -p @heuresis/mcp heuresis-mcp whoami   # show the linked account + device

npx -y -p @heuresis/mcp heuresis-mcp logout # delete the credentials file npx -y -p @heuresis/mcp heuresis-mcp --help # all options npx -y @heuresis/mcp --no-realtime # boot the server with live sync off (persisted) npx -y @heuresis/mcp --realtime # re-enable live sync

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:

HEURESIS_EMAIL=you@example.com          # your Heuresis account email

HEURESIS_PASSWORD=your-account-password # secret — store it in a secrets manager HEURESIS_ANON_KEY=sb_publishable_... # project anon/publishable key (public, not a secret)

optional: HEURESIS_SUPABASE_URL=... # defaults to the production project

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_PASSWORD as 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).

export HEURESIS_SNAPSHOT="/absolute/path/to/your-export.json"

npx @heuresis/mcp

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.

Heuresis

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

sync. labs

README from the maker

@heuresis/mcp

Install

or on demand without installing:

Quickstart

1. Link this machine to your Heuresis account

2. Point your MCP client at it

3. CLI subcommands

Headless mode (CI, cloud agents, disposable containers)

optional: HEURESIS_SUPABASE_URL=... # defaults to the production project

Live sync

Tools

Legacy snapshot mode (deprecated)

License