Claude Desktop and VS Code

Desktop clients launch local MCP processes from their own environment. A command that works in your terminal may fail in an app because PATH, environment variables or working directory differ. Use a verified distribution and inspect the client’s MCP log.

Claude Desktop command entry

{
  "mcpServers": {
    "toolport": {
      "command": "npx",
      "args": ["-y", "@toolport/mcp"],
      "env": { "TOOLPORT_TOKEN": "REPLACE_WITH_LOCAL_SECRET" }
    }
  }
}

Use the desktop client’s documented local-server configuration. Restart or reload as its documentation requires. Browser-hosted connectors are a different transport and do not launch npx on your computer.

VS Code workspace configuration

{
  "inputs": [{
    "type": "promptString",
    "id": "toolport-token",
    "description": "Issue tracker token",
    "password": true
  }],
  "servers": {
    "toolport": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@toolport/mcp"],
      "env": { "TOOLPORT_TOKEN": "${input:toolport-token}" }
    }
  }
}

VS Code uses servers, not mcpServers, in .vscode/mcp.json. The input prompts for the token rather than storing its value in the file. Interactive inputs may not be available in every execution environment; check the official reference for the specific host you use.

Verify and disconnect

• Use the client’s MCP controls to start the server.

• Confirm all four tools are advertised.

• Approve one narrowly scoped read and inspect the result.

• Stop or remove the server entry when finished; revoke access separately if needed.

Remote hosting

This guide describes stdio only. It does not establish a hosted Toolport URL. Do not paste the template’s .example endpoint into a production connection. A remote connection needs a verified endpoint, supported transport and documented authentication.

VS Code: official MCP setup

Local execution and deployment