Tapestry for VS Code

Give VS Code's AI chat your Tapestry memory and docs. This extension registers Tapestry's MCP servers with VS Code's Language Model API, so Copilot Chat — and any MCP-aware assistant in the editor — can recall past decisions from your memory and search Tapestry's documentation. No Claude Code required.

Already using Claude Code in VS Code? You don't need this — the tapestry-discipline + tapestry-patterns plugins already wire these servers through Claude Code's own .mcp.json. This extension is for everyone else who wants the same servers in VS Code's native MCP clients (like Copilot Chat).

What it registers

Install

From the VS Code Marketplace (the normal path):

code --install-extension tapestry.tapestry

Or open VS Code → Extensions → search "Tapestry" → Install. Listing: https://marketplace.visualstudio.com/items?itemName=tapestry.tapestry

From source (for local development against an unreleased version):

cd integrations/vscode
npm install
npm run compile
npx vsce package
code --install-extension tapestry-0.1.0.vsix

Configure

Open VS Code settings (Cmd/Ctrl+,) and search for "Tapestry". Two settings matter:

• tapestry.memoryMcpUrl — paste your deployment's memory MCP URL, e.g. https://your-memory-host.example.com/mcp/memory/. Leave empty to skip the memory server cleanly (the docs server still registers).
• tapestry.docsMcpCommand — defaults to python. Set to python3 or an absolute interpreter path if python on PATH doesn't resolve to the venv where you ran pip install tapestry-docs-mcp.
• tapestry.docsMcpEnabled — defaults to true. Set to false if you don't want the docs server registered.

Settings can also live in .vscode/settings.json per-workspace if you want per-project overrides.

Verify

After install + configuration:

1. Reload the VS Code window.
2. Open Copilot Chat (or any MCP-aware chat surface).
3. The Tapestry tools (memory_recall, memory_write, tapestry_docs_search, etc.) should appear in the tools list.
4. Try a tool call — tapestry_docs_search with query: "observer" should return ranked hits.

If the memory tools 401 or 404, check that your deployment is reachable from your machine and the URL is right.

What's NOT in v0.1.0

• No status bar UI
• No command palette ops (Tapestry: Recall etc.)
• No settings UI beyond the standard configuration page
• No signup flow (the memory URL is whatever you stand up)

All planned for v0.2+.

See also

• VS Code MCP server extension guide — the API this extension uses
• Tapestry — Quickstart (VS Code via Claude Code) — the parallel path that doesn't need this extension
• Tapestry Docs MCP — what tapestry-docs is
• Tapestry Memory MCP — what loom-memory is