Skip to main content
Neo Docs MCP Hero The Neo Docs MCP server gives AI coding assistants direct access to the latest Neo documentation. Connect it once, then ask your assistant about widgets, theming, utilities, release notes, and migration paths while you work.

What is MCP?

MCP (Model Context Protocol) is a standard way for AI tools to read external context. The Neo Docs MCP exposes the published Neo docs at https://neo.tvk.company/mcp, so your assistant can answer with the same source material you would otherwise search manually.
We recommend adding the server per project. This keeps the Neo context close to the codebase that needs it and avoids loading unnecessary tools in unrelated projects.

Connect the MCP

1

Open your project MCP settings

Create or open .cursor/mcp.json in your project root.
2

Add the Neo Docs server

{
  "mcpServers": {
    "neo-docs": {
      "url": "https://neo.tvk.company/mcp"
    }
  }
}
3

Enable the server

Reload Cursor if needed, then enable neo-docs when Cursor detects the new MCP server.

What it can help with

With the Neo Docs MCP server enabled, your AI assistant can:

Answer Neo questions

Ask about widgets, layouts, utilities, theming, properties, and examples without leaving your editor.

Generate Neo code

Ask for components or full screens that follow Neo naming, widget structure, and usage patterns.

Follow current docs

Let your assistant reference the latest docs instead of relying only on model training data.

Handle migrations

Ask your assistant to read release notes and apply documented migration steps across your codebase.

Usage

After connecting the MCP, write natural prompts in your AI assistant:
Example prompts
"Which Neo widget should I use for a searchable picker?"
"Create a settings screen using Neo form components."
"Show me the required setup for Neo theming."
"Migrate this file to the latest Neo release notes."

Troubleshooting

If the server is not available in your assistant:
  1. Check that mcp.json is valid JSON.
  2. Confirm the file is in the correct project-level folder for your tool.
  3. Reload or restart the IDE after changing the config.
  4. Open your tool’s MCP or tools settings and make sure neo-docs is enabled.
  5. Check your IDE logs for MCP connection errors.
Last modified on May 12, 2026