Skip to content

VS Code

Use VS Code’s MCP support for your selected chat profile or harness. VS Code starts a configured local Ark server automatically.

  1. Give the guided setup request to an agent with terminal and file-editing access. Name VS Code and whether you are working locally, over SSH or in a Dev Container.
  2. Let it prepare Ark and the configuration for your installed MCP format; enter keys in the private editor.
  3. Use MCP: Add Server or your edition’s MCP settings when UI confirmation is needed, select the intended user/profile scope, and approve ark-seed.

If an entry was already added, review it rather than adding a duplicate. VS Code and portable Copilot formats differ; the fallback examples below are alternatives, not steps that everyone must complete.

Manual configuration formats and scope
Destination Scope Envelope
.vscode/mcp.json Workspace, VS Code compatibility format servers
Selected user profile’s mcp.json User/profile, compatibility format servers
Workspace-root .mcp.json, where supported Project, portable Copilot format mcpServers
Copilot user configuration User/global for that harness mcpServers

For user/global setup, use MCP: Add Server and select the supported user/profile or harness destination. Do not guess the profile’s storage path. Current official docs place portable Copilot user configuration at $COPILOT_HOME/mcp-config.json, falling back to ~/.copilot/mcp-config.json; confirm this in your installed edition. Older editions may offer only the VS Code profile/workspace format.

Complete the shared prerequisites. A remote or Dev Container session needs the installation and paths on its execution host, not automatically on the local desktop.

Merge this into workspace .vscode/mcp.json, or the profile file opened by the supported configuration command. Use servers, not mcpServers:

{
"servers": {
"ark-seed": {
"type": "stdio",
"command": "/absolute/path/to/uv",
"args": [
"--directory",
"/absolute/path/to/ark-mcp",
"run",
"--locked",
"--no-sync",
"python",
"-m",
"ark_mcp"
],
"env": {
"ARK_MCP_ENV_FILE": "/absolute/path/to/private/ark-mcp/.env",
"MCP_TRANSPORT": "stdio",
"MCP_AUTH_MODE": "local"
}
}
}
}

Replace all placeholder paths. Optional inputs belongs at the top level, not inside servers; this example needs no interactive credential inputs. Do not use envFile to distribute provider keys. Ark reads its private file through the non-secret ARK_MCP_ENV_FILE path.

Only use this variant when your installed harness supports the corresponding portable destination. Merge it into that destination, not .vscode/mcp.json:

{
"mcpServers": {
"ark-seed": {
"command": "/absolute/path/to/uv",
"args": [
"--directory",
"/absolute/path/to/ark-mcp",
"run",
"--locked",
"--no-sync",
"python",
"-m",
"ark_mcp"
],
"env": {
"ARK_MCP_ENV_FILE": "/absolute/path/to/private/ark-mcp/.env",
"MCP_TRANSPORT": "stdio",
"MCP_AUTH_MODE": "local"
}
}
}
}

Portable configuration does not need envFile or VS Code ${input:...} support because the server loads its private credentials itself. Preserve existing entries, avoid duplicate same-name definitions, and do not automatically commit machine-specific project configuration.

Use MCP: List Servers, or the MCP/customizations panel available in your edition, and run the discovery-only check. Continue with Your First Tool Call. Finish active jobs before restarting the connection.

See Integrations, Cursor, Getting Started, Tools, and Configuration.

Sources consulted 2026-11-10. The compatibility and portable variants still require verification against the actual installed edition and harness.