How to connect Fine Structure to VS Code and GitHub Copilot with MCP

VS Code stores MCP settings in an mcp.json file, and you can set the token as a secret input instead of writing it in plain view.

If you work with VS Code and GitHub Copilot Agent Mode, you can connect Fine Structure as a remote MCP server. This gives Copilot access to Fine Structure's tools without you manually copying files, schemas, or error history.

Where to put the file: You can use .vscode/mcp.json for a specific workspace or a User MCP configuration for the whole machine.

Storing the token: VS Code supports input variables, so the token can be saved as a secret and never appear in the file.

Verifying the connection: From the Command Palette you can run MCP: List Servers or open the MCP configuration.

Start in Fine Structure

Create an MCP token and then return to VS Code. If you're not sure, choose Read only to test the connection before editing.

Steps

Sign in to your Fine Structure account.
Open the MCP page using the Create MCP token button in the docs, or go directly to /mcp.
Choose whether the agent gets access to all the apps you own or to a single app only.
Choose permissions: Read only for testing, Build for editing, Full access only for an agent you trust.
Click Create MCP setup and copy the token or the configuration block. The token is shown only once.
In VS Code, open the Command Palette and search for MCP: Open Workspace Folder MCP Configuration or MCP: Open User Configuration.
Paste the config below.
When VS Code asks for the Fine Structure MCP token, paste the token without sharing it with anyone.
Run MCP: List Servers and confirm that the fineStructure server is active.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "fineStructureToken",
      "description": "Fine Structure MCP token",
      "password": true
    }
  ],
  "servers": {
    "fineStructure": {
      "type": "http",
      "url": "https://finestructure.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:fineStructureToken}"
      }
    }
  }
}

Why this is good: The secret input helps you avoid storing tokens inside Git. This matters especially for teams or client projects.