Dependency-graph MCP server. Tells Claude/Cursor what breaks if you change X. Provenance guards.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
ThaskThask it, done. | ![]() |
The dependency graph layer for AI-assisted development.
Map what depends on what, then let Claude Code / Cursor / Codex query it through MCP β with provenance guards so agents can't silently land hallucinated descriptions on your graph.
v0.6.0 β Knowledge OS Foundation. Thask now models the full project memory, not just execution deps: 4 new first-class entity types (
REQUIREMENT,DECISION,EXPERIMENT,PERSON) alongside the original 7, 9 new relationship verbs (realizes,supersedes,decided,produced,owns,reported,drives,tests,conflicts), a domainlifecycleStateorthogonal tostatus, and per-node comments, attachments, and canonical project tags. Same 25 MCP tools β the new capabilities ride on wider enums plus two additive fields.
| Without Thask | With Thask | |
|---|---|---|
| You ask | "Refactor this payment function." | "Refactor this payment function." |
| Agent sees | Just the open file. | The file plus every node that depends_on it across your graph. |
| Agent answers | Plausible code. Three downstream flows quietly break. | "This change touches 3 flows and 2 UIs β I will update them together, or stop and ask." |
| Description drift | Agent rewrites the "why" prose on confidence, you read it, the next agent treats it as ground truth. | Agent keys default to blocking semantic writes. They propose to a queue; a human approves. Source-of-record stays human. |
Every change is recorded with 6-dimension provenance (actor, channel, agent model, mutation kind, trigger, evidence) so the next agent knows what to trust and what to re-derive from code.
Spreadsheets lose context. Linear issue trackers hide relationships. Thask maps your product as a living graph β so you can see what breaks before it breaks.
AI-NativeShip with |
Graph-first ThinkingEvery flow, task, and bug is a node. Every dependency is a visible edge. No more hidden connections. |
Impact at a GlanceOne click shows which nodes are affected by recent changes. Catch regressions before they ship. |
Self-hosted
|
Drag-and-drop nodes with 11 types β Flow, Branch, Task, Bug, API, UI, Group, plus the v0.6.0 Knowledge OS entities Requirement, Decision, Experiment, and Person. Connect them by hovering and dragging the edge handle. Auto-layout with the fCOSE force-directed algorithm.
Toggle Impact Mode to instantly highlight changed nodes and their downstream dependencies. Dimmed nodes are safe; glowing nodes need attention.
Organize related nodes into collapsible groups. Drag nodes in and out. Resize groups freely. Double-click to collapse with a child count badge.
Track every node as PASS / FAIL / IN_PROGRESS / BLOCKED with color-coded visuals. Filter the graph by node type or status to focus on what matters.
Slide-out panel with full editing β title, description (with markdown rendering), type, status, tags, connected nodes, and a complete change history audit log.
Fourteen edge types with distinct colors: the base five (depends_on, blocks, related, parent_child, triggers) plus the v0.6.0 Knowledge OS verbs (realizes, conflicts, drives, supersedes, tests, produced, owns, decided, reported). Every edge also carries a JSONB metadata bag β supersedes records {reason}, produced records {outcome_summary}, etc. Draggable waypoints for edge routing. Click any edge to change its type or delete it.
Full CLI for terminal workflows (npm install -g @thask-org/cli). 25 MCP tools for AI agent integration β Claude Code and Cursor can query and modify your graph directly. One-step browser login (thask login), in-place upgrades (thask self-update). CLI Reference Β· MCP Guide
Every API key is classified as user_interactive, agent, or service with seven independent permission flags. Agent keys default to blocking semantic writes (description, "why" content) and node verification β so a hallucinated description can't silently land on your graph. Every write records 6-dimension provenance (actor, channel, agent model, mutation kind, trigger, evidence) to a single audit_log table. DATABASE.md > Provenance
Agents wanting to revise a description post to node_suggestions and a human approves before the change lands. The deciding human becomes the author of record β the agent is credited only in audit metadata. Server-enforced: accepted decisions require a user_interactive actor regardless of permission flags.
Three endpoints cut N round-trips down to one β node.batch_update (up to 200), edge.batch_create / edge.batch_delete (up to 500). Atomic on permission / cycle failure; per-item skip reasons in skipped[]; HTTP 207 Multi-Status when any item skips. Saves substantial agent context (1 call vs N).
Every CLI invocation, MCP tool call, and HTTP response appends a single JSONL line to ~/.thask/events.jsonl β on your machine only, no upload. Inspect with thask usage (30-day summary, p50/p95 latency, top commands), thask reflog / thask history (recent events, full-text search), or tail -f the file directly. Raw bodies are opt-in (thask telemetry config set capture_payloads true); the default captures only metadata. Tokens, URL credentials, JWT and cookies are masked at write time.
Scan Go codebases to auto-generate dependency graphs. thask scan --path . parses go.mod and imports, creating nodes and edges automatically. Extensible via plugin system.
Detect dependency cycles (Tarjan DFS) and find the critical path (longest depends_on/blocks chain). Toggle Analysis Mode (Shift+A) to visualize cycles and critical path on the canvas.
Versioned REST API at /api/v1/ for third-party integrations. OpenAPI 3.1 spec, interactive Scalar docs, structured error responses, and idempotency support. API Guide
Four team roles β Owner, Admin, Member, Viewer β with granular permissions. Per-project roles (Editor, Viewer). API key authentication for programmatic access.
Share projects via link with viewer or editor access. Manage per-project members with granular roles. Public shared views support realtime collaboration. Embeddable graph views and OG image generation.
Start new projects from built-in templates: API Flow, Microservice Map, Sprint Board. One-click apply from the project creation flow.
Light and dark mode with system detection. Persisted per user. Design system uses CSS variables throughout.
Thask has two parts:
| Server (self-hosted) | CLI (local) | |
|---|---|---|
| What | Web UI + REST API + PostgreSQL | Terminal commands + MCP server |
| Install | docker compose up | npm install -g @thask-org/cli |
| Used by | Humans (browser) | Humans (terminal) + AI agents (MCP) |
| Data | Stores everything (nodes, edges, users) | Reads/writes via server API |
The server runs your graph database and web UI. The CLI talks to the server's API β you can create nodes, run scans, and analyze graphs from the terminal. AI agents (Claude Code, Cursor) use the CLI's built-in MCP server.
Get Thask working with Claude Code in 2 minutes:
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/thask)<a href="https://allmcps.com/mcp/thask"><img src="https://allmcps.com/api/badge/thask?style=directory" alt="Thask on AllMCPs" /></a>