For Swiss manufacturers running ProConcept

A ProConcept MCP server that answers from your ERP within each person's own ProConcept permissions

A ProConcept MCP server gives Claude, ChatGPT or Copilot named tools for sales orders, production orders, project costs and after-sales interventions in ProConcept ERP. ProConcept publishes no API reference; interfaces include cloud APIs, ODBC, XML, EDI and the Oracle database. Neither ProConcept nor Forterro ships an MCP server as of 21 September 2026.

Why ProConcept is hard for agents

Where a ProConcept connection needs engineering, not configuration

01 · Documentation

No public API reference

ProConcept publishes no API reference and no authentication description. Integration details come only from ProConcept or Forterro, so the blueprint starts by getting that material through you or your ProConcept contact.

02 · Deployment

On-premise Oracle or single-tenant cloud

ProConcept runs on Oracle on-premise or single-tenant on AWS in Switzerland. The access path, database or API, differs per customer, and so does the network work to reach it.

03 · Scope

Broad modules, configured per customer

ProConcept covers production, projects, after-sales, finance, payroll and precious materials management, each configured per customer. Mapping business questions to objects is done per installation, not once for everyone.

04 · Naming

Older material says SolvAxis

ProConcept SA was formerly SolvAxis SA and is now part of Forterro. Older integrations and documents use the SolvAxis name, so an inventory of existing interfaces has to search under both.

Checked 21 September 2026

ProConcept at a glance: interfaces, access and what exists for AI

	What we found
Interfaces	ProConcept Cloud APIs and connectors (not published, docs not published): ProConcept only states 'robust APIs and intelligent connectors'; the cloud runs single-tenant on AWS in Switzerland · ODBC, XML and EDI/EDIFACT interfaces (file/EDI, docs not published): listed on the topsoft profile, alongside interfaces to CAD/PDM and banking (ISO 20022) · Oracle database (database, docs not published): ProConcept runs on Oracle; the schema is not publicly documented
Authentication	Not documented publicly.
Vendor MCP server	No vendor server. No ProConcept or Forterro product MCP server; the MCP repositories on Forterro's GitHub are generic tooling, such as a gateway and servers for GitLab, Freshservice and Kubernetes.
Vendor AI assistant	No named ProConcept AI assistant; ProConcept only says its cloud eases the integration of AI, IoT and data analysis.
Other connectors	Flexmonster provides embedded pivot reporting inside ProConcept; it is a reporting component, not an external API.

ProConcept SA (formerly SolvAxis SA), part of Forterro (CH). Swiss mid-sized and large manufacturing, project-based and service companies, mainly in French- and German-speaking Switzerland; ProConcept states more than 15,000 users on over 1,000 sites.

What we build

A first ProConcept tool list, written as the manifest your IT team signs

ProConcept SA (formerly SolvAxis SA), part of Forterro does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.

# proconcept-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  get_customer_orders:        # customer, date range -> sales orders with delivery status
    backend: confirmed in blueprint
    mode: read
  get_production_orders:      # status, due date -> production orders with progress
    backend: confirmed in blueprint
    mode: read
  get_project_costs:          # project number -> budget against actual
    backend: confirmed in blueprint
    mode: read
  list_service_interventions: # customer or serial number -> open after-sales interventions
    backend: confirmed in blueprint
    mode: read
  draft_purchase_request:     # article, quantity, date -> purchase request draft for a person to confirm
    backend: confirmed in blueprint
    mode: propose
audit: every call logged with user, tool, arguments and the ProConcept response

The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.

ProConcept 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

Which production orders for customer X are behind schedule this week?
What is the cost status of project P compared with budget?
Which after-sales service interventions are open for machine serial number S?

What it will not do

Read more than the asking user may read in ProConcept; how each person's ProConcept rights carry through the interface is tested in the blueprint before any tool goes live.
Create a purchase request by itself: the only write tool drafts one, and a person confirms it in ProConcept.
Write to the Oracle database: any change goes through ProConcept's own interfaces and a person, never through SQL.

When this is the wrong page

If the need is pivot reporting inside ProConcept, the embedded reporting already covers it, and cross-year analysis belongs in a data warehouse. A connector is right when people ask questions in Claude, ChatGPT or Copilot, or need ProConcept combined with another system.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your ProConcept owners and checks every backend against your release and licence. Week two tests whether a person's own ProConcept 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 ProConcept 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.

Sources: ProConcept company · ProConcept Cloud · ProConcept production · Forterro: ProConcept · topsoft profile: ProConcept · Forterro GitHub. Read 21 September 2026. Vendor documentation changes; verify against the current release.

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 ProConcept teams ask before the first tool call

Does ProConcept have its own MCP server?

Not as of 21 September 2026. Forterro's GitHub holds generic MCP tooling but nothing for ProConcept, and ProConcept names no AI assistant of its own. An MCP server for Claude, ChatGPT or Copilot has to be built on ProConcept's own interfaces.

Do we need extra ProConcept licences or access for an AI connector?

ProConcept does not publish its API reference, authentication or licensing. We need that material through you or your ProConcept contact, and the licence question is one to check with ProConcept. The blueprint answers both before any build starts.

Can the assistant see data a user is not allowed to see in ProConcept?

No. How each person's ProConcept rights carry through the interface is tested in the blueprint, and the connector never reads the Oracle database around those rights. Two users asking the same question can get two different answers, and that is tested before go-live.

What does a ProConcept 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 ProConcept administrator in the room if you like.