---
title: "AI Integrations"
description: "Connect assistants and agent workflows to the Nimiq Developer Center with MCP, llms.txt, llms-full.txt, and the upcoming built-in assistant."
canonical_url: "https://nimiq.dev/ai"
---
# AI Integrations

> Connect assistants and agent workflows to the Nimiq Developer Center with MCP, llms.txt, llms-full.txt, and the upcoming built-in assistant.

Nimiq Developer Center ships AI-facing surfaces directly from the docs worker. That includes a built-in MCP server for tool-based retrieval, generated `llms.txt` files for model-friendly discovery, and a Docus assistant that can be enabled when the worker has an AI gateway key.

<u-page-section description="Use the integration that matches your assistant, IDE, or agent workflow." headline="Available Surfaces" title="Build against the docs directly">
<u-page-grid>
<u-page-card description="Connect Cursor, VS Code, or any MCP client to the built-in documentation server." icon="i-lucide-plug-zap" title="MCP Server" to="https://nimiq.dev/ai/mcp" variant="outline">



</u-page-card>

<u-page-card description="Give language models a compact or full-text index of the Developer Center." icon="i-lucide-file-text" title="llms.txt" to="https://nimiq.dev/ai/llms" variant="outline">



</u-page-card>

<u-page-card description="Prepare for the built-in docs assistant that will use the same MCP server when enabled." icon="i-lucide-sparkles" title="Assistant" to="https://nimiq.dev/ai/assistant" variant="outline">



</u-page-card>
</u-page-grid>
</u-page-section>

## What ships today

<table>
<thead>
  <tr>
    <th align="left">
      Surface
    </th>
    
    <th align="left">
      Status
    </th>
    
    <th align="left">
      Route
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td align="left">
      MCP server
    </td>
    
    <td align="left">
      Live
    </td>
    
    <td align="left">
      <code>
        /mcp
      </code>
    </td>
  </tr>
  
  <tr>
    <td align="left">
      Cursor deeplink
    </td>
    
    <td align="left">
      Live
    </td>
    
    <td align="left">
      <code>
        /mcp/deeplink
      </code>
    </td>
  </tr>
  
  <tr>
    <td align="left">
      VS Code deeplink
    </td>
    
    <td align="left">
      Live
    </td>
    
    <td align="left">
      <code>
        /mcp/deeplink?ide=vscode
      </code>
    </td>
  </tr>
  
  <tr>
    <td align="left">
      <code>
        llms.txt
      </code>
    </td>
    
    <td align="left">
      Live
    </td>
    
    <td align="left">
      <code>
        /llms.txt
      </code>
    </td>
  </tr>
  
  <tr>
    <td align="left">
      <code>
        llms-full.txt
      </code>
    </td>
    
    <td align="left">
      Live
    </td>
    
    <td align="left">
      <code>
        /llms-full.txt
      </code>
    </td>
  </tr>
  
  <tr>
    <td align="left">
      Docus assistant UI
    </td>
    
    <td align="left">
      Configured
    </td>
    
    <td align="left">
      App config enabled
    </td>
  </tr>
  
  <tr>
    <td align="left">
      Docus assistant backend
    </td>
    
    <td align="left">
      Future rollout
    </td>
    
    <td align="left">
      Requires <code>
        AI_GATEWAY_API_KEY
      </code>
    </td>
  </tr>
</tbody>
</table>

## Deployed URLs

On the public Developer Center deployment, these endpoints are available under `https://nimiq.com/developers`:

- `https://nimiq.com/developers/mcp`
- `https://nimiq.com/developers/llms.txt`
- `https://nimiq.com/developers/llms-full.txt`

The assistant will also run on the same deployment once the AI gateway key is configured.


## Sitemap

See the full [sitemap](https://nimiq.dev/sitemap.md) for all pages.