KnowMapped MCP Server

Validate or create a concept map or Futures Wheel. Set graph.graph_type explicitly. Wheels require causal parent/order metadata and use the same radial geometry as the editor; only radial layout is allowed. Manual wheel creation is included in Free; MCP creation uses the normal MCP entitlement and credit policy. Concept maps: Specify requested layout only as top-level graph.layout_intent. When omitted, requested_layout and resolved_strategy are smart, but [0,0] placeholders are retained for the map client to lay out on first draw; layout_application is client-first-draw. Complete explicit coordinates are preserved instead. Set validate_only=true to check the exact final graph schema, layout, capacity, links, and credits without creating a map, charging credits, or reserving the idempotency key. For credit-bearing creation, show the quoted charge, then confirm the retained draft only after explicit approval.

Return layout bounds and graph statistics without returning graph content.

Retrieve an authorized map with independent node_offset, edge_offset, and page_size parameters. Canonical IDs are always retained in projected nodes and edges even when include_nodes or include_edges omits id. Use summary for statistics without graph content or compact for token-efficient fields. Search results return copy-safe map references so UUIDs should not be typed manually.

Return one concept and its directly connected concepts and relationships without retrieving the full graph. Provide node_id or an exact unique label.

Recover the definitive state of a map creation without creating a map or charging credits. Provide exactly one draft_id or the original idempotency_key. A succeeded result includes the canonical map ID and revision.

Check public snapshot revision, moderation and delivery without loading graph content. Requires maps:publish and editable-map access. Revision differences mean content may have changed, since operational changes also advance revisions. After a timeout retry the original publication with the same idempotency_key; use this tool to check current delivery separately.

Return the authoritative, versioned schema, graph_type_operations and examples for atomic KnowMapped concept-map and Futures Wheel patches. Call this before constructing an update instead of guessing operation or field names.

Read a wheel consequence, its ancestors, inherited domain and paginated descendants, including collapsed content. Omit the node reference to start at the central change. Compact keeps causal metadata; full adds descriptions, resources and provenance.

Search maps available to the connected KnowMapped account. Use this when a user refers to a saved map or wants to find prior concepts; existing ownership and sharing permissions are enforced server-side.

Enable or disable public live viewing for an owned published concept map or Futures Wheel. Enable only at the user's explicit request: live viewers see ongoing saved edits, not just the published snapshot. Requires the existing account entitlement and maps:publish permission. Does not publish a private map or invite collaborators. Reuse an identical idempotency key after a dropped response.

Make a map public or private at its current revision. Obtain the user's explicit permission to publish and confirmation that they have the right to publish before setting copyright_acknowledged=true; never infer it from map content. Initial publication creates a moderated public snapshot and generated preview. Making private removes the snapshot and disables live viewing. Setting an already-public map public does not publish edits: use publish_knowmapped_map. Reuse the same idempotency_key and identical arguments after a dropped response; a different request needs a new key. A pending_review result means publication has not succeeded. On a revision conflict, retrieve the map and reconsider before retrying.

Validate or atomically update an editable concept map or Futures Wheel. For wheels use add_consequence, update_consequence, move_branch, remove_branch (confirmed cascade), set_branch_collapsed, upsert_domain, remove_domain, assign_domain and layout_wheel. Orders, causal edges and radial geometry are derived; concept operations are rejected. For concept maps: Accepted operations are update_map, add_node, update_node, remove_node, add_edge, update_edge, remove_edge, replace_edges, and layout_nodes; get_knowmapped_update_schema is the authoritative versioned contract. Use id for identifiers, title for the map title, and layout_nodes with strategy, spacing, groups, and optional flow. Node references accept IDs, earlier temp_id values, or exact unique labels. Edge references accept IDs or semantic source/target/current-relationship matches. validate_only returns a corrected executable normalized_patch, all detectable errors and warnings, layout positions and bounds, a patch summary, publication state, and current revision without changing data. On a stale write, revalidate the same patch at current_revision, then submit the returned normalized_patch.

Transactionally confirm a preflighted creation by draft ID. Success definitively returns map_id and revision. A failed transaction preserves the draft for retry, and retrying a committed success returns the same result without charging again. Use get_knowmapped_map_creation_result after a timeout or malformed response.

Return an import-ready .know JSON file for an authorized concept map or Futures Wheel. Serialize file as UTF-8 JSON under filename. Includes every node, including collapsed branches, presentation and provenance; does not publish or create a map. Visual exports remain in the app.

Check eligibility and credits for concept maps or Futures Wheels (graph_type), or retain a fully validated graph as a short-lived draft. The exact creation layout field is top-level graph.layout_intent, for example left-to-right. For concept maps, omission records Smart intent and complete explicit coordinates are preserved. Futures Wheels default to radial, derive positions with the wheel renderer, and reject other intents. Fields named layout, layout_type, or strategy are rejected. Drafts do not reserve credits and can be confirmed by draft ID without resending the graph.

Publish or republish completed edits to an already-public map when the user requests it. Use the revision returned by the final edit or a fresh retrieval. Applies the same permissions, locks, moderation, and restrictions as browser publishing and generates the public preview. Reuse the same idempotency_key and identical arguments after a dropped response. Returns published revision and sync state; pending review or sync must not be reported as a fully delivered publication. On a revision conflict, retrieve the map and reconsider before retrying. To publish a private map first use set_knowmapped_map_visibility with explicit copyright acknowledgement.