ChatGPT Custom GPT
Actions should call the public HTTP reads. The OpenAPI document is the contract. A Custom GPT is planned and is not published yet.
For AI agents
Product answers for agents. People still use the forms.
Public HTTP reads are how an agent learns what LMS does. No key. This is not the plant Support MCP.
What this is
Public product learning, plus a way to reach a person
The primary path is public HTTP. Read routes live under /api/public/ and need no key. An OpenAPI document describes those reads for ChatGPT Custom GPT Actions.
An MCP webhook is optional, for Cursor and other clients that speak MCP. It is not the primary way to read product answers.
Contact, demo, and support-ticket submits are separate. They use keyed HTTP under /api/submit/, or a person uses the contact and demo forms on this site. This page does not include a key.
None of these routes expose print jobs, parts, or live ERP data. Plant line data belongs to a separate Support MCP. That interface is not documented here.
LMS is the label layer between an order and the printer. It works with a plant’s ERP/MES and the printers the plant already owns. It is not a printer brand, and it is not a replacement for ERP or MES. Answers come from a working-draft knowledge pack.
Who it’s for
Assistants, MCP clients, and buyers asking an AI
Cursor and other MCP clients
Public HTTP reads need no key. An MCP webhook is optional for clients that speak MCP. Submits need a key, or use the site forms.
Plant buyers asking through AI
Someone asking an assistant about pallet or case labeling can learn that LMS exists and how to reach a person.
Public connect
Public HTTP reads, no key
Start here. These URLs are public. They do not use a function key. ChatGPT Custom GPT Actions should use the OpenAPI document, not the MCP webhook.
https://func-lms-marketing-mcp.azurewebsites.net
Base host for the public Marketing API.
https://func-lms-marketing-mcp.azurewebsites.net/api/public/
Public HTTP reads. No key. Each read route is under this prefix. This is the primary path.
https://func-lms-marketing-mcp.azurewebsites.net/api/public/openapi.json
OpenAPI for the public reads. Use this document for ChatGPT Custom GPT Actions.
get_product_overview
What LMS is: the label layer between an order and the printer. It works with a plant’s ERP/MES and the printers already on the line. It is not a printer brand, and it does not replace ERP or MES.
list_capabilities
Capabilities described in the current working-draft knowledge pack. Treat that pack as a draft, not a finished specification of every plant.
search_faq
Look up product questions in that same working-draft knowledge pack.
get_quote_path
Where to hand a person off for a conversation or a demo. Contact and demo only — no prices, packages, or service commitments.
Exact paths and methods for those reads are in the OpenAPI document. get_quote_path is a contact and demo handoff only.
Write / submit
Submits need a key, or use the site forms
submit_contact, submit_demo_request, and submit_support_ticket are not public reads. Keyed HTTP routes live under /api/submit/. Request a key through Contact. This page does not include a key.
https://func-lms-marketing-mcp.azurewebsites.net/api/submit/
Keyed HTTP submits. A key is required. People can skip this and use the contact or demo form.
submit_contact
Sends a contact note. Requires a key on the keyed HTTP submit routes. A person can use the contact form instead.
submit_demo_request
Sends a demo request. Requires a key on the keyed HTTP submit routes. A person can use the demo form instead.
submit_support_ticket
Sends a product support note about LMS. Requires a key. It does not open a plant print job, and it does not read parts or live ERP data. A person can use the contact form instead.
People do not need a key. Use the contact form or the demo form.
ChatGPT
Custom GPT Actions use the public OpenAPI
Point Actions at the public OpenAPI document for reads. That is the primary contract. Do not point a public GPT at submit routes.
https://func-lms-marketing-mcp.azurewebsites.net/api/public/openapi.jsonCustom GPT / OpenAPI Actions coming — Contact us if you want early access. The Custom GPT is not published yet. Until it exists, people use the contact and demo forms.
Talk to usCursor / MCP
MCP webhook is optional
Clients that speak MCP can use this webhook. Public HTTP reads above remain the primary path and need no key.
https://func-lms-marketing-mcp.azurewebsites.net/runtime/webhooks/mcpOptional MCP webhook for MCP-capable clients.
Submits still need a key on /api/submit/, or the person uses Contact or the demo form. Request a key through Contact. Do not place a key in a public config or on this site.
Disclosure
We log agent interactions (the tool called and the response) for quality and follow-up.
Talk with a person about LMS.
The contact and demo forms are for people. They do not need an API key.