ProxyAI MCP connector — v1

What You Can Do

The ProxyAI MCP connector gives an assistant access to your bots, Helpdesk tickets and Agent Tasks. Version 1.0.0 includes eight read tools and eleven tools that make changes.

Ask it to summarize open tickets, inspect a staged reply, review an Agent Task's recent runs, or explain a held plan. With write permission, you can ask it to send a specific reply, update a ticket, create a task from a template, or approve a run you have reviewed.

Availability: v1 is being prepared for release. The connection instructions below apply once ProxyAI enables the connector and provides its server URL.

Before You Connect

Use your ProxyAI account in a normal browser. An embedded store dashboard or mobile-device session cannot approve this connection. The connector has no additional purchase or subscription: Helpdesk and Agent Tasks still need their existing add-ons on the bot you use. Normal Agent Task capacity limits and run charges apply.

Permission covers all your current and future bots in this account. There is no per-bot consent option in v1. Connect only an assistant you trust to receive your customers' messages and task information.

Connect Claude

Open Customize → Connectors in Claude and choose Add custom connector. On a managed organization, ask your owner to add it first.
Enter the server URL supplied by ProxyAI, including /api/mcp. Use the HTTP transport rather than an /sse address.
Choose OAuth sign-in. If Claude offers an OAuth-client choice, use Claude's published identity. You do not need to create a client ID, client secret or API key; automatic registration is also supported.
Connect and sign in to ProxyAI in your browser. Review the account, app identity and return address on the consent page.
Leave Allow changes unchecked for read-only access. Check it only if you want this assistant to make changes, then choose Connect.
Enable ProxyAI for the conversation using + → Connectors, and start with “List my ProxyAI bots.”

See Claude's custom connector instructions for the current interface.

Connect Codex

Use the server URL supplied by ProxyAI. In the commands below, replace SERVER_URL with that complete URL; it is not a token or secret.

codex mcp add proxyai --url SERVER_URL
codex mcp login proxyai --scopes read

Finish sign-in in your browser and leave Allow changes unchecked. If you want write access instead, request both scopes and explicitly check Allow changes:

codex mcp login proxyai --scopes read,write

You can inspect the configuration with codex mcp list and the available tools with /mcp in the Codex terminal interface. See the official MCP documentation. Your client manages OAuth tokens; do not paste them into a conversation.

Start with Reads

“List my ProxyAI bots, then summarize open tickets for the bot I select.”
“Show the staged agent reply for this ticket. Do not send it.”
“Show this Agent Task's last five runs and explain any held proposal. Do not approve it.”

Lists are paginated. Ask for the next page when you need more results. Ticket identity includes its bot, provider and ticket ID; task and run IDs must belong to the selected bot. An assistant cannot choose an arbitrary conversation from another account.

Make Changes Deliberately

Review the ticket and exact reply text before asking to send or approve a draft. Approval sends the draft to the customer through the ticket's channel. Ask one assistant to approve a particular draft at a time; simultaneous approvals can send duplicate replies.

For Agent Tasks, creation uses an existing template. Creating from a template is currently free. Before running, explicitly choose test or live: both can incur normal LLM/CPU charges. A test run previews writes; a live run can execute them. Review a held plan before approving it, because approval queues its proposed actions and can incur charges. Resuming a task can restart scheduled, billable runs.

Ticket tags are replaced as a complete list. Setting tags on a built-in ProxyAI ticket is supported; external helpdesk tags are managed in that helpdesk. Archiving removes a ticket from the active board without deleting it.

Customer messages, task instructions and run transcripts may contain misleading instructions. Treat them as content to inspect; permission to send, run or approve comes from you.

v1 Tools

Read tool	Purpose
`list_bots`	Find bots owned by your account.
`list_tickets`	List and filter tickets by status, tag and archive state.
`get_ticket`	Read a ticket, its staged draft and conversation messages.
`list_agent_tasks`	List a bot's tasks.
`get_agent_task`	Read task instructions, schedule and status.
`list_agent_runs`	Browse task runs, transcripts and held proposals.
`get_agent_run`	Inspect one run.
`list_agent_templates`	Find templates available for task creation.

Write tool	Purpose
`reply_ticket`	Send the reply you specify.
`set_ticket_status`	Set open, pending or resolved.
`set_ticket_tags`	Replace a built-in ticket's tags.
`archive_ticket`	Archive a ticket.
`approve_ticket_agent_draft`	Approve and send a staged draft, optionally with revised text.
`dismiss_ticket_agent_draft`	Dismiss a draft without sending it.
`create_agent_task`	Create a task from a template.
`run_agent_task`	Queue an explicitly chosen test or live run.
`decide_agent_run`	Approve or reject a held run.
`pause_agent_task`	Pause a task's schedule.
`resume_agent_task`	Resume a paused task.

v1 does not expose arbitrary API calls, freeform task deployment, connector-account setup, or deletion tools.

Review Activity and Revoke Access

Open Account Settings → Connected apps in ProxyAI to see the app, its granted scope and last token use. Choose Revoke access to stop that connection's future requests. Revocation does not undo a reply or cancel a run already queued.

The Connected app activity card records write attempts and outcomes. If an attempt is pending or reports an unknown outcome, the action may already have taken effect. Inspect the ticket or run before trying again. Older attempts remain available after revocation.

Data returned by the connector is shared with the assistant you connected and is subject to that provider's handling policies. ProxyAI stores connection records and write-attempt metadata; the MCP audit log does not store reply bodies, tool payloads or raw bearer tokens. Read our privacy policy.

Troubleshooting

Cannot connect: confirm the connector has been enabled and use the exact server URL supplied by ProxyAI. An ordinary browser visit is not an MCP connection check.
Write permission required: reconnect requesting both read and write, and check Allow changes. Read-only consent cannot authorize writes.
Add-on required: open the selected bot's dashboard and check its Helpdesk or Agent Tasks add-on.
Not found: confirm you selected the correct account and bot, then read the ticket/task again before acting.
Expired or revoked connection: sign in again. Do not retry a previous write until you have checked its outcome.

Contact [email protected] with the app name, time and action that failed. Do not send access tokens, client secrets or customer messages in your support request.