تحميل

Actualog MCP

Actualog MCP lets a supported agent application read current Actualog information and use the operations you are permitted to authorize. You connect the agent to the supplied MCP server address for your Actualog environment and sign in with your own account.

Who can connect

The current pilot supports eligible Application Admin accounts and the prepared local Codex client. Access for other roles is planned. Company membership alone does not currently enable MCP access. Work, hosted clients and other agent applications have not been accepted by this pilot.

Start with Connect your agent to Actualog. If your client is already configured, use Manage your MCP connection to pause, sign out, reconnect or investigate a problem.

How access is organized

  • Agent application means a type of client program, such as Codex. Several users can use the same type of application.
  • A user's access permission means access granted by one user to that application, for an Actualog environment and approved operations. OAuth calls this a grant or delegation. The current pilot does not offer company-specific access selection or management.
  • Request activity means actual requests and tool calls. It does not imply a permanent online connection; registration and a saved permission are not evidence of current activity.

Personal and company permission-management pages are planned. The future company interface will cover access explicitly bound to that company. The current pilot does not provide those pages, and client sign-out alone does not establish that an Actualog permission has been withdrawn.

What the connected agent should read

First call get_actualog_context to obtain the current identity, delegated scopes, available tools, guidance version and explicit coverage gaps. Then use get_category_guidance for the relevant topics, beginning with context-building and context-readiness. Follow returned pagination and coverage indicators when reading actual records.

The current capability includes Category modeling guidance, Category and Attribute reads, quantities and units, selected Brand and logistics operations, reference dictionary reads and selected controlled authoring workflows. The exact operations available depend on your access permission and what the server currently makes available.

Changes require their own authority

Inspection, discussion and a proposal do not authorize applying a change. Supported commands enforce their own native permissions, reviews, revisions, dependency checks and data-state limits. Read each command's current description and guidance before use, inspect its findings, and verify the affected records afterwards. Recovery may use a command receipt or a fresh read according to that command's contract.

Current authoring capabilities are deliberately bounded. MCP does not provide generic Company, Product or Catalog creation and editing, arbitrary populated-category migration, or unrestricted published-category deletion. A successful connection, saved model or activated template does not establish Product readiness or compatibility with every AI provider.

If a client retains older initialization metadata after a server update, reconnect it. Fresh get_actualog_context and guidance responses describe the current capabilities and rules.