Skip to main content

Guided prompts

The server offers four ready-made prompts. In Claude Code they appear as slash commands (type / and look for the server name); in other apps they are in the prompt or attachment menu. Each asks for the customer number and then runs a fixed work plan over the tools.

Implement a new customer​

implement_new_customer: walks the 35 implementation steps.

  1. Reads the customer overview and the implementation guide.
  2. Shows the steps as a table: step, required, state.
  3. Goes through the required steps that are empty, in order: Receiving, Process, Master data, Enrich, Validate, Integrate, Bits and bobs, Close-out. For each step it reads the section reference and existing items, asks you the questions the step needs, tests where a tester exists, and proposes the change for your approval.
  4. One step at a time; it tells you which step comes next.
  5. At the end it proposes a configuration baseline export.

Steps that are kept in the customer portal (and so cannot be seen in the configuration) are recorded with your decision: done, not applicable, or blocked with a reason.

Review a customer's configuration​

review_customer_config: reports gaps and risks, ordered by risk. It changes nothing. It checks among other things:

  • required implementation steps that are empty;
  • inactive items and items nothing refers to;
  • receiving inboxes without a capture rule, and capture rules that can never win;
  • rules whose activation does not match their description, or that never activate on recent invoices;
  • workflow steps without outgoing transitions and a missing catch-all;
  • failing scheduler tasks and webhooks;
  • users in no group, groups without rights, API users past their end date.

Each finding names the section and config item id, why it matters and the fix the app would propose. You pick which ones to fix.

Add a supplier file format​

add_supplier_file_format: from a sample file to a tested inbound file format (CSV, XML, UBL, EDI). The app looks for a global template or existing format to start from, can ask the platform's AI to propose a mapping, tests the format on the sample until the invoices come out right, and proposes it.

Set up a connector​

set_up_connector: an ERP connector from a template, its integration rules and scheduler tasks, as one change set. Write and test the connector code locally with the Connector Toolkit first; see Connectors through the MCP server.