Veyo consists of an MCP Server for AI assistants, a Portal for project management, and an On-Premise edition for code security. Here's everything under the hood.
The cloud edition gives every user instant access to the official Business Central base application. When you need to analyse your own custom code, deploy the included on-premise edition — your source code never leaves your network.
Sign up and immediately query the official Business Central base application code. Every version, locale, and cumulative update — already ingested and ready.
Want to analyse your own AL and C/AL extensions? Deploy the included on-premise edition on your infrastructure. Your custom code is parsed and stored entirely within your network.
Combine cloud and on-premise data to run upgrade analysis between standard BC versions, or compare your custom code against the target you're upgrading to.
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
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 to produce a complete upgrade risk assessment for any object.
Map all external dependencies for an object. Surface breaking changes between versions or explore the complete dependency graph, including deep transitive analysis.
Find all subscribers wired to a specific event publisher. Trace the full execution chain from an event through every custom and standard handler.
Surface deprecated patterns, obsolete API usage, and risky upgrade tags across your codebase. Prioritises critical issues and includes solution suggestions when available.
Identify code patterns incompatible with Business Central SaaS. Essential for partners planning cloud migration — get a clear picture of what needs to change before you start.
Analyse table structures and relationships. Traverse foreign key chains to understand how entities connect. Includes field details, relations, and extension impacts on the data model.
Deep-dive into any table's field definitions. Get data types, properties, option strings, and validation rules — for the whole table or a specific field.
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. Never guess an object ID again.
Browse all procedures in an object at a glance, or inspect a specific one with the full body, variables, and parameters. Covers procedures, triggers, and events.
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 any object. Discover integration points your extensions can subscribe to — across one object or your entire codebase.
Analyse fields displayed on a page, or reverse-lookup: find all pages that show a specific table column. Go from data to UI or UI to data in seconds.
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.
The MCP server authenticates via API key, scoped to specific projects. A key can only access the projects it's been assigned to.
Generate, rotate, and revoke keys at any time through the Portal. Each key tracks usage so you always know what's active.
Install the package, generate an API key in the Portal, add the config to your AI client.
The Veyo Portal is where you set up projects, connect repositories, monitor ingestion, manage credentials, and control team access.
Step-by-step project creation: name your project, connect source and target repositories, assign credentials, and trigger your first ingestion.
Each project supports multiple repositories with distinct roles: source version, target version, and custom extensions. Compare any combination.
Connect GitHub and Azure DevOps repositories using encrypted PATs. Credential resolution cascades: repository, project, then user scope.
Watch ingestion progress live via Server-Sent Events. Track job status, file counts, error rates, and batch completion across all your projects.
Generate, rotate, and revoke API keys scoped to specific projects. Track usage with last-used timestamps and request counts.
Invite team members and assign roles per project: Owner, Admin, Member, or Viewer. Control who can ingest, query, and manage settings.
Name your project and choose your organisation. The wizard guides you through each step with validation and helpful defaults.
Point to your GitHub or Azure DevOps repos. Assign each as source (current version) or target (upgrade version). Add credentials — encrypted at rest with Fernet.
Trigger ingestion and watch progress in real-time. The system detects changes per-commit, downloads only modified files, and parses them through 20+ extractors.
See every ingestion job in real-time: pending, downloading, processing, completed, or failed. Jobs stream updates via SSE so the dashboard is always current.
Each project card shows connected repositories, last ingestion timestamp, file counts, and active API keys. Drill into any project for full configuration and history.
PATs and API tokens are encrypted with Fernet symmetric encryption. Credentials are scoped and resolved hierarchically: repository > project > user.
Organisation-level system repositories make standard Business Central base application code available to all projects. Set up once, share across your team.
Every project gets a unique collection prefix that namespaces all 12 semantic tables. Project A cannot see Project B's data — even within the same organisation.
Organisations group users and projects under a single billing and management boundary. Members can be assigned different roles per project within the org.
System repositories (shared BC base application code) are scoped to the organisation level, so all projects in an org can reference the same standard code without duplicating ingestion.
A hub-and-spoke design with the Orchestrator at the centre. PostgreSQL is the data store and the job queue — no external brokers.
Stop working around hallucinations. Start building with confidence.