Skip to main content

​
Overview

The AnySite MCP Server requires proper configuration to connect with your API credentials and customize tool behavior. This guide covers all configuration options available.

​
Configuration File

The MCP server uses a JSON configuration file that should be placed in your project directory or specified via environment variables.

​
Basic Configuration

Create a hdw-config.json file with the following structure: 
{
  "apiKey": "your-hdw-api-key",
  "baseUrl": "https://api.anysite.io",
  "defaultTimeout": 30000,
  "retryAttempts": 3,
  "enableLogging": true,
  "logLevel": "info"
}

​
Configuration Options

​
apiKey
string
required
Your AnySite API access token. Get this from your dashboard.
​
baseUrl
string
default:"https://api.anysite.io"
The base URL for the AnySite API. Usually you don’t need to change this.
​
defaultTimeout
number
default:"30000"
Default timeout in milliseconds for API requests.
​
retryAttempts
number
default:"3"
Number of retry attempts for failed API requests.
​
enableLogging
boolean
default:"true"
Enable or disable logging output.
​
logLevel
string
default:"info"
Log level: debug, info, warn, error.

​
Environment Variables

Alternatively, you can configure the MCP server using environment variables: 
export HDW_API_KEY="your-hdw-api-key"
export HDW_BASE_URL="https://api.anysite.io"
export HDW_TIMEOUT="30000"
export HDW_RETRY_ATTEMPTS="3"
export HDW_LOG_LEVEL="info"
Environment variables take precedence over configuration file settings.

​
Tool-Specific Configuration

​
LinkedIn Tools Configuration

Configure LinkedIn-specific settings: 
{
  "tools": {
    "linkedin": {
      "maxResults": 50,
      "includePrivateProfiles": false,
      "searchDepth": "standard"
    }
  }
}

​
Instagram Tools Configuration

Configure Instagram-specific settings: 
{
  "tools": {
    "instagram": {
      "maxPosts": 100,
      "includeStories": false,
      "mediaQuality": "standard"
    }
  }
}

​
Rate Limiting Configuration

Configure rate limiting to stay within API limits: 
{
  "rateLimiting": {
    "enabled": true,
    "requestsPerMinute": 60,
    "burstLimit": 10
  }
}

​
Claude Desktop Integration

To use the MCP server with Claude Desktop, add this configuration to your Claude config file:

​
macOS

Edit ~/Library/Application Support/Claude/claude_desktop_config.json: 
{
  "mcpServers": {
    "hdw": {
      "command": "node",
      "args": ["/path/to/hdw-mcp-server/dist/index.js"],
      "env": {
        "HDW_API_KEY": "your-hdw-api-key"
      }
    }
  }
}

​
Windows

Edit %APPDATA%\Claude\claude_desktop_config.json: 
{
  "mcpServers": {
    "hdw": {
      "command": "node",
      "args": ["C:\\path\\to\\hdw-mcp-server\\dist\\index.js"],
      "env": {
        "HDW_API_KEY": "your-hdw-api-key"
      }
    }
  }
}

​
Cursor Integration

For Cursor IDE integration, add the MCP server to your workspace settings: 
{
  "mcp.servers": {
    "hdw": {
      "command": "node",
      "args": ["./node_modules/@horizondatawave/mcp-server/dist/index.js"],
      "env": {
        "HDW_API_KEY": "your-hdw-api-key"
      }
    }
  }
}

​
Validation

Test your configuration by running the MCP server in debug mode: 
node dist/index.js --debug --config ./hdw-config.json
You should see output similar to: 
[INFO] AnySite MCP Server starting...
[INFO] Configuration loaded successfully
[INFO] API connection verified
[INFO] 20+ tools registered
[INFO] MCP Server ready on stdio

​
Troubleshooting

​
Common Issues

  • Verify your API key is correct and active
  • Check that the key has proper permissions
  • Ensure the key isn’t expired
  • Check your internet connection
  • Verify the base URL is correct
  • Try increasing the timeout value
  • Enable rate limiting in configuration
  • Reduce requests per minute
  • Check your API plan limits

​
Debug Mode

Enable debug logging for troubleshooting: 
{
  "logLevel": "debug",
  "enableLogging": true
}
This will provide detailed information about API requests, responses, and internal operations.

​
Next Steps

⌘I