Skip to content

Tuskway for VS Code

VS Code agent mode, on the same page as the team.

VS Code connects to Tuskway as a remote MCP server. Agent mode can read the feature's notes and design, pick up a ticket brief and record what it changed, for every teammate to see.

What changes

What VS Code gets from Tuskway.

  • One click to connect

    The install link adds the server to VS Code. Start it from the MCP view and sign in with your Tuskway account.

  • Search in plain words

    Agents search every epic in plain language, so “why did we move the cart server-side?” finds the decision.

  • Every version kept

    See who changed what, person or agent, and bring back any earlier version of a note.

Setup

Connect VS Code in a minute.

Then run the workflow from VS Code, one command per step:

  1. /start-epicCapture the goal, constraints and open questions.
  2. /write-designDraft the tech design in sections your team reviews.
  3. /draft-ticketsSplit it into briefs with acceptance checks.
  4. /tackle-ticketBuild one ticket from its brief and design section.
Add to VS Code
  1. 1

    Start the server from the MCP view and sign in when asked.

  2. 2

    Or paste this into mcp.json. VS Code uses servers, and the server needs a transport type.

    mcp.json
    {
      "servers": {
        "tuskway": {
          "type": "http",
          "url": "https://tuskway.com/mcp"
        }
      }
    }

Step-by-step guide: set up Tuskway in VS Code

FAQ

VS Code questions.

Which config key does VS Code use?

VS Code's mcp.json uses servers with a type of http, not the mcpServers key other clients use. The snippet on this page has the right shape.

Give VS Code a plan your team agreed on.

Every agent on the team reads the same spec, whatever tool it runs in.