Ask questions, run reports, create and update records — from Claude, ChatGPT or Gemini. Every person connects with their own token, and you can revoke it in seconds.
Priority Gateway v1.55.x · endpoint POST /mcp
Two tabs, one endpoint: a question answered from live data, and a write that stops for a human.
An LLM reads what you paste into it. Without a tool surface, every Priority question ends in a screenshot, a CSV export, or a wrong guess.
Every install has its own forms, columns and rules. A connector with a schema baked in goes stale the morning somebody adds a column.
Reading is easy to approve. Writing is not. The question a finance lead actually asks is: whose rules apply when the model presses save?
One endpoint answers all three.
Three tools instead of twenty-three, with nothing lost along the way. A model learns them once and uses them on any Priority.
priority_discover
Find out what exists
Find a form or procedure by name, see its fields however deep they nest, and read the dropdown values.
priority_action
Do it in one call
Query, create, update, delete. Run procedures and reports, fire form actions, upload files, batch several writes.
priority_session
Edit like a person would
Open a form, set one field, watch Priority answer with warnings and cascading updates, then save.
Progressive discovery is why this works on your Priority. The model asks what exists before it does anything, so nothing about your install is hardcoded on our side. Add a column to ORDERS this morning and the model sees it this afternoon.
"How much did we sell last month" is one wrong join away from a confident wrong number. So the model gets the right slice of your schema first.
Anything with a total, a ranking, a breakdown or a date range.
The forms it needs, the filters that give them meaning, and how they connect, from a map of your own install.
It composes the query itself, against the dialect rules it was handed.
Checked against that same map before anything runs.
Run on the read-only channel, and answered in the conversation.
SQL handling depends on the query path. The end-user path validates a structured query and generates bounded read SQL. The separately authorized administrative path accepts raw SQL and validates it before execution.
That map is built from your own Priority by BI Generator: every table, column and form, how they connect, and what each field actually means — including whatever your implementer built. The custom table behind your quality process and the columns somebody added to the order line are on the map next to the standard ones. A model working from general knowledge of Priority would not know they exist; a model handed this context can answer questions about them on the first try.
The controls are the ones Priority already has. The gateway's job is to expose them, not to reinvent them.
| When the model… | What actually happens |
|---|---|
| reads data | OData and WebSDK data operations use the connected Priority user. Gated SQLI checks the verified user’s form access and runs the approved query as the tenant master. Its coverage depends on enforcement settings and does not reproduce every screen or field restriction. |
| writes SQL | The SQL channel is read-only by construction. INSERT, UPDATE, DELETE and the rest of the mutating verbs are rejected before the query leaves the gateway. |
| creates or updates a record | The write goes through Priority's own form, so Priority's validations, business rules and triggers all run. Nothing writes straight to a table. |
| trips a Priority warning | The warning text is surfaced into the conversation instead of being swallowed. Someone confirms or cancels, and the save waits. |
| hits a confirmation dialog | You choose per call: confirm it, cancel it, fail the call, or hand the dialog text to the model and let it decide out loud. |
| picks the wrong protocol | The reference docs are part of the tool surface. The model looks up which technology fits before it guesses, and gets a correction hint when a query hits a known wall. |
Same endpoint, same tokens. Pick the one your people already use.
Paste the URL and connect. The sign-in is standard OAuth, and the client works out the rest by itself.
# Add a custom connector
https://your-gateway/mcp
Download the connector bundle from the licensing portal and open it. No config file to hand-edit, no JSON to get wrong.
# One click, from the portal priority-gateway.mcpb
ChatGPT and Gemini reach the gateway through their MCP support, and so does anything else that speaks the protocol over HTTP. Build your own agent on the same three tools.
# Streamable HTTP POST /mcp Authorization: Bearer gct_…
The token that clears the REST API clears MCP too. Nobody types a Priority password into an AI tool.
A gct_ token pins the Priority server, the user, the company and the language it was minted for. Mint it at the gateway's connect page or in the licensing portal; the default life is 365 days. A leaked token cannot be pointed at a different tenant.
Revoke a person from the portal or the API and the next request fails. Repoint a server and every token on it is revoked with it, so a stale token can't keep dialing the address it was minted against.
Turn on consent gating and signing in requires a pasted token, which ties every AI session to a real Priority user rather than to whoever found the URL.
Issued tokens are kept in an encrypted store, so redeploying the gateway doesn't disconnect anyone. The file on its own is useless to whoever takes it.
Four facts worth checking before you wire anything.
Three tools in place of twenty-three, with nothing lost.
Not a separate install, a separate licence, or a separate service to run.
Connected clients stay connected through a redeploy.
By construction, not by policy. Mutating verbs never reach Priority.
The /mcp endpoint your client connects to runs on Amazon Web Services, with Cloudflare in front of every request.
The hosted gateway runs in Amazon's Tel Aviv region. Passwords and keys are kept in Amazon's encrypted store, never in a config file.
Every request comes through Cloudflare first. It encrypts the traffic, absorbs attacks and filters out bots, and it shortens the trip from wherever your people are.
The servers accept no incoming connections at all. They dial out to Cloudflare, and traffic comes back down that same line, so there is no public door to find. Admin screens sit behind a second lock.
Running the gateway yourself? This ships inside it, and reaches the outside world the same way, without opening a port on your network.
One registration connects your team to Priority through AI. These products are already built on the surface this page describes.
Riding the same three tools
One sentence to a runnable app on your own Priority forms.
The same tools, the same tokens, in whatever you build next.
See the whole suite on the portfolio hub, or read what sits underneath this surface on the Priority Gateway page.