A SuperOffice MCP server that reads the sale and its next due date

What we build

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

Built on what SuperOffice documents: companies (Contact), persons, sales, projects, activities on a sale, stakeholders. 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.

# superoffice-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_my_sales:     # user -> sales that user may see
    backend: GET /api/v1/Sale
    mode: read
  get_sale:          # id -> amount, stage, next due date
    backend: GET /api/v1/Sale/{id} and /NextDueDate
    mode: read
  list_activities:   # sale -> activities
    backend: GET /api/v1/Sale/{id}/Activities
    mode: read
  list_stakeholders: # sale -> people on the sale
    backend: GET /api/v1/Sale/{id}/Stakeholders
    mode: read
  draft_activity:    # sale, text, date -> an activity a person saves
    backend: not posted by the agent
    mode: propose
audit: every call logged with user, tool, arguments and the SuperOffice 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

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

SuperOffice (NO). Mid-sized B2B sales teams. The DACH overview of 14 May 2026 lists SuperOffice at more than 6,000 customers, with offices in Frankfurt, Cologne, Dortmund, Düsseldorf and Munich, and names it for industrial Mittelstand sales.

Why SuperOffice is hard for agents

Where a SuperOffice connection needs engineering, not configuration

SuperOffice 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 SuperOffice owners and checks every backend against your release and licence. Week two tests whether a person's own SuperOffice 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 SuperOffice 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: SuperOffice REST API · Sale entity · Authorization code flow, no client credentials · 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