VS Code Homespun transfer

How to: VS Code Homespun transfer

client:VS Code transport:streamable-http tool:transfer

Add Homespun to VS Code

01
Open .vscode/mcp.json and merge this in. Keep any servers already there.

{
  "servers": {
    "homespun": {
      "type": "http",
      "url": "https://homespun.dev/mcp"
    }
  }
}

02
Save the file and restart VS Code.
03
Ask for something transfer does. VS Code lists the server's tools on connect and calls transfer itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that Homespun's identifier in your config matches the one above exactly.

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Set these first

Homespun will not start until these are set, so transfer never becomes available.

HOMESPUN_API_KEY
HOMESPUN_URL
HOMESPUN_AGENT_NAME
HOMESPUN_REGISTER_SECRET

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

Homespun MCP server