Veyo MCP - Model Context Protocol Server for NAV/Business Central

Veyo MCP is an MCP (Model Context Protocol) server that provides Business Central/NAV codebase analysis tools directly to Claude Desktop, Claude Code, and Cursor. It connects to a Veyo API server that manages your pre-ingested code analysis data.

Quick Start

Claude Desktop

Add this configuration to your Claude Desktop config file:

• Windows: %APPDATA%\Claude\claude_desktop_config.json
• macOS/Linux: ~/.config/Claude/claude_desktop_config.json

For macOS/Linux:

{
  "mcpServers": {
    "vela": {
      "command": "npx",
      "args": ["-y", "veyo-mcp"],
      "env": {
        "VELA_API_URL": "http://your-server:8000",
        "VELA_API_KEY": "your-api-key-here"
      }
    }
  }
}

For Windows:

{
  "mcpServers": {
    "vela": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "veyo-mcp"],
      "env": {
        "VELA_API_URL": "http://your-server:8000",
        "VELA_API_KEY": "your-api-key-here"
      }
    }
  }
}

Then reload MCP configuration in Claude Desktop.

Claude Code

Add the MCP server using the mcp add command:

claude mcp add veyo-mcp npx veyo-mcp --scope user

Then configure the environment variables in your project's .claude/mcp.json or globally in ~/.claude/mcp.json:

For macOS/Linux:

{
  "mcpServers": {
    "veyo-mcp": {
      "command": "npx",
      "args": ["-y", "veyo-mcp"],
      "env": {
        "VELA_API_URL": "http://your-server:8000",
        "VELA_API_KEY": "your-api-key-here"
      }
    }
  }
}

For Windows:

{
  "mcpServers": {
    "veyo-mcp": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "veyo-mcp"],
      "env": {
        "VELA_API_URL": "http://your-server:8000",
        "VELA_API_KEY": "your-api-key-here"
      }
    }
  }
}

Cursor

Add this configuration to your Cursor MCP settings file (usually ~/.cursor/mcp.json or in your project settings):

For macOS/Linux:

{
  "mcpServers": {
    "vela": {
      "command": "npx",
      "args": ["-y", "veyo-mcp"],
      "env": {
        "VELA_API_URL": "http://your-server:8000",
        "VELA_API_KEY": "your-api-key-here"
      }
    }
  }
}

For Windows:

{
  "mcpServers": {
    "vela": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "veyo-mcp"],
      "env": {
        "VELA_API_URL": "http://your-server:8000",
        "VELA_API_KEY": "your-api-key-here"
      }
    }
  }
}

Then restart Cursor to load the MCP server.

How it works:

• npx automatically downloads and runs the latest version from npm
• -y flag auto-confirms the installation
• No manual installation or updates needed

Note for Windows users: Windows requires the cmd /c wrapper because npx is a batch file (.cmd) that cannot be executed directly. The cmd /c command tells Windows to run the batch file through the command interpreter.

Configuration

Environment Variables

All configuration is passed through environment variables in your MCP configuration:

| Variable | Required | Description | Example | |----------|----------|-------------|---------| | VELA_API_URL | Yes | The URL of your Veyo API server | http://your-server:8000 | | VELA_API_KEY | Yes | Your API authentication key | your-api-key-here | | VELA_PROJECT_ID | No | Project identifier (scopes queries to a specific project) | my-bc-project |

Available Tools

The MCP server exposes Business Central/NAV analysis tools:

Upgrade & Compatibility Analysis

• consolidated_upgrade_report - Comprehensive upgrade analysis combining event subscriptions, dependencies, and SaaS incompatibilities
• upgrade_tag_explorer - Find upgrade/obsolete tags for objects and fields
• deprecated_code_explorer - Identify deprecated patterns and risky upgrade tags
• dependency_explorer - Analyze dependencies and validate against target version for breaking changes
• event_flow_tracker - Track event publisher-subscriber chains and identify breaking subscriptions
• saas_incompatibility_explorer - Find SaaS-incompatible code patterns for migration planning

Code Analysis

• event_publisher_explorer - Find event publishers in objects by ID or wildcard pattern
• procedure_lister - List all procedures in an object with signatures, with optional inspect mode for full procedure body
• extension_finder - Find table/page extensions for base objects
• object_name_resolver - Resolve object names to IDs with fuzzy matching

Data & Structure Analysis

• table_field_analyzer - Analyze table structures with complete field definitions, data types, and properties
• data_model_rebuilder - Rebuild data models and analyze table relationships

Page Analysis

• page_field_analyzer - Analyze page fields and their source table bindings, or reverse-lookup which pages display a given field
• page_layout_tool - Retrieve the full hierarchical layout tree for a page (areas, groups, repeaters, controls)

Usage Examples

Once configured, you can ask Claude:

Upgrade Analysis

• "Run a comprehensive upgrade analysis for Codeunit 50099"
• "What are the upgrade risks for Table 50075?"
• "Find upgrade tags for Table 36 field Amount"
• "What event subscriptions will break after upgrade in Codeunit 50036?"

Code Analysis

• "Show me all dependencies for COD50099"
• "Find deprecated code patterns in the source version"
• "What event publishers exist in Codeunit 80?"
• "List all procedures in Codeunit 50099"

Data & Page Structure

• "Analyze the Customer table structure"
• "Show me complete field definitions for Table 50075"
• "What fields are displayed on the Sales Order page?"
• "Which pages show the 'Amount' field from the Sales Line table?"

Troubleshooting

Common Issues

MCP server won't start:

• Verify Node.js 18+ is installed: node --version
• Check the API server is running at the configured URL
• Review Claude Desktop logs for connection errors

Tools returning errors:

• Verify VELA_API_URL is correct and accessible
• Check VELA_API_KEY is valid
• Ensure the Veyo API server is running

Can't connect to API:

• Check firewall settings if the API server is on a different machine
• Verify the API server is listening on the correct port

Requirements

• Node.js 18+ (for native fetch support)
• Running Veyo API server with ingested BC/NAV codebase data