Configuring MCP Servers
Editing and managing MCP server configuration files
Configuration File Location
MCP server settings are managed as JSON files. The location and format depend on which assistant is currently active.
| Assistant | Configuration Location |
|---|---|
| AIRGAP Assistant (Cline fork) | %APPDATA%\AIRGAP Studio\User\globalStorage\airgap.airgap-assistant\settings\cline_mcp_settings.json (single file) |
| AIRGAP Lite Assistant (Continue fork) | %USERPROFILE%\.continue\mcpServers\ directory (one *.json file per server) |
| Project-scoped settings | Project root\.vscode\mcp.json (when supported by the active assistant) |
Project-scoped settings take priority over the same assistant's global settings. The two assistants do not share MCP servers, so to use the same server in both you must register it on each side separately.
Editing the Configuration File
Opening from the Command Palette
- Press
Ctrl+Shift+Pto open the Command Palette. - Search for
MCP. - Select the MCP: Edit Settings command.
Manual Editing
You can open the configuration file directly and edit the JSON manually.
Configuration Format
Basic Structure
{
"mcpServers": {
"server-name": {
"command": "executable command",
"args": ["arg1", "arg2"],
"env": {
"ENV_VAR": "value"
},
"disabled": false
}
}
}
Configuration Fields
| Field | Type | Description | Required |
|---|---|---|---|
command | string | Server executable path or command | Required |
args | string[] | Array of arguments to pass to the command | Optional |
env | object | Environment variables to set for the server process | Optional |
disabled | boolean | If true, the server will not be loaded | Optional |
Configuration Examples
Node.js MCP Server
{
"mcpServers": {
"file-tools": {
"command": "node",
"args": ["C:/mcp-servers/file-tools/index.js"],
"disabled": false
}
}
}
Python MCP Server
{
"mcpServers": {
"data-analyzer": {
"command": "python",
"args": ["C:/mcp-servers/data-analyzer/server.py"],
"env": {
"PYTHONPATH": "C:/mcp-servers/data-analyzer"
}
}
}
}
Multiple Servers
{
"mcpServers": {
"file-tools": {
"command": "node",
"args": ["C:/mcp-servers/file-tools/index.js"]
},
"db-connector": {
"command": "node",
"args": ["C:/mcp-servers/db-connector/index.js"],
"env": {
"DB_PATH": "C:/data/local.db"
}
},
"unused-server": {
"command": "node",
"args": ["C:/mcp-servers/unused/index.js"],
"disabled": true
}
}
}
Server Management
Adding a Server
- Add a new entry to the
mcpServersobject in the configuration file. - Save the file.
- AIRGAP Assistant will automatically detect and start the new server.
Removing a Server
Delete the server entry from the configuration file, or set "disabled": true to deactivate it.
Checking Server Status
You can check the connection status of each server in the MCP section of the AIRGAP Assistant settings panel.
- Connected: The server is running normally
- Disconnected: The server is not connected
- Error: An error occurred while starting the server
Air-Gapped Environment Considerations
When using MCP servers in an air-gapped environment, keep the following in mind:
- Server executables and all dependencies must be pre-installed locally.
- For servers that require
npm install, prepare offline packages in advance. - Servers that call external APIs will not work in an air-gapped environment.
Related Documentation
- MCP Server Features - MCP overview and concepts
- Connecting to a Remote MCP Server - Remote server connection