









































Works out-of-box with your favorite AI agents

Arena PLM Quality is a product lifecycle and quality management platform for manufacturers. Makini's MCP server brings Arena PLM Quality data and workflows to AI agents directly, with no custom integration to build.
Have any questions? We’re here to help You
Arena PLM and Arena QMS are two sides of one cloud platform from Arena, a PTC business; PTC completed its $715 million acquisition of Arena Solutions in January 2021. The PLM side manages Items, BOMs, Changes and Suppliers, and the QMS side adds quality processes such as CAPA, NCMR and 8D with 21 CFR Part 11 compliant electronic approvals. Both run in the same SaaS workspace, so quality records link directly to the product record.
Yes, Arena PLM has a REST API, but it is not switched on by default: PTC activates REST API access per account, and each account carries a request limit per 24 hour period. Authentication uses a login that returns an API session key, or OAuth 2.0 client credentials for a machine user. Sessions expire 90 minutes after the last action, and Supplier users cannot use the API; it is for Employee and Partner accounts.
A quality process in Arena QMS is a record built from a template, such as CAPA, NCMR or 8D, that moves through defined steps with assigned owners and approvers. Each process can list affected objects, for example the Items, Changes or Suppliers involved, and holds the files and sign-offs collected along the way. Templates are configured per workspace, so step names and terminology follow your own quality procedures rather than a fixed vendor vocabulary.
In Arena PLM a Request is a change request: a proposal that describes a problem or improvement and is evaluated before anyone touches the product record. A Change is the engineering change order that actually revises Items, BOMs and files, with routing, approval and implementation tasks. Requests can carry evaluation issues and lead to one or more Changes, so an agent reading both can show which requests are still waiting and which changes implement them.
To connect Arena PLM to Claude or ChatGPT, sign in to your Arena workspace through Makini Link, then paste the MCP endpoint Makini issues into Claude, ChatGPT, Cursor or another MCP client. Your Arena credentials are entered in Makini Link, not in the chat client. Once connected, call get_connection_details to see which Arena objects and fields the connection exposes, since items, changes and quality records appear only where the connection supports them.
An AI agent finds open NCMRs and CAPAs in Arena QMS by searching quality processes by template and status, where the connection exposes quality process data; run get_connection_details first to confirm that it does. Ask for processes built from the NCMR or CAPA template that are still open, grouped by owner or affected Item, and the agent lists overdue steps and the Suppliers involved, so a quality manager sees the backlog without opening each record.
No, an AI agent should not approve a Change or close a CAPA in Arena PLM; approvals are electronic signatures tied to a named person, and Arena supports 21 CFR Part 11 compliant approvals for regulated manufacturers. Keep the agent reading and drafting: it can summarize an open CAPA, prepare a change description or flag missing affected items. Where the connection and the user's rights allow writes, test on a few records with a reviewer.
The MCP connection sees the Arena workspace that the authorizing user logs into, because an Arena login targets one workspace at a time; a company with several workspaces, for example one per subsidiary, decides which one the agent gets. Use a dedicated Employee account, since Supplier users cannot use the Arena REST API, and REST access must be enabled for the account by PTC. The endpoint Makini issues is scoped to that login.