Skip to main content
VS Code’s built-in MCP support (used by GitHub Copilot Chat’s agent mode and other MCP-aware extensions) reads from a workspace .vscode/mcp.json or your user settings.

Workspace config

Create .vscode/mcp.json:
Using inputs means VS Code prompts you for the key the first time (and stores it securely) instead of writing it in plain text into a file you might commit.

User settings (all workspaces)

Command Palette → MCP: Open User Configuration, and add the same xentfi entry under your VS Code version’s MCP servers section in settings.json.

Enabling it

1

List servers

Command Palette → MCP: List Servers → confirm xentfi shows as running.
2

Use agent mode

Open Copilot Chat, switch to Agent mode — XentFi tools are offered automatically when relevant.
3

Debug if needed

Command Palette → MCP: Show Server Output, look for [xentfi-mcp] lines.
VS Code’s MCP integration has changed across releases. If .vscode/mcp.json isn’t picked up, check the Command Palette for the current MCP commands in your installed version and use MCP: Add Server to generate a stub, then fill in the command/args/env from the snippet above.

Next steps

Tools Reference

See every available tool.

Codex / Agents SDK

Another way to build with these tools programmatically.