VS Code

Connect VS Code

VS Code’s AI tooling (Copilot Chat and compatible MCP-aware extensions) supports OAuth-protected remote MCP servers — connect Antiem to keep agent sessions in your editor grounded in your brand profile.

01
Add Antiem as an MCP server
In VS Code's MCP settings (or a compatible extension’s MCP configuration), add a new server using Antiem's MCP server URL: https://mcp.antiem.io/mcp.
02
Let it discover the authorization server
VS Code reads Antiem’s public discovery documents at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server to find the OAuth server automatically.
03
Sign in and review the consent screen
You’re sent to Antiem to sign in (if you aren’t already), then to a consent screen that names exactly which brand and scope VS Code is asking for.
04
Authorize the connection
Approve the request. VS Code receives an access token scoped to the brand(s) you approved — it cannot read brands outside that scope.
05
Use it, then check it anytime
Ask your agent session to pull your brand profile or boundaries while it works. Every call is logged; review or revoke access anytime from /connections inside Antiem.

Antiem exposes 17 mostly read-only tools over MCP. Only proposing a change to a brand field requires an owner or admin role in your Antiem organization.

All agents