Use DerivaDEX Docs with AI Tools

​

Connect an AI tool to the public docs

1. Start with the public docs URL: https://docs.derivadex.com.
2. Use the Mintlify MCP endpoint at https://docs.derivadex.com/mcp if your AI tool supports MCP connections.
3. Use the published skill discovery endpoints if your AI tool supports skill.md or skills registries:
   • https://docs.derivadex.com/skill.md
   • https://docs.derivadex.com/.well-known/skills/index.json
   • https://docs.derivadex.com/.well-known/agent-skills/index.json
4. Ask the tool to stay inside public DerivaDEX docs and to keep transport and visibility explicit.

​

Fastest install paths from the docs site

• Copy MCP server URL to copy the exact public /mcp endpoint
• Copy MCP install command when your tool supports a generic MCP install command
• Connect to Cursor for the shortest Cursor install path
• Connect to VS Code for the shortest VS Code install path

​

Connect common MCP clients

​

Claude

1. Open Claude settings and go to Connectors.
2. Add a custom connector named DerivaDEX Docs.
3. Use the URL https://docs.derivadex.com/mcp.
4. In chat, attach the connector before asking a docs question.

​

Claude Code

claude mcp add --transport http DerivaDEXDocs https://docs.derivadex.com/mcp

​

Cursor

1. If the docs page exposes Connect to Cursor, use it first.
2. Otherwise open the command palette.
3. Run Open MCP settings.
4. Select Add custom MCP. This opens mcp.json.
5. Add the server:

{
  "mcpServers": {
    "DerivaDEXDocs": {
      "url": "https://docs.derivadex.com/mcp"
    }
  }
}

6. In Cursor chat, ask What tools do you have available? and confirm the DerivaDEX Docs server appears.

​

VS Code

1. If the docs page exposes Connect to VS Code, use it first.
2. Otherwise create or update .vscode/mcp.json:

{
  "servers": {
    "DerivaDEXDocs": {
      "type": "http",
      "url": "https://docs.derivadex.com/mcp"
    }
  }
}

3. Use the public MCP endpoint above for public docs only.

​

What the public MCP server can and cannot see

• The public /mcp endpoint returns indexed public pages only.
• Mintlify indexes pages in the public docs navigation by default. Hidden pages or noindex pages may not appear in MCP search results.
• Internal repo workflow docs are not part of this public MCP surface.
• Authenticated Mintlify MCP surfaces such as /authed/mcp are outside this public-docs guide.

​

Use the right public route

• Start at Getting Started for orientation by audience.
• Use Tutorials for guided first-success workflows.
• Use How-to Guides for specific tasks.
• Use Reference for exact limits, fields, and lifecycle semantics.
• Use Explanation for system-design and mechanism context.
• Use API Reference when transport and contract details matter.

​

Prompting rule for better answers

• stay inside public DerivaDEX docs unless you explicitly provide another source
• distinguish REST from realtime rather than collapsing them into one API
• name whether a route is tutorial, how-to, reference, or explanation when that matters
• treat restricted or product-specific surfaces as boundary summaries unless the public docs say otherwise

​

Keep boundaries explicit

• Public MCP and skill endpoints expose indexed public docs, not internal repo workflow docs.
• Restricted and product-specific API families are documented with explicit visibility labels, but their private/generated spec bundles are not part of the public docs surface. Do not treat them as public-by-default, and do not assume AI discovery endpoints will enumerate them as if they were public REST or realtime contracts.
• Historical or redirected routes may still resolve, but the hierarchy-first public docs sections are the active authority.

​

Verify before acting

• exact limits or formulas
• error and retry behavior
• request-signing or encryption details
• governance or compliance statements

​

When AI answers are not enough

1. Check FAQ.
2. Run Troubleshooting.
3. Use Support Channels when you need a docs clarification or escalation.