Skip to main content
Integrate your deployed MCP servers with Claude Desktop for enhanced AI capabilities.

​
Overview

NimbleBrain Studio generates complete Claude Desktop configurations automatically, making it easy to connect your MCP servers to Claude.
No manual JSON editing required! Studio generates the entire configuration for you.

​
Quick Setup

1

Deploy an MCP Server

Ensure you have at least one server deployed in your workspace
2

Generate Configuration

From the server details page, click Claude Desktop Config
3

Copy Configuration

Click Copy to Clipboard to copy the JSON
4

Open Claude Config File

Navigate to Claude’s configuration file:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
5

Paste & Save

Paste the configuration and save the file
6

Restart Claude Desktop

Quit and restart Claude Desktop to load the servers

​
Generated Configuration

Studio generates a complete configuration including: 
{
  "mcpServers": {
    "nationalparks-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nimbletools/mcp-client",
        "https://mcp.nimbletools.dev/{workspace-id}/nationalparks-mcp/mcp"
      ],
      "env": {
        "NTCLI_TOKEN": "your-workspace-token"
      }
    }
  }
}

​
Configuration Components

​
Server Name
string
The MCP server identifier from the registry
​
command
string
Always npx to use the NimbleTools MCP HTTP client
​
args
array
Array containing:
  • -y flag to bypass prompts
  • @nimbletools/mcp-client package
  • Your server’s MCP endpoint URL
​
env.NTCLI_TOKEN
string
Your workspace authentication token (automatically included)

​
Multiple Servers

Add multiple MCP servers to Claude Desktop:

​
Option 1: Generate Combined Config

1

Navigate to Workspace Settings

Go to Settings → Claude Desktop
2

Select Servers

Check all servers you want to include
3

Generate Config

Click Generate Combined Config
4

Copy & Apply

Copy and paste into your Claude config file

​
Option 2: Merge Individual Configs

Manually merge configurations from multiple servers: 
{
  "mcpServers": {
    "nationalparks-mcp": {
      "command": "npx",
      "args": ["-y", "@nimbletools/mcp-client", "https://mcp.nimbletools.dev/{workspace}/nationalparks-mcp/mcp"],
      "env": {"NTCLI_TOKEN": "your-token"}
    },
    "finnhub-mcp": {
      "command": "npx",
      "args": ["-y", "@nimbletools/mcp-client", "https://mcp.nimbletools.dev/{workspace}/finnhub-mcp/mcp"],
      "env": {"NTCLI_TOKEN": "your-token"}
    }
  }
}
You can mix NimbleTools servers with locally-run MCP servers in the same config file.

​
Verifying Integration

​
Check Claude Desktop

After restarting Claude Desktop:
1

Open Claude Desktop

Launch the application
2

Look for Tool Indicator

You should see a 🔌 icon or “Tools available” message
3

Start a Conversation

Begin a new chat to test the integration
4

Ask a Question

Try a query that would use your MCP server’s tools

​
Example Queries

  • nationalparks-mcp
  • finnhub-mcp
  • github-mcp
“What are the top 5 most visited national parks?”“Show me national parks in California with camping facilities”

​
Tool Call Visibility

Claude will show you when it’s using your MCP tools:

Claude

I’ll search for national parks in California.

🔧 Using tool: search_parks

I found 9 national parks in California…

​
Troubleshooting

Possible causes:
  • Claude Desktop wasn’t fully restarted
  • Configuration file has JSON syntax errors
  • Config file is in wrong location
Solution:
  • Fully quit Claude Desktop (check system tray)
  • Validate JSON syntax with a JSON validator
  • Verify file path matches your OS
Possible causes:
  • Server is scaled to zero (cold start delay)
  • Workspace token expired
  • Required secrets not configured
Solution:
  • Wait 5-10 seconds for cold start
  • Refresh token in Studio (Settings → API Tokens)
  • Check server requires secrets and add them
Possible causes:
  • Token expired
  • Token was revoked
  • Wrong workspace token
Solution:
  • Generate a new token in Studio
  • Update NTCLI_TOKEN in config file
  • Restart Claude Desktop
Possible causes:
  • Server scaled to zero
  • First request after idle period
Solution:
  • Set minimum replicas to 1 in server settings
  • Understand cold starts typically take 2-5 seconds

​
Advanced Configuration

​
Custom Environment Variables

Add extra environment variables for specific servers: 
{
  "mcpServers": {
    "your-server": {
      "command": "npx",
      "args": ["-y", "@nimbletools/mcp-client", "https://..."],
      "env": {
        "NTCLI_TOKEN": "your-token",
        "CUSTOM_VAR": "custom-value",
        "DEBUG": "true"
      }
    }
  }
}
Environment variables in Claude’s config are separate from secrets in Studio. These are only used by the client, not the server.

​
Mixing NimbleTools and Local Servers

Run NimbleTools-hosted and local MCP servers together: 
{
  "mcpServers": {
    "nimbletools-server": {
      "command": "npx",
      "args": ["-y", "@nimbletools/mcp-client", "https://mcp.nimbletools.dev/..."],
      "env": {"NTCLI_TOKEN": "your-token"}
    },
    "local-server": {
      "command": "node",
      "args": ["/path/to/local-server/index.js"]
    }
  }
}

​
Configuration Management

​
Backing Up Configuration

Always back up your Claude config before making changes: 
# macOS
cp ~/Library/Application\ Support/Claude/claude_desktop_config.json ~/claude_config_backup.json

# Windows
copy %APPDATA%\Claude\claude_desktop_config.json %USERPROFILE%\claude_config_backup.json

​
Version Control

Store configurations in version control for team sharing: 
# .gitignore - exclude tokens!
claude_desktop_config.json

# Share template without tokens
claude_desktop_config.template.json

Server Management

Deploy and manage MCP servers

API Keys & Tokens

Generate and manage workspace tokens

CLI: Claude Config

Generate config from command line

Developer Integration Guide

Advanced integration patterns
⌘I