Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.dzap.io/llms.txt

Use this file to discover all available pages before exploring further.

The DZap MCP server exposes DZap AI capabilities through a tool-based interface for MCP-compatible clients. Connect once; the client can discover and call DZap tools through the standard MCP flow.

​
What you get

  • Discovery — clients list available tools and inspect their schemas.
  • Invocation — clients call tools with structured inputs.
  • Safety — sensitive actions are clearly marked and gated.
  • Observability — responses are structured enough for clients to explain what happened.

​
When to use it

Claude Desktop and similar

Connect DZap to an MCP-capable assistant and let it call tools directly.

Internal copilots

Curated subset of DZap tools for support, ops, research, or strategy.

Custom agent stacks

MCP as the first integration layer before you decide on a tighter contract.

Cursor IDE

DZap tools alongside your code editor.

​
Tool families

The MCP server exposes tools across several domains:
  • Asset and token lookup
  • Prices and balances
  • Routes and quotes
  • DeFi positions and pool context
  • Transaction build and simulation
  • Docs and knowledge retrieval
  • Analytics and sentiment helpers
See Tool Categories for the full breakdown.

​
Conceptual request flow

User
  ↓ asks a DeFi question
MCP Client (Claude Desktop / Cursor / your agent)
  ↓ tools.list / tool call
DZap MCP Server (https://ai.dzap.io/sse)
  ↓ executes selected tool
DZap Tools
  ↓ structured result
MCP Client → User

​
Connection

The DZap MCP server is hosted at https://ai.dzap.io/sse (Server-Sent Events transport). Most clients use the mcp-remote helper to bridge their config to the remote endpoint: 
{
  "mcpServers": {
    "DZapAI": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://ai.dzap.io/sse"
      ]
    }
  }
}
Per-client paths and exact format are in the dedicated pages.

​
What’s read-only vs execution-sensitive

Tools split into two classes:
ClassExamplesConfirmation
Readbalances, prices, positions, routesnone
Execution-sensitivebuild, simulate, performgated by client + runtime
For the security model, see Safety & Execution.

​
Next

Claude Desktop

Connect in 60 seconds.

Custom clients

Integrate into your own agent runtime.