Built on the official `mcp` Python SDK (`>=1.27`), which negotiates the **2025-11-25** MCP protocol revision. Runs over **stdio** by default and
Built on the official mcp Python SDK (>=1.27), which negotiates the 2025-11-25 MCP protocol revision. Runs over stdio by default and optionally over the Streamable HTTP transport. That is what the obsidian jsoncanvas mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 11 tools. What each one is for:
create_canvas — Create a canvas from nodes (and optional edges) and write it to aInput — nodes (array of JSON Canvas node objects), filename (string, no extension),validate_canvas — Validate canvas data against the JSON Canvas 1.0 specificationread_canvas — Read a stored .canvas file and return its nodes and edgeslist_canvases — List the .canvas files available in OUTPUT_PATHReturns — array of filenamesedit_canvas — Add, update, and/or remove nodes and edges on a stored canvas in oneexport_canvas — Export a stored canvas to another formatsearch_canvases — Case-insensitive substring search across stored canvasesTools — create_canvas, read_canvas, and edit_canvas are linked to the canvas viewer via _meta.ui.resourceUri, so UI-capable hosts render the result inlineResources — The Resources tool exposed by this serverConfiguration is passed through the environment: OUTPUT_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Obsidian Jsoncanvas's toolset — create_canvas, Input, validate_canvas and 8 more — is a fair guide to whether it matches your workflow. It is maintained by Cam10001110101; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| create_canvas | Create a canvas from nodes (and optional edges) and write it to a |
| Input | nodes (array of JSON Canvas node objects), filename (string, no extension), |
| validate_canvas | Validate canvas data against the JSON Canvas 1.0 specification. |
| read_canvas | Read a stored .canvas file and return its nodes and edges. |
| list_canvases | List the .canvas files available in OUTPUT_PATH. |
| Returns | array of filenames. |
| edit_canvas | Add, update, and/or remove nodes and edges on a stored canvas in one |
| export_canvas | Export a stored canvas to another format. |
| search_canvases | Case-insensitive substring search across stored canvases. |
| Tools | create_canvas, read_canvas, and edit_canvas are linked to the canvas viewer via _meta.ui.resourceUri, so UI-capable hosts render the result inline. |
| Resources | The Resources tool exposed by this server. |
### uv (stdio)
```json
{
"mcpServers": {
"jsoncanvas": {
"command": "uv",
"args": ["--directory", "/path/to/jsoncanvas", "run", "mcp-server-jsoncanvas"],
"env": { "OUTPUT_PATH": "./output" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OUTPUT_PATH | Filesystem location the server is allowed to use. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.