API Reference

Define an allowed connection pattern between node types for a relationship type. All three (relationship type, source node type, target node type) must already exist in the metamodel. Use get_metamodel to check existing types.

Add a new node type (entity type) to the metamodel. Do this before creating nodes of that type. You can define custom properties with data types.

Add a new relationship type to the metamodel. After creating it, use add_allowed_connection to specify which node types can be connected with it.

Auto-show all relationships between elements already placed on a diagram. For model diagrams shows M1 relationships; for metamodel diagrams shows allowed connections. Applied immediately.

Add nodes or node types to a diagram with auto-grid layout. For model diagrams use node IDs or auto-IDs (e.g. REQ-1); for metamodel diagrams use node type IDs. Applied immediately.

Create a new diagram for visualizing model elements. Use diagram_type 'metamodel' for M2 type diagrams, 'model' for M1 instance diagrams. Applied immediately.

Create a stored filter with a composable expression. Expressions: {"OfType":{"type_id":"<id>"}}, {"HasTag":{"tag":"foo"}}, {"NameMatches":{"operator":"Contains","value":"foo"}}, {"And":[...]}, {"Or":[...]}, {"Not":expr}, {"InFolder":{"folder_id":"<id>","recursive":true}}, or "All". Applied immediately.

Create a new folder for organizing model elements. Use layer 'metamodel' for node/relationship type folders, 'model' for node/relationship/diagram folders. Applied immediately.

Create new node instances. Node type must already exist in the metamodel (use get_metamodel to check, or add_node_type to create). Changes are applied immediately and broadcast to all connected browser users in real-time.

3 parameter(s)

Create relationships between existing nodes. Both source and target must exist. The relationship type must exist in the metamodel and have an allowed connection defined for the given source/target node types.

Delete a diagram and all its element placements. Does NOT delete the underlying nodes or relationships — only the visual representation. Applied immediately.

Delete a stored filter. Does not delete any model data. Applied immediately. Accepts filter ID or name.

Delete one or more nodes. By default, all connected relationships are also deleted (cascade). Set cascade_relationships to false to fail if the node has any relationships.

2 parameter(s)

Delete one or more relationships by their IDs. Use get_relationships to find the relationship IDs first.

Merge duplicate nodes into a single node. All relationships from merged nodes are redirected to the kept node. The merged nodes are then deleted. Use find_similar_nodes to identify candidates.

1 parameter(s)

Move model elements into a folder (or to root by omitting folder_id). Supports nodes, relationships, node types, relationship types, diagrams, and folders. Applied immediately.

Remove an allowed connection constraint, revoking permission for a relationship type to connect specific node type pairs. Applied immediately.

Remove nodes or node types from a diagram. Also removes connected relationship visualizations on that diagram. Does NOT delete the underlying elements. Applied immediately.

Remove a node type from the metamodel. Also cascades to remove all M1 instances of that type and their relationships. Applied immediately. Use with caution — cannot be undone via MCP.

Remove a relationship type from the metamodel. Also removes all relationships of that type from M1. Applied immediately. Use with caution.

Rename an existing folder and optionally update its description. Applied immediately.

Update an existing diagram's name or description. Applied immediately. Accepts diagram ID or name.

Update the model's top-level name or description. Applied immediately.

Update an existing node type: rename, recolor, change description, or add new properties. Applied immediately and broadcast to all connected users.

Update labels, descriptions, or properties on existing nodes. Use set_label/set_description to update core fields, set_properties for key-value pairs, and remove_properties to clear values. Node IDs accept both UUIDs and auto-IDs (e.g. REQ-42).

1 parameter(s)

Update an existing relationship type: rename, recolor, change description, or add new properties. Applied immediately and broadcast to all connected users.

Update labels, descriptions, or properties on existing relationships. Applied immediately and broadcast to all connected users. Relationship IDs accept both UUIDs and auto-IDs (e.g., "CON-5").

Update tags on any model element (node, relationship, node type, relationship type, diagram, or folder). Replaces all existing tags. Applied immediately.

Find nodes with similar names that might be duplicates. Uses string similarity matching. Useful before creating new nodes to avoid duplication.

3 parameter(s)

Get the model's schema (metamodel). Returns all node types, relationship types, their properties, allowed connections, and instance counts. Always call this first to understand what the model contains.

1 parameter(s)

Get complete details for one or more nodes by their IDs. Returns all properties, description, and metadata. Accepts both UUIDs and auto-IDs (e.g. REQ-42).

2 parameter(s)

Find relationships (connections) between nodes. Filter by relationship type, source node, target node, or node types. Source and target IDs accept both UUIDs and auto-IDs (e.g. REQ-42).

7 parameter(s)

Get model-wide statistics: node and relationship counts by type, most connected nodes, and property completeness. Useful for a quick model overview.

1 parameter(s)

Search for nodes (instances) in the model. Filter by type, name, description, property values, or folder. Returns summaries — use get_node_details for full information.

8 parameter(s)