Let users connect your agent to their Claude, ChatGPT or AI app
What it does
A visitor can open your deployed agent, choose Use with an AI app, and copy a personal MCP connection for Claude Code, Codex, Cursor, or VS Code.
Before this
API/MCP deployments already let builders connect a client. The visitor-facing option on embeds, direct links, and Portals was previously limited to staff.
Why it matters
Your customers can use the agent inside tools they already work in while Pickaxe applies their access and usage limits.
How to offer it to your users
Open the deployment or Portal Design tab. Under Submission Through MCP, turn on Show AI app option. New direct links and embeds have the option enabled by default.
When someone opens the agent, the terminal icon in its header opens Use this agent in your AI app. They choose their app and copy the setup command or MCP configuration. The connection gives that client access to this deployed agent.
- Who it runs as
- Requests run as the signed-in member or visitor who opened the agent, with that person's deployment access and usage allowance.
- Keep it private
- The copied configuration contains a Studio session token. Each user should make their own connection, keep the token private, and reconnect when the session expires.
Connecting from ChatGPT
ChatGPT has its own custom MCP app setup. For a Business, Enterprise, or Edu workspace, an admin or owner enables developer mode. The admin or owner, or an authorized Enterprise or Edu developer, can create and test a custom app using a remote MCP endpoint and supported authentication. Only an admin or owner can publish it for workspace members.
ChatGPT is not in this Pickaxe client picker. Its copied Claude Code and Codex configurations contain short-lived session tokens and are not a ready-made ChatGPT connection. Before telling users they can connect from ChatGPT, confirm that your deployment has an authentication flow ChatGPT supports.
Read OpenAI's ChatGPT MCP setup guide