Skip to content
Agentmart
Submit a tool

Exeris AI Bridge

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

Connector by exeris-systems · GitHub account verified by the MCP Registry

IndexedApache-2.0Local (stdio)
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/exeris-systems-ai-bridge

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
24 read · 2 write · 0 delete
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 26

Read from the source code; the running server may list different tools.

Read 24 · Look things up without changing anything.

  • caps-describe_composition
  • caps-list_capabilities
  • docs-get_adr
  • docs-get_hla
  • docs-get_repo_doc
  • docs-get_template
  • docs-get_whitepaper
  • docs-list_adrs
  • docs-list_repo_docs
  • docs-list_repos
  • docs-search
  • kernel-describe_subsystem
Show 12 more tools
  • kernel-get_bootstrap_dag
  • kernel-get_jvm_ergonomics
  • kernel-list_providers
  • lsp-describe_domain
  • lsp-list_actions
  • lsp-list_domains
  • lsp-preview_mutation
  • sdk-describe_annotation
  • sdk-get_ast_schema
  • sdk-get_scoping_rules
  • sdk-list_annotations
  • sdk-list_deprecations

Write 2 · Create, change, send or run things.

  • bridge-health
  • bridge-version

Secrets and settings it asks for

Other settings (environment variables or headers).

  • EXERIS_DOCS_ROOT
  • EXERIS_PROJECT_ROOT

Files it touches

  • Any path the agent passes to its tools

Tools (26)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • bridge-health

    Report which tool families can serve requests and why the others cannot. Each family carries its state and, when unavailable, the reason and the remedy. Families backed by a child process also report that process's current state — without starting it. Call this first when a tool returns 'family_unavailable'.

  • bridge-version

    Identify this MCP server: package name and version, the Node runtime it is running on, which persona mode it resolved to, and what bundled reference data it carries. Use it to confirm which bridge build an answer came from, and which upstream release that data reflects.

  • caps-describe_composition

    Report the composition stamp from cap-manifest.json: whether the capability graph validated, the composition version, and the content binding digest, alongside the manifest schema version, the module count and initOrder. Answers 'is this build's composition trustworthy, and which build is it'. A project with no capabilities returns a present:false answer, not an error.

  • caps-list_capabilities

    List the capability modules composed into this project, from the build-time cap-manifest.json: each module's qualified name, the services it provides with their versions, and which module owns the lifecycle. Also returns initOrder exactly as the manifest states it. A project with no capabilities returns an empty list, not an error.

  • docs-get_adr

    Fetch the full markdown body of a specific ADR by number. Resolves the link from the registry against the ecosystem root, so cross-repo ADRs (those whose content lives in a sibling repo) are read from their authoritative source.

  • docs-get_hla

    Fetch the High-Level Architecture document (high-level-architecture.md) from exeris-docs. Canonical narrative of the three-tier model.

  • docs-get_repo_doc

    Fetch a specific markdown document from `<repo>/docs/<path>`. Use `docs-list_repo_docs` to discover valid paths.

  • docs-get_template

    Fetch one of the canonical decision-doc templates from exeris-docs/templates/. Three kinds: ADR (decision made), RFC (multi-option strategic question), RESEARCH (falsifiable hypothesis, lab-notebook shape).

  • docs-get_whitepaper

    Fetch the B2B technical whitepaper (b2b-technical-whitepaper.md) from exeris-docs.

  • docs-list_adrs

    List all ADRs from the Exeris ecosystem registry. Each entry carries number, title, owning repo, scope, visibility, status, and link. Optional `status` filter narrows the result by the first token of the status cell (e.g. 'accepted', 'proposed', 'superseded', 'reserved').

  • docs-list_repo_docs

    List markdown documents under `<repo>/docs/**` for an Exeris sibling repo. The `adr/` subdirectory is excluded — those are the registry's territory and reachable via `docs-list_adrs` / `docs-get_adr`. Use `docs-list_repos` to discover valid repo names.

  • docs-list_repos

    List sibling Exeris repos under the ecosystem root that publish a `docs/` directory. Returned names are usable as `repo` input to `docs-list_repo_docs` and `docs-get_repo_doc`.

  • docs-search

    Search exeris-docs for a literal substring (case-insensitive). Returns the path, line number, and snippet of each match, capped by maxResults. Optional pathFilter narrows to files whose docs-root-relative path contains the substring (e.g. 'adr/' to scope to ADR files). Scope is the docs root only; cross-repo content is reachable via get_adr.

  • kernel-describe_subsystem

    Detail for a single kernel subsystem by name (e.g. memory, crypto, persistence, graph, transport, events, flow, http, security).

  • kernel-get_bootstrap_dag

    Snapshot of the kernel bootstrap dependency DAG — nodes (subsystems) with their phase, declared dependencies, and running state.

Show 11 more tools
  • kernel-get_jvm_ergonomics

    What the JVM running the kernel actually resolved at startup: selected GC, max/committed heap, visible processors, and the container limits it detected (cgroup CPU quota/period, memory cap, cpuset) plus large-page, CDS and AOT-cache state. Null fields mean the kernel could not determine that value. A kernel that does not implement this answers a snapshot with gcName 'unknown' and -1 byte counts.

  • kernel-list_providers

    List all SPI providers registered with the running kernel, including driver origin (community/enterprise priority).

  • lsp-describe_domain

    Return the source-model description of an @ExerisDomain type: fields, actions, relationships, generated artefacts, and the `sourceDigest` that `lsp-preview_mutation` takes as its concurrency token.

  • lsp-list_actions

    List all @Action methods across the workspace, with their owning @ExerisDomain.

  • lsp-list_domains

    List all @ExerisDomain types known to the active LSP session.

  • lsp-preview_mutation

    Preview how the SDK's canonical writer would change an @ExerisDomain source file for one mutation, applied in memory. Returns `{ result, sourcePath, diff }`: a unified diff and the SDK outcome in `result.outcome` — SUCCESS, CONFLICT (the source drifted from the baseline; the result carries baseline, current and intended values), VALIDATION_ERROR, or NO_BASELINE. Nothing is written: apply the diff with your own file tools. For a stale-free preview, pass the entity's last-emitted metadata as `baselineJson` and the `sourceDigest` from `lsp-describe_domain` as `concurrencyToken`.

  • sdk-describe_annotation

    Describe a specific Exeris SDK annotation: simple and qualified name, owning package rationale, targets, retention, purpose, detailed description, all attributes (with types, defaults, required-ness, descriptions, and deprecations), and annotation-level deprecation status.

  • sdk-get_ast_schema

    Get JSON Schema for the Exeris build-time DomainMetadata AST and sibling records. If 'definition' is omitted, returns the top-level schema envelope, reader requirements (such as Jackson 3 constraints), and definition list. If 'definition' is specified (e.g. 'DomainMetadata', 'FieldMetadata', 'ActionMetadata'), returns the schema definition for that specific record.

  • sdk-get_scoping_rules

    Get canonical authoring contract scoping rules for Exeris SDK annotations (including @Field vs @Validation split, FieldMetadata as single AST carrier per ADR-054, derived SQL NOT NULL and API not-blank generator semantics, form lifecycle scoping, deprecations, and sibling vs nested form trap). Supports optional filtering by rule ID or query string.

  • sdk-list_annotations

    List Exeris SDK annotations from the authoring contract: name, qualified name, package, targets, retention, and purpose. Supports optional filtering by package (e.g. 'system', 'security', 'capability', or full package name), target (e.g. 'METHOD', 'TYPE', 'FIELD'), or query string.

  • sdk-list_deprecations

    List all deprecated Exeris SDK annotations and attributes across the authoring contract, including replacement guidance, since version, and forRemoval status. Supports filtering by package or forRemoval only.

Signals

Stars
0
Forks
0
Open issues
0
Weekly downloads
45
Last commit
Oct 21, 2026 (8 days ago)
Last release
Oct 21, 2026 (8 days ago)
Last package publish
Oct 21, 2026 (8 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.exeris-systems/ai-bridge
Version
0.8.0
Auth
No auth
Packages
npm @exeris/ai-bridge
License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Cite this page

Exeris AI Bridge MCP server. Agent Mart. https://agentmart.dev/connectors/exeris-systems-ai-bridge (last updated 2026-10-24)