MCP Configuration

Model Context Protocol (MCP) servers extend your agent's capabilities by connecting to external services and data sources. This step is optional but powerful for integrating with external systems.

Transport Types

MCP supports four transport types for connecting to servers:

stdio (Standard I/O)

The most common transport type. Runs a local command and communicates via standard input/output. Typically used with npx packages.

1{
2  "name": "filesystem",
3  "transport": "stdio",
4  "command": "npx",
5  "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/directory"],
6  "env": {}
7}

HTTP

Connects to a REST endpoint. Useful for remote MCP servers.

1{
2  "name": "remote-server",
3  "transport": "http",
4  "url": "https://api.example.com/mcp",
5  "headers": {
6    "Authorization": "Bearer ${API_TOKEN}"
7  }
8}

SSE (Server-Sent Events)

Uses Server-Sent Events for real-time communication.

1{
2  "name": "streaming-server",
3  "transport": "sse",
4  "url": "https://api.example.com/mcp/events"
5}

SDK

Loads a JavaScript module directly. Useful for custom in-process servers.

1{
2  "name": "custom-server",
3  "transport": "sdk",
4  "serverModule": "./custom-mcp-server.js"
5}

Available Server Templates

Filesystem

Git & Version Control

Databases

APIs & Web

Cloud Services

Productivity

Environment Variables

MCP server configurations can reference environment variables using the${VAR_NAME} syntax. These values are read from your .env file at runtime.

1{
2  "name": "github",
3  "transport": "stdio",
4  "command": "npx",
5  "args": ["-y", "@modelcontextprotocol/server-github"],
6  "env": {
7    "GITHUB_TOKEN": "${GITHUB_TOKEN}"
8  }
9}

Adding Custom Servers

Click "Add Custom Server" to configure a server not in the templates list. You'll need to specify:

• Name - Unique identifier for the server
• Transport - How to connect (stdio, http, sse, sdk)
• Command/URL - The command to run or URL to connect to
• Arguments - Command-line arguments (for stdio)
• Environment - Environment variables to set

Generated Configuration

MCP configuration is written to .mcp.json in your generated project:

1{
2  "mcpServers": {
3    "filesystem": {
4      "command": "npx",
5      "args": ["-y", "@modelcontextprotocol/server-filesystem", "./data"]
6    },
7    "github": {
8      "command": "npx",
9      "args": ["-y", "@modelcontextprotocol/server-github"],
10      "env": {
11        "GITHUB_TOKEN": "${GITHUB_TOKEN}"
12      }
13    }
14  }
15}