Get information about the connected ONE Framework instance, including server version and the currently authenticated user. Use this to verify the connection is working and to see who you are authenticated as.

Execute a FETCH query against the ONE Framework instance. FETCH is a custom query language for retrieving, filtering, and aggregating data from one or more entities. Use this to: explore data, discover relationships, run reports, and understand the data model.

Syntax examples:

• FETCH entity (key, name) LIMIT 10 — basic retrieval

• FETCH entity (key, name) FILTER name CONTAINS "invoice" — filtered

• FETCH invoice (key, total) { invoice_item TO invoice (key, product_name) } — with linked entities

The query is always executed under the security privileges of the authenticated user.

List all entities in the ONE Framework instance. Returns entity names, their display names (where available), and whether they are public/customizable. Use this to discover what data is available before diving into specific entities. Tip: After listing entities, use get_entity_schema to see the full structure of an entity.

Get the full schema of an entity: its properties (fields with types and constraints) and its relationships to other entities. Use this to understand what data an entity holds and how it connects to other entities.

Returns:

• Properties: name, type, required flag, default value

• Relationships: name, type (OneToMany, ManyToOne), foreign entity, cascading rules

Retrieve a single entity record by its entity name and key (primary key). Returns the full record with all properties and child entities. Use this when you know exactly which record you need (e.g., entity 'user' with key 1).

To discover records, use fetch_query instead.

Create a new entity record. ⚠️ Requires Create permission on the entity.

Provide the entity name and a properties object with field values. Optionally include child entity records (nested creation).

Example: create a new catalog entry:

• entityName: "ui_catalog"

• properties: { "name": "my_catalog", "fetch": "FETCH ..." }

IMPORTANT: This creates real data. Double-check your values before submitting. There is NO delete functionality via this MCP — mistakes must be corrected manually.

Update an existing entity record. ⚠️ Requires Update permission on the entity.

Provide the entity name, primary key, and the properties to update. Only the properties you include will be changed — others remain unchanged. Optionally include child entity records.

IMPORTANT: This modifies real data. There is NO delete/undo via this MCP. Use get_entity_record first to see the current state before updating.

List all workflow definitions in the system, optionally with their event bindings. Each workflow may be bound to one or more entities and lifecycle events (onBeforeInsert, onAfterUpdate, etc.).

Use this to understand what business logic runs when data changes.

Get the full source code and metadata of a workflow by its key (primary key). Use list_workflows first to find the workflow key you need.

Returns the workflow name, source module, and the full source code.

Execute a named workflow method with arguments. Workflows are server-side scripts that contain business logic. Use this to trigger actions, run calculations, or invoke custom processes.

Before executing, use list_workflows to discover available workflows and get_workflow to read their source code and understand what they do.

Arguments are passed as key-value pairs matching the workflow's parameter names.