Claude Code

Claude Code supports remote HTTP MCP servers natively, making it a natural fit for the hosted BoldSign MCP server. This setup uses an environment variable for the API key and a project-level .mcp.json file so the configuration is portable and the key is never stored in source control.

Set the BOLDSIGN_API_KEY environment variable in your terminal:

Linux/macOS:

export BOLDSIGN_API_KEY="your-api-key-here"

Windows (PowerShell):

$env:BOLDSIGN_API_KEY="your-api-key-here"

This environment variable is temporary for the current terminal session. For persistent storage, add it to your shell profile or use a secrets manager.

Create a file named .mcp.json in your project root (same directory as package.json or your project files):

{
    "mcpServers": {
        "boldsign": {
            "type": "http",
            "url": "<YOUR_REGION_MCP_ENDPOINT>",
            "headers": {
                "X-API-Key": "${BOLDSIGN_API_KEY}"
            }
        }
    }
}

Replace &lt;YOUR_REGION_MCP_ENDPOINT&gt; with the hosted MCP endpoint that matches your BoldSign account region. The ${BOLDSIGN_API_KEY} placeholder is expanded from your shell environment at runtime, and Claude Code does not store the API key.

  1. Start Claude Code in your project directory:
    claude
    
  2. Open the MCP tools view:
    /mcp
    
  3. Confirm that the boldsign server is listed and shows the available tools.

Try a simple read-only request first to verify the connection is working:

  • List my recent templates
  • Show my contacts

Once verified, you can use action-oriented prompts like:

  • Server not connecting? Run /mcp to check if the server is listed. Restart Claude Code if needed.
  • Authentication errors? Verify your API key is correct and the environment variable is set.
  • Wrong region? Ensure the MCP endpoint matches your BoldSign account region.