A weclapp MCP server that reads the open quotation and does not accept it

What we build

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

Built on what weclapp SE documents: customers and parties, opportunities, quotations, sales orders, sales invoices. 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.

# weclapp-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  list_open_quotations: # customer -> quotations that are not accepted
    backend: GET /quotation, v1 or v2 as the tenant runs
    mode: read
  get_quotation:        # id -> status, date, customer, items
    backend: GET /quotation/id/{id}
    mode: read
  list_opportunities:   # filter -> open opportunities
    backend: GET /opportunity on v2, confirmed in blueprint on v1
    mode: read
  get_party:            # id -> the customer or contact
    backend: GET /party/id/{id} on v2, or /customer on v1
    mode: read
  draft_quotation_note: # quotation, text -> a note a person saves
    backend: not posted by the agent
    mode: propose
audit: every call logged with user, tool, arguments and the weclapp 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.

Checked 6 October 2026

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

weclapp SE (DE). Cloud-first SMEs in trade and services. The DACH overview of 14 May 2026 lists weclapp at more than 12,000 customers, part of 3U Holding, in Marburg, with CRM and ERP in one suite.

Why weclapp is hard for agents

Where a weclapp connection needs engineering, not configuration

One interface per row

How the weclapp interfaces differ

weclapp 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.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your weclapp owners and checks every backend against your release and licence. Week two tests whether a person's own weclapp 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 weclapp 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: weclapp API · API v2 changelog: party, opportunity, quotation · DACH CRM market overview, 14 May 2026. Read 6 October 2026. Vendor documentation changes; verify against the current release.

Related

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