Priority MCP Server
Priority is an ERP platform covering financials, sales and purchase orders, invoicing, inventory, projects, service and HR. Its REST API exposes every Priority form as an OData entity.
What is the Priority MCP Server?
The Priority MCP server gives AI agents structured, permission-aware access to Priority through the Model Context Protocol. With 29 pre-built actions, agents can read, create, and update Priority data on behalf of authorized users.
Willow ships the Priority MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Priority is being used by every AI agent in your stack.
Tools
List Forms
List every Priority form (OData entity set) exposed by this installation, such as CUSTOMERS, ORDERS, LOGPART and AINVOICES. Start here to discover which forms exist before querying them, since the exposed forms depend on the customer's Priority modules and customizations.
Get Form Metadata
Retrieve the schema of a single Priority form as EDMX XML: its key fields, every column with its type (Edm.String, Edm.Int64, Edm.Decimal, Edm.DateTimeOffset), Hebrew/English descriptions, and the subforms available for expansion. Use this before creating or filtering records so field names and types are exact. Requires Priority 25.0 or later and only works for top-level forms (ORDERS, not ORDERITEMS).
Get Priority Version
Return the Priority version and server IP of the connected installation, e.g. '25.1-20.0.0.119'. Useful for checking whether version-gated API features are available (per-form metadata needs 25.0+, data modification needs 17.2+, text forms need 20.0+).
Query Records
Query any Priority form with the full set of OData options: filter, select, expand, orderby, top, skip and since. Works for every form the installation exposes, so use it for forms without a dedicated tool — projects, receipts, warehouse balances, PART, PHONEBOOK and private customizations — after confirming the exact name with List Forms. Always select the fields you need: Priority returns every column of a form by default.
Get Record
Retrieve a single record from any Priority form by its key, optionally inlining subforms. Keys are the form's business key, not the internal auto-numbered id: ORDERS is keyed by ORDNAME ('SO18000002'), CUSTOMERS by CUSTNAME, LOGPART by PARTNAME. Forms with composite keys (such as AINVOICES) need key_expression.
Create Record
Create a record in any Priority form. Supply the fields as an object keyed by the uppercase Priority column names, e.g. {"CUSTNAME": "T000001"} for ORDERS. Subform lines can be created in the same call by including the subform as an array, e.g. {"CUSTNAME": "T000001", "ORDERITEMS_SUBFORM": [{"PARTNAME": "TR0001", "TQUANT": 5}]}. Priority validates the record exactly as its UI would and returns the saved entity, including generated values such as ORDNAME. Note that Priority cannot roll back a saved record.
Update Record
Update selected fields of an existing record in any Priority form. Only the fields you supply are changed. Reference the record by its business key (ORDNAME, CUSTNAME, PARTNAME…) — the internal auto-unique key is read-only and cannot be used here.
Delete Record
Delete a record from any Priority form by its key. Deletions are immediate and cannot be undone, and Priority refuses records that are referenced by documents or have already been processed.
List Subform Records
List the lines of a subform belonging to a specific record, e.g. the items of an order via ORDERS('SO18000002')/ORDERITEMS_SUBFORM. Subform names come from the parent form's metadata and almost always end in _SUBFORM. Prefer this over expanding when you only need the lines.
Create Subform Record
Add a line to a subform of an existing record, e.g. add an item to an order by posting {"PARTNAME": "TR0001", "TQUANT": 5} to ORDERS('SO18000002')/ORDERITEMS_SUBFORM. Priority fills in derived values such as description, unit and price, and returns the created line with its KLINE.
Update Subform Record
Update a single subform line of a record, e.g. change the quantity of order item 1 via ORDERS('SO18000002')/ORDERITEMS_SUBFORM(1). Identify the line by its KLINE number, or by a raw key expression when the subform has a composite key.
Delete Subform Record
Delete a single subform line of a record, e.g. remove order item 1 via ORDERS('SO18000002')/ORDERITEMS_SUBFORM(1). Deletions are immediate and cannot be undone.
Get Record Text
Read the free-text note attached to a record, e.g. the text of an order via ORDERS('SO20000422')/ORDERSTEXT_SUBFORM. Text subforms are named after the parent form plus TEXT_SUBFORM and the content is returned as HTML in the TEXT property. Requires Priority 20.0 or later.
Update Record Text
Add or replace the free-text note of a record, e.g. append a comment to an order via ORDERS('SO20000422')/ORDERSTEXT_SUBFORM. Text is HTML (use <br> for line breaks); set append to false to replace the existing text instead of adding to it. Requires Priority 20.0 or later.
Attach File
Attach a file to a record's attachments subform, e.g. ORDERS('SO21000113')/EXTFILES_SUBFORM. Provide the file as base64 content plus its MIME type; the connector assembles the data URL Priority expects. Allowed types are governed by the application server's MIME configuration. Requires Priority 21.0 or later (the suffix option needs 22.0).
List Customers
List customers from the CUSTOMERS form. Filter on columns such as CUSTNAME (customer number), CUSTDES (name), STATDES (status), PHONE or EMAIL, e.g. "CUSTDES eq 'ACME Inc.'". CUSTOMERS is a wide form, so select only the fields you need.
Get Customer
Retrieve one customer from the CUSTOMERS form by customer number (CUSTNAME), optionally inlining subforms such as CUSTPERSONNEL_SUBFORM (contacts) or CUSTNOTES_SUBFORM.
List Sales Orders
List sales orders from the ORDERS form. Useful columns are ORDNAME (order number), CUSTNAME, CDES (customer name), CURDATE (order date), ORDSTATUSDES (status) and TOTPRICE. Pass since to pull only orders changed after a timestamp, which is the efficient way to sync.
Get Sales Order
Retrieve one sales order from the ORDERS form by order number (ORDNAME), with its line items inlined by default. Pass expand to change which subforms are returned, e.g. 'ORDERITEMS_SUBFORM,ORDERSTEXT_SUBFORM,SHIPTO2_SUBFORM'.
Create Sales Order
Create a sales order in the ORDERS form, optionally with its line items in the same call. Only the customer number is required — Priority derives the order number, dates, prices and currency from the customer and price list. Pass extra header fields (such as DETAILS, AGENTCODE or REFERENCE) via fields.
Add Sales Order Item
Add a line item to an existing sales order (ORDERS/ORDERITEMS_SUBFORM). Priority fills in the part description, unit and price from the catalog and price list, and returns the created line including its KLINE.
List Invoices
List A/R invoices from the AINVOICES form. Useful columns are IVNUM (invoice number), IVDATE, CUSTNAME, CDES, TOTPRICE, QPRICE and IVTYPE. Note that AINVOICES has a composite key (IVNUM, IVTYPE, DEBIT), so use Get Invoice to fetch a single one.
Get Invoice
Retrieve one A/R invoice from the AINVOICES form using its composite key, with its lines inlined by default. Invoice type defaults to 'A' (invoice) and debit to 'D'; use List Invoices first if you are unsure of the exact combination.
List Parts
List catalogue items from the LOGPART form (the part list). Useful columns are PARTNAME (part number), PARTDES (description), BARCODE, FAMILYNAME (part family), TYPE and LASTPRICE, e.g. "FAMILYNAME eq '001' and LASTPRICE gt 200".
Get Part
Retrieve one catalogue item from the LOGPART form by part number (PARTNAME), optionally inlining subforms such as warehouse balances or price lists.
List Suppliers
List suppliers from the SUPPLIERS form. Useful columns are SUPNAME (supplier number), SUPDES (name), PHONE, EMAIL, ADDRESS and STATDES (status).
List Purchase Orders
List purchase orders from the PORDERS form. Useful columns are ORDNAME (purchase order number), SUPNAME, CDES (supplier name), CURDATE and STATDES. Expand PORDERITEMS_SUBFORM for the ordered lines.
Run Batch Request
Combine up to 100 reads and writes into a single OData $batch call, with dependencies between them. Requests reference each other by id — a later request can use '$1/ORDERITEMS_SUBFORM' as its url to act on the entity created by request '1' — which also pinpoints exactly which operation failed. Note that Priority commits each operation as it runs: a failed batch is not rolled back.
Refresh Form Metadata
Clear the cached REST metadata for a form so that newly added custom fields become visible to the API. Priority rebuilds the metadata on the next request to that form. Omit the form name to clear metadata for every form, which is slower to rebuild. Requires Priority 22.0 or later.
Customize Tools
Edit descriptions, modify arguments, select tools, or add new ones
Set Up Your Priority MCP Server in Minutes
Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.
Claude Desktop
{
"mcpServers": {
"willow-priority": {
"type": "http",
"url": "https://<org>.mcp-s.com/mcp/mcp/priority"
}
}
}Cursor
{
"mcpServers": {
"willow-priority": {
"type": "http",
"url": "https://<org>.mcp-s.com/mcp/mcp/priority"
}
}
}Claude Code
claude mcp add willow-priority --transport http https://<org>.mcp-s.com/mcp/mcp/priorityn8n
{
"url": "https://<org>.mcp-s.com/mcp/mcp/priority",
"method": "POST"
}Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.
Enterprise Governance for Priority
Willow adds the layer Priority and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.
Priority MCP Server FAQ
What is the Priority MCP server?
The Priority MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Priority data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.
How is Willow's Priority MCP server different from the official one?
The official Priority MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.
Which AI clients work with the Priority MCP server?
Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.
Is the Priority MCP server secure? How does Willow handle authentication?
Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Priority, nothing more. No credentials reach the LLM. Every action writes to an audit trail.
Can I limit which Priority actions agents can take?
Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.
How do I detect shadow Priority MCP servers in my org?
Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Priority MCP locally, you'll see it.
What does the Priority MCP server cost?
Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.
How do I install the Priority MCP server with Willow?
Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.
Compare Willow MCP Gateway
See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.
Your agents are already in the wild.
Give them a Basecamp. Go from AI chaos to AI work, in minutes.