Gorgias integration for AI agents.
Gorgias integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Gorgias tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real Gorgias actions, managed and audited.
Your user connects Gorgias once; your agent can then use Gorgias to manage customers, tickets, messages, tags, users, integrations, and account support workflows — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants Gorgias access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported Gorgias tools.
15 tools are generated from the published Gorgias catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 15 tools. All published catalog entries are included in this page's server-rendered HTML.
- Create a customer
- Create a customer
- Customers
- Create a tag
- Create a tag
- Tags
- Create a ticket
- Create a ticket
- Tickets
- Create a message
- Create a message and either: - not send it if the attribute `sent_datetime` is filled. If you import a message that was already sent, make sure to set this value. - send it to the recipients if the attribute `sent_datetime` is empty. - add it to the ticket as an internal note if you specified this channel. Internal notes are not sent to your customers. When a message is created, it does not mean that this one has been sent because the creation and sending process are decoupled. Messages are basically sent asynchronously. Once a message has been sent, Gorgias will automatically update the message to fill the time when it was sent (`sent_datetime`).
- Ticket Messages
- Retrieve your account
- Retrieve your account
- Account
- Retrieve a customer
- Retrieve a customer
- Customers
- Retrieve a ticket
- Retrieve a ticket
- Tickets
- List customers
- List customers, paginated, and ordered by their name (alphabetical order).
- Customers
- List integrations
- List integrations matching the given parameters, paginated.
- Integrations
- List messages
- List messages matching the given parameters, paginated.
- Ticket Messages
- List tags
- List tags matching the given parameters, paginated, and ordered.
- Tags
- List tickets
- List tickets, paginated and ordered by the attribute of the given view.
- Tickets
- List users
- List users, paginated and ordered by their name (alphabetical order).
- Users
- Update a customer
- Update a customer
- Customers
- Update a ticket
- Update a ticket
- Tickets
Gorgias integration, answered
- How do AI agents use Gorgias through Open Connector?
- Your user connects Gorgias once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Gorgias tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Gorgias MCP server?
- Yes. Open Connector can serve Gorgias as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Gorgias actions with credentials injected server-side.
- Where do Gorgias credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Gorgias — keep the keys.
Open source, self-hostable, with Gorgias credentials that never leave your infrastructure. Run it from source today.