Claude Code

Claude Code talks to MCP servers via HTTP. Add the dLazy server with the claude mcp add CLI, then restart Claude Code:

claude mcp add --transport http dlazy \
  --url https://dlazy.com/mcp \
  --header "Authorization: Bearer sk-xxxx"

This writes to your Claude Code MCP config. The equivalent JSON shape:

{
  "mcpServers": {
    "dlazy": {
      "type": "http",
      "url": "https://dlazy.com/mcp",
      "headers": {
        "Authorization": "Bearer sk-xxxx"
      }
    }
  }
}

Calling Tools

Inside Claude Code, every dLazy tool is named mcp__dlazy__<cli_name>. Examples:

• mcp__dlazy__gpt-image-2
• mcp__dlazy__veo-3.1
• mcp__dlazy__script

Narrow the Tool Set

Claude Code exposes whichever tools the MCP server registers — which can be controlled by the ?models= query param:

claude mcp add --transport http dlazy-images \
  --url 'https://dlazy.com/mcp?models=gpt-image-2,seedream-4.5,banana-pro' \
  --header "Authorization: Bearer sk-xxxx"

This is useful when you want different MCP servers (one per task) connected at the same time without overflowing the agent's tool list.

Async Tools

Async tools wait by default on the MCP side, so Claude Code sees one synchronous reply with the final result. If you need to fire-and-forget, run the CLI from a Bash tool call instead.