# MCP for VS Code

> Connect VS Code (agent mode / Copilot MCP) to SiberMate using a remote HTTP MCP server entry.

Last updated: 2026-06-15

## Server URLs

- Default remote MCP URL: `https://mcp.sibermate.com/mcp`
- Multi-tenant profile URL: `https://mcp.sibermate.com/profile/{YOUR TENANT DOMAIN}/mcp`
- Example profile URL: `https://mcp.sibermate.com/profile/sibermate.com/mcp`

## Setup Notes

- Create an mcp.json file in your workspace (.vscode/mcp.json) or user profile.
- Add SiberMate as an http server; the Authorization header goes under requestInit.headers.
- Prefer an inputs prompt (${input:...}) for the key instead of hardcoding it.

## Authentication

- Recommended remote flow: OAuth discovery from the MCP server URL.
- Bearer fallback: use `Authorization: Bearer <SIBERMATE_API_KEY>` only when the client supports custom headers.
- Local stdio fallback: `npx -y @sibermatedev/mcp` with `SIBERMATE_API_KEY` in the client environment.

## VS Code mcp.json

```
{
  "servers": {
    "sibermate": {
      "type": "http",
      "url": "https://mcp.sibermate.com/mcp",
      "requestInit": {
        "headers": {
          "Authorization": "Bearer ${input:sibermate_key}"
        }
      }
    }
  }
}
```

## Safety Checklist

- Use a dedicated tenant API key for MCP setup.
- Keep API keys out of prompts, screenshots, repositories, browser history, and shared docs.
- For profile URLs, the domain in the URL must match the tenant returned by the API key.
- Review generated action plans before sending assignments, reminders, removals, uploads, or deletions.

Related docs:

- https://docs.sibermate.com/mcp
- https://docs.sibermate.com/api-reference.md
- https://api.sibermate.com/v1/openapi.json