Veyo MCP connects any MCP-compatible AI assistant directly to your parsed Business Central codebase. 14 specialised query tools. Exact, structured data. Zero hallucinations.
Compatible with
The MCP server sits between your AI assistant and the Veyo Orchestrator. It translates natural tool calls into precise semantic queries.
Install the Veyo MCP package globally. It ships as a single Node.js executable that connects to your Veyo instance via API key.
Point your MCP client at the Veyo server. Provide your API key and project ID. Configuration takes one line in your client's JSON config.
Your AI assistant automatically discovers all 14 tools and uses them contextually. Ask questions in natural language — the tools handle the structured query.
Each tool is designed for a specific class of query. Your AI discovers them automatically via MCP and uses the right one for each question.
The most powerful tool. Runs event subscription analysis, dependency checks, and SaaS incompatibility scans in a single call. Pass an object type and name/ID to get a complete upgrade risk assessment.
Map all external dependencies for an object. Filter to show only breaking changes between versions, or get the complete dependency graph. Supports scan_dependencies for deep transitive analysis.
Find all subscribers wired to a specific event publisher. Trace the execution chain from an event through all custom and standard handlers. Filter by event name for precision.
Surface deprecated patterns, obsolete API usage, and risky upgrade tags. Filter by severity to focus on critical issues first. Includes solution suggestions when available.
Identify code patterns incompatible with Business Central SaaS. Essential for partners planning cloud migration. Filter by object type, name pattern, or specific objects.
Analyse table structures and relationships. Traverse foreign key chains at configurable depth. Includes field details, relations, and extension impacts on the data model.
Deep-dive into a specific table's field definitions. Get data types, properties, option strings, and validation rules. Filter to a specific field by name or ID.
Find all extensions targeting a base object: TableExtensions, PageExtensions, EnumExtensions, and more. Understand what custom code modifies standard behaviour.
Search for Business Central objects by name with fuzzy matching. Resolve names to IDs and types. Set max_results and min_score to control precision.
Two modes: browse (compact list of all procedures in an object) and inspect (full body, variables, parameters for a specific procedure). Filter by type: procedure, trigger, or event.
Find ObsoleteState and ObsoleteReason tags for objects and fields. Track what Microsoft has marked for deprecation and the timeline for removal.
List all event publishers defined in a specific object. Discover integration points your extensions can subscribe to. Supports wildcard search across objects.
Analyse fields displayed on a page, or reverse-lookup: find all pages that show a specific table column. Filter by source table for precise results with common field names.
Retrieve the full hierarchical layout tree for any page. Returns the nested structure of areas, groups, repeaters, and field controls with their AL properties.
Every tool accepts a version_target parameter: either "source" (your current version) or "target" (what you're upgrading to).
This means your AI can compare procedure signatures across versions, find what changed in a table between BC22 and BC24, or identify which event publishers were removed in the target.
With the on-premise edition, your LLM also gets access to the standard Business Central base application code for the exact locale, version, and cumulative update — not just your custom extensions.
The MCP server uses API key authentication scoped to specific projects. On top of that, a session attestation layer using HMAC-SHA256 signing ensures that every query comes from a legitimate client.
Sessions automatically expire after 5 minutes of inactivity. Heartbeats keep active sessions alive. API keys can be rotated at any time through the Portal.
Each API key tracks usage: last used timestamp and request count. Scoping ensures a key can only access the projects it's been assigned to.
Install the package, generate an API key in the Portal, add the config to your AI client.
Log in to the Veyo Portal, navigate to your project's API Keys page, and generate a new key. The key is scoped to the project and tracks usage automatically. You'll also find your Project ID on the project settings page.
Stop working around hallucinations. Start building with confidence.