### Gainium MCP Local Stdio Configuration

Source: https://gainium.io/help/mcp

Use this configuration for the simplest setup when your client supports stdio. Gainium credentials remain local.

```json
{
	"mcpServers": {
		"gainium": {
			"command": "npx",
			"args": ["-y", "gainium-mcp"],
			"env": {
				"GAINIUM_API_KEY": "YOUR_GAINIUM_API_KEY",
				"GAINIUM_API_SECRET": "YOUR_GAINIUM_API_SECRET"
			}
		}
	}
}
```

--------------------------------

### Paper Trading Context Example

Source: https://gainium.io/help/mcp

Example of a tool call input that enables paper trading for a specific request. This is typically set per request using `paperContext: true`.

```json
{
	"botId": "507f1f77bcf86cd799439011",
	"botType": "dca",
	"paperContext": true
}
```

--------------------------------

### Bot ID Restriction Example

Source: https://gainium.io/help/mcp

Example of a tool input that includes a `botId`. This is common for write operations like starting, stopping, or modifying bots.

```json
{
	"botId": "507f1f77bcf86cd799439011",
	"botType": "dca"
}
```

--------------------------------

### Claude Code Local stdio CLI Setup

Source: https://gainium.io/help/mcp

Add a local Gainium MCP server to Claude Code using the command-line interface. This pattern is for stdio connections.

```bash
claude mcp add gainium -- npx -y gainium-mcp

```

--------------------------------

### Claude Code Hosted HTTP CLI Setup

Source: https://gainium.io/help/mcp

Add a hosted Gainium MCP server to Claude Code using the command-line interface. This pattern is for HTTP connections.

```bash
claude mcp add --transport http gainium https://mcp.gainium.io/mcp

```