NexusRM / API and MCP

Built for scripts and agents too.

Everything in the UI is backed by a REST API. User-bound tokens let scripts, CI jobs and self-hosted AI agents use it under the same permissions and audit trail as the person who owns the token.

Request a demo NexusRM overview
01 / Tokens

Tokens that act as you.

Any user can create a personal API token with an optional expiry. The token is shown once; only its hash is stored. A request with the token is treated as that user, with the same roles, access filtering and audit entries.

  • Shown once, stored as a hash
  • Optional expiry
  • Same RBAC and audit as the owner
Token created dialog showing a new API token once, with a note about using it with the MCP server
02 / Administration

Every token, one list.

Administrators see every token with its owner, creation date, last use and expiry, and can revoke any of them immediately.

  • Owner, last used and expiry per token
  • Instant revocation
  • Self-service for every user
Administration list of all API tokens with owners, last-used dates, expiry and revoke actions
REST

OpenAPI document

The API publishes an OpenAPI document, so clients can be generated and endpoints explored.

AI

MCP server

An MCP server gives self-hosted AI agents typed tools to read and write projects, modules, objects, links and baselines.

Version history

Read-only git access

Clone a project's version history over HTTP with git, read-only, using the same token.

← All NexusRM features