Overview
Generate Claude Desktop MCP configuration for a deployed server. This creates the JSON configuration needed to integrate your MCP server with Claude Desktop.Syntax
Arguments
ID of the deployed server to generate configuration for
Options
Target workspace ID (defaults to active workspace)
Add —insecure flag for development servers with self-signed certificates
Show instructions for copying to clipboard
Show detailed output
Examples
Basic Configuration Generation
Production Configuration
Uses current active workspace.Specific Workspace
Configuration Structure
The generated configuration includes:Field | Description |
---|---|
command | npx - runs packages without installing them |
args | Bridge arguments including endpoint and token |
endpoint | Workspace-specific server endpoint |
token | Workspace access token for authentication |
auth | Authentication method (null for token-based) |
oauth | OAuth configuration (false for token-based) |
No Installation Required: The configuration uses
npx
which automatically downloads and runs @nimbletools/mcp-http-bridge
without needing to install it globally. Claude Desktop will handle this automatically.Usage in Claude Desktop
1
Copy Configuration
Copy the entire JSON output from the command
2
Open Claude Config
Open your claude_desktop_config.json file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Linux:
~/.config/claude/claude_desktop_config.json
- Windows:
%APPDATA%\Claude\claude_desktop_config.json
3
Add Server Config
Add the server configuration to the
mcpServers
section4
Restart Claude
Restart Claude Desktop to load the new configuration
Security Notes
Token Security: The generated configuration contains your workspace access token. Keep this configuration file secure and don’t share it publicly.
Development vs Production: Use
--insecure
flag only for development environments with self-signed certificates. Production servers should use valid SSL certificates.