kObsidian MCP

Canvas Node Connections

canvas.connections

Read-onlyIdempotent

Retrieve incoming and outgoing edges for a specific canvas node, enabling step-by-step graph traversal without loading the entire file. Use to inspect local connections or navigate between linked nodes.

Instructions

Return the incoming and outgoing edges of a single canvas node. Use this to walk the canvas graph one node at a time without loading the full document. Read-only. For full-graph parsing, use canvas.parse.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Input Schema

TableJSON Schema

Name	Required	Description
`nodeId`	Yes	Id of the node whose edges to return.
`filePath`	Yes	Vault-relative path to an Obsidian `.canvas` file.
`vaultPath`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`nodeId`	Yes
`filePath`	Yes
`incoming`	Yes
`outgoing`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.5Aug 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed8 schema fields changedv0.1.2Apr 25, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / filePath / description

Added value: +"Vault-relative path to an Obsidian `.canvas` file."

addedInput schema / properties / nodeId / description

Added value: +"Id of the node whose edges to return."

addedOutput schema / properties / filePath
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / incoming

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / nodeId
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / outgoing

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / required

Added value: +[
+  "filePath",
+  "nodeId",
+  "incoming",
+  "outgoing"
+]

First observedv0.1.0Apr 24, 2026

TDQS

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already state readOnlyHint, idempotentHint, and destructiveHint, so the description's 'Read-only' is redundant but not harmful. It adds valuable behavioral context about session-active vault resolution and the precedence of an explicit vaultPath, which is not derivable from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: operation, use case with alternative, and vault behavior. No filler, and the most important information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and annotations cover safety, the description provides the essential context: graph-walking use case, full-graph alternative, and vault resolution rules. Nothing critical is missing for an agent to select and invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers nodeId and filePath with good descriptions, and the description fills the gap for vaultPath by explaining it overrides the session-active vault. This is meaningful added meaning beyond the schema for the undocumented parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a precise verb and resource: 'Return the incoming and outgoing edges of a single canvas node.' It clearly differentiates from canvas.parse, which handles full-graph parsing, and from links.connections, which likely deals with note links rather than canvas edges.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool ('to walk the canvas graph one node at a time without loading the full document') and names the alternative for full-graph parsing ('use canvas.parse'). It also clarifies the vault selection behavior with vaultPath taking precedence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server