For industrial sales teams on CAS genesisWorld

A CAS genesisWorld MCP server that reads the address dossier and does not share a password

A CAS genesisWorld MCP server reads addresses, dossiers and appointments from REST v7.0 on the customer's application server. CAS does not ship an MCP server as of 6 October 2026. A community server exists and logs in with a password. Pexon does not copy that login. The signed list is read-only.

Why CAS genesisWorld is hard for agents

Where a CAS genesisWorld connection needs engineering, not configuration

01 · Password

The published agent login is a password

The community server stores a user name and password. Two sellers behind one password see one person's rights, or an admin's. We do not copy that.

02 · Edition

Opportunities are a module

The installation guide says further editions add modules such as receipts and order management. A pilot on Standard Edition does not invent an opportunity object the server does not list.

03 · Desktop

DCOM is not an assistant protocol

Desktop clients use DCOM. The agent uses the REST service, and only the types that service lists for this database.

04 · Key

The product key is a tenant secret

Calls carry X-CAS-PRODUCT-KEY in the community client. The key is not a user. It does not replace the asking person's permissions.

Checked 6 October 2026

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

	What we found
Interfaces	genesisWorld REST v7.0 (REST/JSON, docs public) · Desktop RPC (DCOM, docs public)
Authentication	The community MCP that calls this API sends a product key plus a user name and password. CAS documents the REST service on the server. We do not ship a shared password. The blueprint uses the per-user login that installation already has.
Vendor MCP server	No vendor server. No CAS-shipped MCP server was on the pages read on 6 October 2026. A community server, cas-genesis-world-mcp, calls REST v7.0 with a product key and a password. That is not the connector we ship.
Vendor AI assistant	None found.
Other connectors	cas-genesis-world-mcp is a community server for REST v7.0. It can run read-only. Its documented login is a product key plus a user name and password, which is a shared secret if more than one person uses it.

CAS Software AG (DE). Industrial Mittelstand in machinery and wholesale. The DACH overview of 14 May 2026 lists CAS genesisWorld at more than 20,000 customers, headquartered in Karlsruhe, and names it for complex B2B sales.

What we build

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

Built on what CAS Software AG documents: addresses, appointments, tasks, opportunities where that edition exposes them, dossiers. 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.

# cas-genesisworld-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  smart_search:       # text -> matching addresses and records
    backend: GET /v7.0/smartsearch
    mode: read
  get_address:        # id -> the address record and its dossier
    backend: GET /v7.0/type/address/{id} and dossier/full
    mode: read
  list_appointments:  # user, range -> appointments
    backend: GET /v7.0/type/appointment/list, if that type is permitted
    mode: read
  list_opportunities: # user -> open opportunities
    backend: the opportunity type, only when the edition lists it
    mode: read
  draft_appointment:  # address, time -> an appointment a person saves
    backend: not created by the agent
    mode: propose
audit: every call logged with user, tool, arguments and the CAS genesisWorld 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.

One interface per row

How the CAS genesisWorld interfaces differ

genesisWorld REST v7.0

REST/JSON. Documentation is public. served by the application server at /genesisrest.svc/v7.0, with a Swagger document on the demo host. Reads include smart search and typed records such as addresses

REST/JSON. Docs public.

Desktop RPC

DCOM. Documentation is public. the installation guide says desktop clients talk to the application server over DCOM. That is not the agent path

DCOM. Docs public.

CAS genesisWorld 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 open appointments does this seller have with this address?
What is on the dossier for this company?
Which opportunities are open, if this edition has that type?

What it will not do

Write an address, appointment or opportunity. The signed list is read-only.
Log in with one shared password for the whole sales team.
Query a data type the REST service does not list for this database.

When this is the wrong page

If the team only needs CAS's own screens, stay there. A connector is right when a seller asks an assistant outside genesisWorld and the answer has to be that person's records, not a shared technical user.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your CAS genesisWorld owners and checks every backend against your release and licence. Week two tests whether a person's own CAS genesisWorld 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 CAS genesisWorld 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: CAS REST demo, Swagger v7.0 · CAS installation guide, DCOM and web service · DACH CRM market overview, 14 May 2026. Read 6 October 2026. Vendor documentation changes; verify against the current release.

Connectors for 100 source systems — the dated catalogue this page belongs to
cobra CRM connector — CRM, cobra computer's brainware GmbH
HubSpot connector — CRM, HubSpot, Inc.
Pipedrive connector — CRM, Pipedrive
Claude MCP server development — how we build an MCP server for any internal system

Questions CAS genesisWorld teams ask before the first tool call

Does CAS genesisWorld ship its own MCP server?

No CAS-shipped MCP server was on the pages read on 6 October 2026. A community server, cas-genesis-world-mcp, calls REST v7.0 with a product key and a password. That is not the connector we ship. This page describes what we add around that fact: a signed tool list and a test that the asking user only sees their own records.

Can the assistant change a deal or send a mail?

Not on the list we sign. The blueprint starts read-only. A draft the person saves in the CRM is the only write, and only after that is agreed.

Will two sellers see the same pipeline?

Only where the CRM would already show both of them the same records. Calls run as the person who asked. The blueprint tests that with two users before anything is called production.

What does a CAS genesisWorld connector cost?

The two-week Readiness Blueprint is fixed at €4,900: the tool list, a check against your tenant, and a test that permissions survive the round trip. A 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 CAS genesisWorld administrator in the room if you like.