Developer

Connect your own systems and AI agents to a workspace. EVERJUST exposes a read/write API over your data and a built-in MCP server, so tools like Claude Code and Codex can work in your records. Every call runs as the key's user, so it is bounded by that user's permissions and logged.

  • External API

    Read and write your data from other systems over JSON-RPC.

    External API

  • AI agents & MCP

    Connect Claude Code or Codex to a workspace through the guarded MCP server.

    AI agents & MCP

  • Reference

    Every API surface and MCP tool, with schemas and the permission model.

    Reference

  • Platform architecture

    How EVERJUST is put together — multi-tenant, isolated databases per workspace.

    Architecture

What you can do

Your workspace is reachable two ways from outside. The external API reads and writes records over JSON-RPC from another system. The built-in MCP server lets an AI agent work in your data under a scoped, audited key. Both run as the key's user, so every call is bounded by that user's permissions. Start by giving the integration its own scoped account.

A note on the code namespace

EVERJUST is built on an open-source framework whose model and API names use the odoo namespace (for example model names like crm.lead and the JSON-RPC path). Examples in these docs use those real names so calls run as-is — the product is EVERJUST, the underlying framework keeps its original names.

Before you start

  • Give each integration its own integration or agent user and API key — never a shared admin login.
  • Scope that user to only the apps and records it needs. Every call is bounded by its permissions and written to the audit log.
  • For AI agents, the MCP server adds guardrails and an audit trail on top of the same API.

Last reviewed: 2026-07-21

← Move to a new domain Platform architecture →

Need a hand with this? company@everjust.co — a human answers.