MCP Setup

Client Configuration

ALGOFLOW exposes MCP tools for challenge signing, deployment, and deployment history retrieval.

Use one shared MCP profile per machine and keep secret values only in local config.

{
  "preferences": {
    "coworkWebSearchEnabled": true,
    "coworkScheduledTasksEnabled": false,
    "ccdScheduledTasksEnabled": false
  },
  "mcpServers": {
    "w3deploy": {
      "command": "w3deploy-mcp",
      "env": {
        "W3DEPLOY_API_BASE": "https://api.yourdomain.com",
        "W3DEPLOY_WALLET_ADDRESS": "<YOUR_WALLET_ADDRESS>",
        "W3DEPLOY_API_TOKEN": "<YOUR_PRODUCTION_JWT>",
        "W3DEPLOY_EVM_PRIVATE_KEY": "<YOUR_PRIVATE_KEY_IF_AUTOSIGN>"
      }
    }
  }
}

Available Tools

• •connect_w3deploy_mcp: validates backend connectivity.
• •request_deploy_challenge: returns message to sign.
• •deploy_code_to_ipfs: uploads files and creates deployment.
• •get_deployment_history: returns latest and historical releases.

Best Practices

• •Use production API URL, not localhost, for shared environments.
• •Rotate API tokens regularly and scope by user/workspace.
• •Never commit private keys to repository files.
• •Prefer challenge signing over long-lived signing keys when possible.