MCP as the primary assistant workflow
For many users, the MCP-style workflow may be the main way they use Graphode day to day. They can keep designing through a familiar AI assistant while the assistant uses Graphode tools to fetch context, report progress, create checkpoints and return evidence.
Graphode does not need to be the place where every sentence is typed. It becomes the stable control plane underneath the conversation.
- Work through familiar assistants
- Fetch scoped context
- Report progress
- Create checkpoints
Task execution tools
The execution loop covers the operational path: compile task context, fetch detail, report progress, create checkpoint, register artifact, raise gap, check drift, evaluate acceptance and resume.
This is the part that makes agent work controlled instead of a long uninspectable chat.
- graphode.context.compile_task
- graphode.context.get_detail
- graphode.task.get
- graphode.task.report_progress
- graphode.task.report_checkpoint
- graphode.task.register_artifact
- graphode.task.report_gap
- graphode.execution.check_drift
- graphode.execution.evaluate_acceptance
- graphode.resume.get_state
- graphode.resume.update_state
GraphoTree tools
MCP-style tooling can also expose GraphoTree read and draft-editing tools where authorized. This lets assistants help populate and refine the model without directly mutating published reality.
Draft-first control keeps agent changes proposed, reviewed and published through safeguards rather than silently changing the accepted model.
- graphode.graphotrees.list
- graphode.graphotree.get
- graphode.graphotree.versions.query
- graphode.graphotree.nodes.query
- graphode.graphotree.context.compile
- graphode.graphotree.draft.ensure
- graphode.graphotree.node.create
- graphode.graphotree.node.update
- graphode.graphotree.node.delete_from_draft
- graphode.graphotree.relation.create
- graphode.graphotree.relation.update
- graphode.graphotree.tree_membership.upsert
Review and publish tools
Candidate review, merge request and draft publish tools let Graphode keep model changes auditable. They also make it possible for agents to contribute structure while humans retain control.
- graphode.graphotree.candidate_review.create
- graphode.graphotree.merge_request.create
- graphode.graphotree.merge_request.resolve
- graphode.graphotree.draft.publish
Availability wording
Exact MCP tool availability may vary during early access. Tool descriptions use planned, designed to, where supported or available when verified owner routes, schemas, claims and audit behavior are in place.
- Claim-filtered discovery
- Authorization checks
- Owner-service policy
- Audit requirements
Session and current scope tools
These tools are product-direction public catalog entries for opening a Graphode session, resolving authorized scope and reading workspace or project detail where owner routes, schemas, claims and audit behavior are verified.
- graphode.session.open
- graphode.context.current
- graphode.workspaces.list
- graphode.workspace.get
- graphode.projects.list
- graphode.project.get
- graphode.project.create
Task execution loop tools
The execution loop lets compatible assistants compile scoped context, fetch details, report progress, create checkpoints, register artifacts, raise gaps, check drift, evaluate acceptance and resume from the last meaningful state where supported.
- graphode.context.compile_task
- graphode.context.get_detail
- graphode.task.get
- graphode.task.report_progress
- graphode.task.report_checkpoint
- graphode.task.register_artifact
- graphode.task.report_gap
- graphode.execution.check_drift
- graphode.execution.evaluate_acceptance
- graphode.resume.get_state
- graphode.resume.update_state
Graphode task control tools
Task control tools are designed to query, create, update, pause or take over tasks through authorized flows instead of leaving long-running work trapped in an uninspectable chat session.
- graphode.tasks.query
- graphode.task.create
- graphode.task.update
- graphode.task.pause
- graphode.task.takeover
GraphoTree read and context tools
Read and context tools let an assistant inspect authorized GraphoTrees, versions and nodes, then compile focused GraphoTree context for a task or review step.
- graphode.graphotrees.list
- graphode.graphotree.get
- graphode.graphotree.versions.query
- graphode.graphotree.nodes.query
- graphode.graphotree.context.compile
GraphoTree draft editing tools
Draft editing tools are presented as proposed, reviewed model changes. They help compatible assistants create or refine candidate structure without silently mutating published project reality.
- graphode.graphotree.draft.ensure
- graphode.graphotree.node.create
- graphode.graphotree.node.update
- graphode.graphotree.node.delete_from_draft
- graphode.graphotree.relation.create
- graphode.graphotree.relation.update
- graphode.graphotree.tree_membership.upsert
GraphoTree review and publish tools
Review and publish tools keep agent-proposed or imported structure auditable before it becomes trusted model state. Humans can retain control through candidate review, merge requests and guarded publish steps.
- graphode.graphotree.candidate_review.create
- graphode.graphotree.merge_request.create
- graphode.graphotree.merge_request.resolve
- graphode.graphotree.draft.publish
Planned artifact and result helpers
Artifact and result helpers are planned public catalog entries for upload preparation and result submission where the corresponding owner routes and schemas are ready.
- graphode.artifact.prepare_upload
- graphode.result.submit
Early-access availability caveat
Exact MCP tool availability may vary during early access. Public tool names are product-direction catalog entries unless verified owner routes, schemas, claims and audit behavior are in place.
- Claim-filtered discovery
- Authorization checks
- Owner-service policy
- Audit requirements