Skip to content
Agentmart
Submit a tool

Heuresis

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

Connector by ToremLabs · GitHub account verified by the MCP Registry

IndexedAGPL-3.0Local (stdio)
Write a review

Chalk Labs

Need help deploying Heuresis?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/toremlabs-heuresis

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
12 read · 17 write · 4 delete · 4 not yet classified
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 37

Read from the source code; the running server may list different tools.

Read 12 · Look things up without changing anything.

  • find_concepts
  • find_orphans
  • get_concept
  • get_project_graph
  • get_run
  • get_subtree
  • get_workspace_summary
  • list_concepts
  • list_edges
  • list_projects
  • list_recent_decisions
  • search_concepts

Write 17 · Create, change, send or run things.

  • add_concept
  • add_kref
  • add_to_idea
  • archive_concept
  • bulk_add_concepts
  • create_idea
  • create_project
  • link_concepts
  • rename_idea
  • run_operator
  • run_operator_and_commit
  • set_idea_members
Show 5 more tools
  • set_parent
  • set_standing
  • star_concept
  • update_concept
  • update_project

Delete 4 · Delete, drop, revoke or wipe things.

  • delete_idea
  • delete_project
  • remove_concept
  • remove_concepts

Not yet classified 4 · We could not tell from the name and description.

  • expand_concept
  • recolor_idea
  • unarchive_concept
  • validate_concept

Tools (37)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • add_concept

    Create a new concept (Node). If parentId is given, the concept becomes a CHILD of that concept and a partition edge is auto-created. If parentId is omitted, the concept attaches to the project root.

  • add_kref

    Convenience: create a k-ref (knowledge reference) edge from fromId → toId. Equivalent to link_concepts with kind=k-ref.

  • add_to_idea

    Add a single concept to an existing Idea (idempotent).

  • archive_concept

    Archive a concept (status=archived). Reversible via unarchive_concept.

  • bulk_add_concepts

    Create many concepts in a single atomic transaction. `items` is an array; each item carries label / description? / parentId? / projectId? / tags?. project_id is resolved per-item (explicit > inherited from parent > workspace solo project). Returns the created ids in input order.

  • create_idea

    Create a new Idea (a named grouping of concepts) with an optional color and optional starting node membership.

  • create_project

    Create a new Project (problem-with-direction) with a name and brief. Optional `direction`.

  • delete_idea

    Delete an Idea. Membership rows cascade via FK; the underlying concepts are untouched.

  • delete_project

    Delete a project. By default its concepts are LEFT behind as orphans (find them later with find_orphans). Pass deleteNodes:true to also hard-delete every concept in the project (each cascades its subtree) so no orphans are created.

  • expand_concept

    Recursive Branch — expand a concept by `breadth` children at each of `depth` levels (depth*breadth ≤ 60). Commits each level immediately so the webapp shows partial results as the run progresses. Optionally takes an `angle` hint that biases the underlying EXPLORE operator. Best when the anchor has few or no children yet; on a dense subtree consider `run_operator(family="explore")` so the operator can read existing children and propose complementary partitions.

  • find_concepts

    Find concepts by label/substring match. Returns up to k hits, each with id, label, status.

  • find_orphans

    Surface concepts no normal traversal reaches, scoped to your workspace: 'projectless' (in no project — typically left behind by delete_project) and 'danglingParent' (parent_id points at a deleted node). Read-only. Clean up with remove_concepts (delete) or set_parent (re-home).

  • get_concept

    One concept by id, optionally with its ancestry (parent chain), direct children, and idea memberships.

  • get_project_graph

    Every node + edge inside one project. Returns a graph the agent can reason over end-to-end. Use for project-wide questions.

  • get_run

    Fetch an async operator run by its runId. Returns { status: "running" | "done" | "error" }; when "done", the `result` field holds the operator output (candidates / committedIds). Waits up to ~8s for completion before returning, so a simple poll loop converges fast. run_operator / run_operator_and_commit / expand_concept hand back a runId whenever their work exceeds the ~8s fast-path window.

Show 22 more tools
  • get_subtree

    A node and its descendants up to a given depth. Pass the concept as `id` (or `rootId`). Use when the user asks "tell me about everything under X".

  • get_workspace_summary

    Counts of nodes / edges / projects / ideas + a one-line overview of each project and idea. Always start here when you don't know what's in the workspace.

  • link_concepts

    Create an edge between two concepts. kind is one of: 'k-ref' (knowledge reference), 'derived-from' (provenance link), 'semantic-adjacency' (sibling kinship). Partition (parent/child) edges are managed via add_concept / set_parent.

  • list_concepts

    List concepts in the workspace or one project. Returns id / label / status / parentId / tags up to `limit` entries (default 500). Use BEFORE making changes to learn what already exists.

  • list_edges

    List every edge in the workspace (or restricted to a project). Filter by kind: partition / k-ref / semantic-adjacency / derived-from / imported-from.

  • list_projects

    Every project in the workspace with brief, direction, lifecycle, and node count. Use this to figure out which project the user is asking about.

  • list_recent_decisions

    Nodes the user has explicitly resolved (validated, starred, or archived) recently. Use to surface "what did we conclude last week" without a full scan.

  • recolor_idea

    Change an Idea's color (any CSS color string).

  • remove_concept

    Hard-delete a concept and its descendants (walks the subtree via parent_id AND partition edges). Edges and project/idea memberships cascade via FK. Refuses to delete a project root node. For many at once, use remove_concepts.

  • remove_concepts

    Bulk hard-delete: delete many concepts in one call (each cascades its own subtree). Returns per-id results. Ids already swept up in another id's cascade come back ok:false (not-found) — expected, not fatal. Pair with find_orphans for cleanup.

  • rename_idea

    Rename an Idea.

  • run_operator

    Run an ASIT / TRIZ / Contradiction / Free / Combine / Explore operator against one concept (the anchor). Returns CANDIDATE concepts WITHOUT committing them — call `bulk_add_concepts` (or `run_operator_and_commit`) to persist. Use this when you want the agent to vet the candidates before writing. The anchor must already live in a project; the operator pulls in ancestry + validated knowledge in the same project to ground the prompt.

  • run_operator_and_commit

    Same as `run_operator`, but immediately writes every top-level candidate as a child of the anchor with a partition edge and a provenance row stamped origin='mcp'. Use when the agent is confident the candidates should land directly on the canvas (e.g. inside an autonomous expand loop). Children-of-children proposed in `partitions[].children` are NOT auto-committed — request them via a separate run.

  • search_concepts

    Substring search across concept labels, descriptions, partition attributes, rationale, and tags. Use this when the user mentions a concept by name and you don't have its id. (Semantic search is a Phase 19.5 enhancement.)

  • set_idea_members

    Replace an Idea's full membership with `nodeIds`. Reconciles the junction table: inserts missing pairs, deletes pairs no longer in the set. Returns added / removed counts.

  • set_parent

    Re-parent an existing concept: nodeId's parent becomes newParentId (or detached when null). Updates BOTH node.parent_id AND the partition edge so the canvas tree stays in sync.

  • set_standing

    Set a concept's STANDING — how known / proven the idea is in the wider world. `standing` ∈ 'novel' | 'emerging' | 'established' | 'unknown'. `rationale` is a one-sentence justification (saved as `standing_rationale`). Use this when classifying / judging novelty.

  • star_concept

    Toggle the starred flag on a concept (user-favorite marker).

  • unarchive_concept

    Revive a previously-archived concept (status=open). Idempotent on already-open nodes.

  • update_concept

    Update an existing concept's label, description, tags, partitionAttribute, rationale, or status. Only the fields provided are changed.

  • update_project

    Update a project's name / brief / direction / lifecycle. Only fields provided are changed.

  • validate_concept

    Mark a concept as validated (status=validated). Optionally also overwrite `rationale`. Idempotent on already-validated nodes.

Signals

Stars
0
Forks
0
Open issues
0
Weekly downloads
23
Last commit
Jun 6, 2026 (4 months ago)
Last release
Jun 2, 2026 (5 months ago)
Last package publish
Jun 6, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.ToremLabs/heuresis
Version
1.0.0-rc.9
Auth
No auth
Packages
npm @heuresis/mcp
License
AGPL-3.0
Repository
github.com/ToremLabs/heuresis-mcp
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registrygithub-graphql

More from ToremLabs

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get Heuresis running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying Heuresis?

CallGet help
Cite this page

Heuresis MCP server. Agent Mart. https://agentmart.dev/connectors/toremlabs-heuresis (last updated 2026-10-24)