For machine and plant builders running PRO.FILE
A PRO.FILE MCP server gives Claude, ChatGPT or Copilot named tools for documents, parts, where-used, versions and tasks. PROCAD documents its PRO.FX REST API in public; using it needs a licence agreement and AppServer 10.0.14.00 or later. Revalize ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.
What we build
Built on what PROCAD, part of Revalize documents: documents, parts, projects, part-document structures and where-used, version history and change log, workflow status and allowed transitions, tasks and processes, file attachments and previews. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# pro-file-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
search_documents: # free text or field filter -> documents with number, version and status
backend: ExecuteCollectionQuery / full-text metadata search
mode: read
get_part: # part number -> part metadata and linked documents
backend: LoadEntity (Part) + part-document structure query
mode: read
get_where_used: # document or part -> parent structures
backend: Document Parents (WhereUsed) query
mode: read
get_version_history: # entity -> versions with status and dates
backend: VersionHistory query
mode: read
list_my_tasks: # user -> open tasks with target entity
backend: Task with Filter query
mode: read
propose_status_change: # entity, target state -> draft status change for a person to confirm
backend: GetAllowedTargetStates, then ChangeEntityStatus after confirmation
mode: propose
audit: every call logged with user, tool, arguments and the PRO.FILE responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
Checked 21 September 2026
| What we found | |
|---|---|
| Interfaces | PRO.FX-Framework REST API (MobilityService) (REST/JSON, docs public): RPC-style POST calls to the PRO.FX AppServer in the customer installation; needs AppServer 10.0.14.00 or later (PRO.FILE 8.7 SP7+ or 8.6 SP14+) and a licence agreement with the vendor · DynamicSearch endpoints (REST/JSON, docs public): search, suggest, facet views and indexing status · PRO.FX .NET API (.NET, docs public): Windows API on the client-side PRO.FX Runtime, documented briefly at the end of the REST collection |
| Authentication | Bearer token from an IdentityServer token endpoint (/connect/token) via AuthenticateUser; the PRO.FILE 10.5 samples cover password and Windows authentication, and NTLM (AutoLogin) is supported. Access rights follow the PRO.FILE user. |
| Vendor MCP server | No vendor server. No MCP server or AI agent connector from PROCAD or Revalize; the April 2026 roadmap mentions only future data-driven assistance functions. |
| Vendor AI assistant | None found. |
| Other connectors | ProfileREST on GitHub is a community client that uploads PDFs as documents, and the Revalize Integration Hub connects ERP systems; neither is an AI connector. |
PROCAD, part of Revalize (DE). Mid-sized discrete manufacturers, mostly machine and plant engineering, that use PRO.FILE as the backbone for CAD data, documents, BOMs and change processes; Revalize states more than 800 customers.
Why PRO.FILE is hard for agents
01 · Schema
The REST API is RPC over POST with generic entity methods such as LoadEntity and ExecuteCollectionQuery. What a part or document looks like is defined per tenant, so the connector reads GetClassSchemata and GetFieldSchemata first and never hard-codes field names.
02 · Licensing
Using the PRO.FX APIs needs a licence agreement with the vendor, even though the Postman documentation is public. REST needs AppServer 10.0.14.00 or later, so older installations have no REST interface at all.
03 · Network
The PRO.FX AppServer is hosted on IIS inside the customer network. The MCP server runs next to it, and an assistant in the cloud reaches it only through a gateway your IT team controls.
04 · Identity
Authentication changed between version 10.4 and the IdentityServer of 10.5, and NTLM auto-login exists alongside both. The connector has to match your installed version to carry each person's own PRO.FILE login through.
PRO.FILE holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
When this is the wrong page
If the goal is ERP synchronisation of parts and BOMs, the Revalize Integration Hub is built for that and is the shorter path. A connector is right when people ask about PRO.FILE data in Claude, ChatGPT or Copilot, or when an assistant has to combine it with ERP or quality data.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your PRO.FILE owners and checks every backend against your release and licence. Week two tests whether a person's own PRO.FILE permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named PRO.FILE administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
Not as of 21 September 2026. Revalize's April 2026 roadmap mentions future data-driven assistance functions, but no MCP server or agent connector. An MCP server has to be built against the public PRO.FX REST API, which is what this page describes.
Using the PRO.FX APIs needs a licence agreement with the vendor, even though the documentation is public. REST also needs AppServer 10.0.14.00 or later, which means PRO.FILE 8.7 SP7 or 8.6 SP14 and up. The blueprint settles both points before anything is built.
No. Each call runs with the asking person's own PRO.FILE token, so PRO.FILE's access rights decide every answer. Two users asking the same question can get two different answers, and that is tested before go-live.
The two-week Readiness Blueprint is fixed at €4,900: agreed tool list, backends checked against your release, identity tested end to end, costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Thirty minutes with the engineer who would build the connector, with your PRO.FILE administrator in the room if you like.