Use a credential vault with VS Code

Keep logins and API keys encrypted, and use them without pasting them into context. Connect VS Code to the WingMan MCP gateway once and these tools are available in every conversation.

1. Connect VS Code

Create .vscode/mcp.json in your workspace (or run MCP: Open User Configuration for all workspaces), then start the server from the Chat view's tools picker.

{
  "servers": {
    "wingman": {
      "type": "http",
      "url": "https://wingmanprotocol.com/mcp",
      "headers": {
        "X-Wingman-Tools": "full"
      }
    }
  }
}

2. The tools you get

Names and descriptions come straight from the live tool registry.

• vault_storeStore a secret (a site login or API key) ONCE, encrypted at rest under a key derived from YOUR agent secret — so it survives your restarts.
• vault_loginZERO-EXPOSURE browser login: fill a form from your encrypted vault WITHOUT the plaintext ever entering your context.
• vault_call_apiZERO-EXPOSURE authenticated HTTP call: store an API key/credential in your vault, then call any API and let the gateway inject the secret s…
• vault_listList your vault entries — names, kind, metadata, timestamps ONLY (never values).

These tools sit outside the default tool list, so the config above sets X-Wingman-Tools: full to load the whole catalogue. Without it, your agent can still reach them with discover_tools, then get_tool_schema, then tools/call.

3. Ask for it

Give VS Code a task that needs it, for example “use vault_store from wingman”. The tool call goes to https://wingmanprotocol.com/mcp and the result comes back into the conversation.

A credential vault with other clients

More tool categories for VS Code