Skip to main content

AMFG Public API: MCP Tools & App Settings Reference

This guide details the Model Context Protocol (MCP) integrations and App Configuration endpoints available in the AMFG Public API.

Written by AMFG Consulting & Support

Model Context Protocol (MCP) Integration

The AMFG Public API exposes Model Context Protocol (MCP) tools compliant with the 2026-07-28 MCP specification. These tools enable AI assistants and automated agents to interact directly with quotes, tickets, and parts within your AMFG environment.

Endpoint & Protocol Details

  • Endpoint: POST /mcp

  • Authentication: Uses the standard Public API Authorization header (Authorization: <secret> or Authorization: Bearer <secret>).

  • Tool Count: Exposes 9 MCP tools covering core operations across:

    • Quotes: Retrieval, creation, and state updates.

    • Tickets: Querying ticket queues and updating details.

    • Parts: Inspection of part geometry metadata, production parameters, and DFM status.

Documentation Note: For specific tool schemas, parameter definitions, and invocation samples, refer to the MCP tag in the interactive API documentation.

App Settings Endpoint

Retrieve application-level configuration settings tied to the authenticated Incoming Secret. This endpoint provides crucial context regarding configured measurement units, contact information, and workspace order thresholds.

Get App Settings

Retrieves workspace units of measurement, support/contact emails, and customer/management order value minimums.

HTTP

GET /api/v1/app

Authorization

Requires an IncomingSecret passed in the Authorization header.

Responses

  1. 200 OK

Returns the application configuration schema.

  • Response Schema: application/json

  • Object Structure:

JSON

{
  "unitsOfMeasurement": "mm",
  "contactEmail": "support@example.com",
  "minOrderValue": 50.00,
  "mcMinOrderValue": 100.00
}

  • Field Descriptions:

    • unitsOfMeasurement: The workspace display unit (mm, cm, or inch). Note: All backend pricing and geometrical calculations are conducted in millimeters (mm).

    • contactEmail: The configured primary contact email for app-related notifications.

    • minOrderValue: The minimum order threshold applied to the customer-facing quotation tool (Front-End Portal).

    • mcMinOrderValue: The minimum order threshold applied to internal orders within the Management Console (MC).

2. 401 Unauthorized

Authentication failed. Returned identically for all authorization failure causes:

JSON

{
  "code": 401,
  "message": "Not Authorized"
}

3. Default (Downstream Error Pass-Through)

Downstream microservice or database errors pass through verbatim with diagnostic headers:

  • Header x-error-source: Names the failing downstream service.

  • Header x-error-source-request-id: Unique identifier to cite when logging support tickets.

Additional Semantics

For comprehensive entity schemas, data types, and field-level definitions, refer to the AMFG Engine API Reference.

Did this answer your question?