Skip to main content
Glama
ONE-MCP

ONE-MCP

by alexxcpr

MCP ONE

MCP server for the ONE Framework ERP — gives Claude autonomous access to explore your data model, run queries, and understand business logic.

Setup

1. Install dependencies

npm install

2. Configure

Copy .env.example to .env and fill in your instance details:

cp .env.example .env
ONE_URL=https://your-instance.oneerp.ro
ONE_API_KEY=your-api-key-here

3. Register with Claude Code (project-level)

The project already has a .mcp.json file. Update it with your credentials, then restart Claude Code.

Or manually add a project-level MCP server:

// .mcp.json (project root)
{
  "mcpServers": {
    "one": {
      "command": "npx",
      "args": ["tsx", "src/index.ts"],
      "cwd": "D:\\ONE-Projects\\MCP-ONE",
      "env": {
        "ONE_URL": "https://your-instance.oneerp.ro",
        "ONE_API_KEY": "your-api-key"
      }
    }
  }
}

Related MCP server: Business Central MCP Workshop Server

Tools

Discovery & Reading

Tool

Description

get_instance_info

Server version + authenticated user

fetch_query

Execute FETCH queries (filter, link, aggregate)

list_entities

Discover all entities in the system

get_entity_schema

Full schema: properties + relationships

get_entity_record

Read a single record by entity name + key

Write Operations

Tool

Description

create_entity_record

Create a new record ⚠️

update_entity_record

Update an existing record ⚠️

Workflows

Tool

Description

list_workflows

Workflow definitions + event bindings

get_workflow

Workflow source code + metadata

execute_workflow

Run a workflow method with arguments

Security

  • No DELETE tool — the MCP does not expose a delete operation

  • API key permissions are inherited from the associated user's roles — ensure the user has only View + Create/Update access in ONE

  • All FETCH queries run under the security context of the authenticated user

  • Create/Update tools require explicit user confirmation (MCP permission model)

Development

npm run dev        # Run with tsx (stdio transport)
npm run build      # Compile TypeScript
npm run typecheck  # Type checking only

Available Tools

10 tools
create_entity_recordA

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.

Inputs: entityName (required), properties (required), children.

execute_workflowA

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.

Inputs: method (required), workflowName (required), args.

fetch_queryA

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.

Inputs: query (required).

get_entity_recordA

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.

Inputs: key (required), entityName (required).

get_entity_schemaA

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

Inputs: entityName (required).

get_instance_infoA

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.

Inputs: no named parameters.

get_workflowA

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.

Inputs: key (required).

list_entitiesA

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.

Inputs: limit, filter.

list_workflowsA

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.

Inputs: limit, entityFilter.

update_entity_recordA

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.

Inputs: key (required), entityName (required), properties (required), children.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: instance info, querying, entity metadata, entity records, and workflows. Even overlapping tools like fetch_query and get_entity_record are clearly differentiated by purpose (discovery vs. direct lookup).

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (get_, list_, create_, update_, execute_), but 'fetch_query' deviates from the get_/list_ convention. Entity-specific tools share a consistent 'get_entity_*' prefix, and workflow tools follow 'list/get/execute_workflow'.

    Tool Count5/5

    With 10 tools, the set is well-scoped for the server's purpose: exploring the data model, querying data, managing entities, and executing workflows. No tool feels redundant, and the count supports a complete workflow without being bloated.

    Completeness4/5

    The tool surface covers metadata discovery, querying, record creation/update, and workflow execution. The explicit lack of delete functionality is a notable gap, but it is acknowledged and likely intentional for safety. Read and update paths are fully covered, so agents can accomplish most tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enables AI assistants like Claude to interact with Odoo ERP systems through natural language, allowing users to search, create, update, and manage business data in their Odoo instance.
      39,303 PyPI
      416
      Mozilla Public 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that integrates with Microsoft Dynamics 365 Business Central, enabling querying of customers, items, and sales orders through natural language commands in Claude Desktop.
      10
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A remote MCP server that connects Claude to Acumatica ERP, enabling per-user OAuth-authenticated access to over 40 tools for querying and managing Acumatica data with role-based security and sensitive field redaction.
      Apache 2.0