English Français العربية

Exeris AI Bridge

Registre officiel Outils de développement

Read-only Exeris context for AI agents: ADRs, SDK contract, build output, kernel diagnostics.

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @exeris/ai-bridge
Claude Code 
claude mcp add exeris-ai-bridge -e 'EXERIS_PROJECT_ROOT=<EXERIS_PROJECT_ROOT>' -e 'EXERIS_DOCS_ROOT=<EXERIS_DOCS_ROOT>' -- npx -y @exeris/ai-bridge@0.8.0
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "exeris-ai-bridge": {
            "command": "npx",
            "args": [
                "-y",
                "@exeris/ai-bridge@0.8.0"
            ],
            "env": {
                "EXERIS_PROJECT_ROOT": "<EXERIS_PROJECT_ROOT>",
                "EXERIS_DOCS_ROOT": "<EXERIS_DOCS_ROOT>"
            }
        }
    }
}

Variables d'environnement

  • EXERIS_PROJECT_ROOT Root of your own project, for build-* and caps-*. Defaults to the nearest pom.xml at or above the working directory.
  • EXERIS_DOCS_ROOT An exeris-docs checkout. Without one, docs-* answers from the registry snapshot bundled in the package.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. @exeris/ai-bridge
  2. Installation
  3. Requirements
  4. Tools
  5. Configuration
  6. Troubleshooting
  7. Versioning
  8. Links
  9. License

@exeris/ai-bridge

Model Context Protocol server that gives AI agents the context of an Exeris application: what your build emitted, the SDK's authoring contract, the ADR registry, and a running kernel.

Every tool is a read. The bridge never writes to your project, never calls a model API, and runs as a separate process from the Java kernel. It is built for developers writing an application on Exeris, and works without a checkout of the ecosystem: the reference data it needs ships inside the package.

Installation

Run the server inside your project, so it finds your pom.xml.

Claude Code

claude mcp add exeris -- npx -y @exeris/ai-bridge

Claude Desktop: install exeris-ai-bridge-<version>.mcpb from the GitHub Releases. Desktop does not start the server inside a project, so set Project root in the extension's settings to use the build-* and caps-* tools.

Any other MCP client (Cursor, VS Code, Copilot): the command is npx -y @exeris/ai-bridge over stdio.

{
  "mcpServers": {
    "exeris": { "command": "npx", "args": ["-y", "@exeris/ai-bridge"] }
  }
}

The server is also listed in the MCP Registry as io.github.exeris-systems/ai-bridge.

Requirements

  • Node 20 or newer.
  • kernel-* only: JDK 25 or newer, and eu.exeris:exeris-kernel-diagnostics-cli in your local Maven repository, which a build of an Exeris application puts there.
  • No network at run time. The bridge reads artefacts already in ~/.m2 and never downloads.

Tools

Tool names are family-tool. All 31 are listed in every session; a family whose dependency is missing answers with a structured family_unavailable result naming the reason and the remedy.

FamilyAnswersTools
build-*What your last build emitted, which files codegen owns, what a build diagnostic meansbuild-list_domains, build-get_domain_metadata, build-explain_artefacts, build-get_detach_state, build-explain_diagnostic
caps-*The capability composition your build validatedcaps-list_capabilities, caps-describe_composition
sdk-*The SDK's annotations, deprecations, scoping rules and AST schema; whether your project pins a different SDKsdk-list_annotations, sdk-describe_annotation, sdk-list_deprecations, sdk-get_scoping_rules, sdk-get_ast_schema
docs-*The Exeris ADRs, the high-level architecture, the whitepaper and the decision templatesdocs-list_adrs, docs-get_adr, docs-search, docs-get_hla, docs-get_whitepaper, docs-get_template, docs-list_repos, docs-list_repo_docs, docs-get_repo_doc
kernel-*A running kernel's providers, bootstrap DAG, subsystems and JVM ergonomicskernel-list_providers, kernel-get_bootstrap_dag, kernel-describe_subsystem, kernel-get_jvm_ergonomics
lsp-*@ExerisDomain types and actions from the Studio language server, and a preview of a source edit as a difflsp-list_domains, lsp-describe_domain, lsp-list_actions, lsp-preview_mutation
bridge-*The server itself: version, bundled data, and why a family is unavailablebridge-version, bridge-health

docs-list_repos, docs-list_repo_docs and docs-get_repo_doc need a checkout of the Exeris repositories; the other docs-* tools answer from a registry snapshot bundled in the package. lsp-* needs a locally built exeris-platform-lsp, which publishes no runnable jar yet.

Configuration

Nothing needs setting for an application. Every variable is optional, and none can stop the server from booting.

VariableDefaultPurpose
EXERIS_PROJECT_ROOTnearest pom.xml above the working directoryThe project build-*, caps-* and sdk-* report on
EXERIS_MAVEN_REPO<localRepository> in ~/.m2/settings.xml, then ~/.m2/repositoryWhere published jars are looked up
EXERIS_KERNEL_VERSIONnewest release in the local repositoryThe diagnostics CLI version to launch
EXERIS_KERNEL_COMMAND / EXERIS_KERNEL_JARresolved from the local repositoryLaunch the kernel diagnostics CLI explicitly
EXERIS_LSP_COMMAND / EXERIS_LSP_JARnoneLaunch exeris-platform-lsp
EXERIS_LSP_WORKSPACEthe working directoryThe workspace the language server indexes
EXERIS_DOCS_ROOTthe bundled snapshotAn exeris-docs checkout to read instead
EXERIS_BRIDGE_MODEappcontributor for work on Exeris itself: source checkouts win over published jars

How each variable resolves, the launch ladder for the Java children, and the bundled reference data are described in the configuration reference.

Troubleshooting

Call bridge-health. It reports every family's state, with the reason and the remedy for each one that is unavailable, without starting any child process. bridge-version reports the build and the upstream releases its bundled data came from. The server also writes a one-line summary (mode=… docs=… lsp=… kernel=… build=… caps=…) to stderr, which MCP clients show in their logs.

Versioning

The package follows semver. Until 1.0, a minor release may change a tool's output shape; the release notes list every change a client may notice. At 1.0 the tool names and input schemas are frozen.

0.8.0 targets exeris-kernel 0.12.0, exeris-sdk 0.12.0 and exeris-tooling 0.10.0, all on Maven Central.

License

Apache-2.0

Questions fréquentes

Qu'est-ce que Exeris AI Bridge ?

Read-only Exeris context for AI agents: ADRs, SDK contract, build output, kernel diagnostics.

Comment installer Exeris AI Bridge ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add exeris-ai-bridge -e 'EXERIS_PROJECT_ROOT=<EXERIS_PROJECT_ROOT>' -e 'EXERIS_DOCS_ROOT=<EXERIS_DOCS_ROOT>' -- npx -y @exeris/ai-bridge@0.8.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Exeris AI Bridge ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Exeris AI Bridge est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient Exeris AI Bridge ?

Il est publié par exeris-systems. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.