MCP Servers
Model Context Protocol server features and configuration
What Is MCP?
MCP (Model Context Protocol) is a protocol for extending AI model capabilities. Through MCP servers, you can connect external tools, data sources, and services to the AI assistant.
How It Works
AIRGAP Assistant
|
v
MCP Client (built-in)
|
v
MCP Server (local process)
|
v
Tools / Data Sources / Services
When the AI assistant processes a user request, it automatically invokes tools connected via MCP servers as needed. Users simply make requests in natural language — no special commands required.
MCP in Air-Gapped Environments
In air-gapped environments where network access is restricted, MCP servers run as local processes only.
Available MCP Server Types
| Type | Description | Air-Gap Compatible |
|---|---|---|
| Local Tool Server | File system, database access | Yes |
| Local API Server | Internal network API calls | Yes (intranet) |
| External Service Server | Cloud API integration | No |
Figma MCP (AIRGAP Bridge)
The Prototype tab in AIRGAP Bridge integrates with Figma Desktop's MCP plugin.
- Run the MCP plugin in the Figma Desktop app.
- Communicates via JSON-RPC 2.0 protocol on
localhost:3845. - If Figma MCP is not running, Bridge falls back to .fig file drop mode.
Basic Configuration
MCP server settings are managed via JSON files.
{
"mcpServers": {
"my-local-tool": {
"command": "node",
"args": ["C:/tools/my-mcp-server/index.js"],
"disabled": false
}
}
}
Configuration Options
| Option | Description | Required |
|---|---|---|
command | Server execution command | Required |
args | Command arguments | Optional |
env | Environment variables | Optional |
disabled | Whether disabled | Optional (default: false) |
Related Documentation
- MCP Server Configuration - Configuration file editing guide
- Connecting to a Remote MCP Server - Remote server connection in networked environments