01 · Docs
No public API reference
keytech names a REST web API but publishes no reference for it. Every endpoint has to be confirmed against your own keytech web API instance before a tool is written.
For manufacturers running keytech PLM
A keytech MCP server that finds drawings, files and tasks under each user's own keytech rights
A keytech MCP server gives Claude, ChatGPT or Copilot named tools for keytech elements, files and tasks. keytech names a REST web API but publishes no reference, so every endpoint is confirmed against your installation. keytech and Revalize ship no MCP server as of 21 September 2026; Pexon builds one, starting with a two-week blueprint.
Why keytech is hard for agents
Where a keytech connection needs engineering, not configuration
02 · Versions
The only samples are from 2018
The public sample code dates from 2018. Current keytech versions, keytech 14 and later, may differ in paths and fields, so the blueprint starts with a check of your release.
03 · Identity
Basic auth and per-element rights
The samples use HTTP Basic authentication, which needs TLS and a decision on how each person's own login reaches the API. keytech keeps permissions per element, and the connector has to respect them on every answer.
04 · Roadmap
One of two Revalize PLM products
keytech sits in the Revalize portfolio next to PRO.FILE, and the long-term roadmap is not public. Ask Revalize about the future of the web API before committing to a build.
Checked 21 September 2026
keytech at a glance: interfaces, access and what exists for AI
| What we found | |
|---|---|
| Interfaces | keytech api (Web API) (REST/JSON, docs not published): keytech describes a REST web service for customer and third-party applications; there is no public reference, and resource paths are visible only in vendor sample apps from 2018 |
| Authentication | The 2018 vendor sample apps send HTTP Basic authentication (user name and password) to the web API; SSO is mentioned for keytech search. There is no public authentication documentation. |
| Vendor MCP server | No vendor server. No MCP server or AI agent integration from keytech or Revalize found. |
| Vendor AI assistant | None found. |
| Other connectors | keytech's own sample apps on GitHub (search, my tasks, favourites, saved queries) are Angular demos from 2018, marked as not for productive use. |
keytech, PROCAD International GmbH, part of Revalize (DE). Mostly German-speaking mid-sized manufacturers in machinery, automotive supply, aerospace and medical engineering that manage CAD data, documents and BOMs in keytech PLM/DMS.
What we build
A first keytech tool list, written as the manifest your IT team signs
keytech, PROCAD International GmbH, part of Revalize does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# keytech-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_elements: # search text, page -> matching elements
backend: keytech api search (GET /search?q= in the 2018 samples), confirmed in blueprint
mode: read
get_element: # element key -> metadata
backend: keytech api elements (GET /elements/{elementKey} in the 2018 samples), confirmed in blueprint
mode: read
get_element_files: # element key -> attached files and master file
backend: keytech api element files, resource confirmed in blueprint
mode: read
list_my_tasks: # user -> open workflow tasks
backend: keytech api user tasks, resource confirmed in blueprint
mode: read
propose_element_update: # element key, field changes -> draft update for a person to confirm
backend: confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the keytech 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.
keytech 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.
What the connector answers, and what it will not do
Questions it answers
- Where is the current drawing and master file for article number X?
- Which keytech tasks are assigned to me, and which documents do they refer to?
- What does my saved query for open change requests return right now?
What it will not do
- Change an element by itself: the one write tool drafts an update, and a person confirms it in keytech.
- Read more than the asking user may read in keytech; element permissions come from keytech, not from the connector.
- Rely on the 2018 sample paths: every backend is confirmed against your installation first.
When this is the wrong page
If keytech data only has to flow into ERP or CAD, keytech's own interfaces cover that and no assistant is needed. A connector is right when people ask about keytech data in Claude, ChatGPT or Copilot, or when an answer needs keytech and another system together.
Start with the Readiness Blueprint.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your keytech owners and checks every backend against your release and licence. Week two tests whether a person's own keytech 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 keytech 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.
Related
- Connectors for 100 source systems — the dated catalogue this page belongs to
- Claude MCP server development — how we build an MCP server for any internal system
Questions keytech teams ask before the first tool call
Does keytech have its own MCP server?
Not as of 21 September 2026. Neither keytech nor Revalize has published an MCP server or an AI agent integration. An MCP server has to be built against the keytech web API, which is what this page describes.
Do we need extra keytech licences or access for an AI connector?
keytech does not publish the licence terms of its web API, so ask keytech or Revalize before the build. The blueprint also needs access to your web API instance, because the only public paths come from sample apps from 2018.
Can the assistant see elements a user is not allowed to see in keytech?
No. keytech keeps permissions per element, and each call runs as the asking person, so keytech decides every answer. Two users asking the same question can get two different answers, and that is tested before go-live.
What does a keytech connector cost?
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
Not a sales call. An architecture call.
Thirty minutes with the engineer who would build the connector, with your keytech administrator in the room if you like.