Guides

Use Crispy with an OpenAI dot

Set up Crispy as a custom MCP app, then check whether it is available to your dot before assigning LinkedIn work.

What a dot can do

A dot is an always-on agent with its own cloud computer and browser. Its cloud work can continue while your devices are off. A dot can use supported plugins that are installed and enabled for your account, within their existing permissions.

Availability

Dots are rolling out gradually. OpenAI currently lists Pro 100, Pro 200, and Pro 500 for users over 18 outside the European Economic Area, United Kingdom, and Switzerland. Business Premium and Enterprise are rolling out worldwide. Enterprise dots are off by default and require a workspace administrator to enable them.

Custom MCP access is a separate gate. OpenAI currently limits full write MCP to eligible Business and Enterprise or Edu workspaces. Pro custom apps are read or fetch only, and managed workspaces control developer-mode access.

Before you connect

Create or sign in to your Crispy account.
Connect the LinkedIn profile you want the dot to use.
During OAuth, confirm that you select the correct Crispy account.

Preferred setup with MCP and OAuth

Confirm that your plan and workspace permit custom MCP apps. In ChatGPT, open Settings → Apps → Advanced Settings and enable developer mode. Managed workspaces may require an administrator to grant access first.
Open Settings → Apps → Create and start a custom app named Crispy.
Enter https://crispy.sh/api/mcp as the MCP server endpoint and choose OAuth.
Select Scan Tools, complete the Crispy OAuth flow, select the intended account, and wait for the tool scan to finish.
Review the discovered tools and permissions, then select Create.
Open your dot's profile and review its available plugins. Use Crispy only if the custom app appears there and is enabled. OpenAI documents that dots can use supported plugins installed for the account. It does not guarantee that every custom MCP app is available to every dot.

Keep credentials in the OAuth flow. Never put an API key in a conversation.

Start with a read-only task

Use a narrow prompt that names both the allowed work and the actions that remain off limits.

Use Crispy to call list_conversations and summarize my recent LinkedIn inbox.
Group conversations into urgent, follow-up, and no action. Draft suggested replies when useful.

This is a read-only and draft-only task. Do not send messages, send invitations, publish
posts, delete anything, or launch a campaign. Ask for my explicit approval before any
action that changes LinkedIn or contacts another person.

Keep consequential actions behind approval

Begin with research, summaries, and drafts. Review the proposed audience and exact copy before allowing a write. Require explicit human approval for sends, invitations, posts, campaign launches, deletion, purchases, and any other consequential action.

Advanced connected-computer option

A dot can also work through a connected computer. On a computer where the Crispy CLI is already authenticated, the dot can use that existing setup. The computer must remain online and the ChatGPT app must stay open. This route is useful for advanced local workflows, but MCP with OAuth is the simpler default.

Advanced REST option

Custom workflows can call the Crispy REST API at https://crispy.sh/api/v1. Use a secure secret store and the documented authorization flow. REST is best for code you control, not for credentials shared in chat.

Troubleshooting

If Crispy is missing from the dot's available plugins, that custom app is not available to the dot on your current account. Use the connected-computer option above or wait for supported plugin availability.
If tools are unavailable, check plan, rollout, and workspace policy.
If OAuth opens the wrong profile, disconnect and authorize the correct Crispy account.
If a connected computer stops responding, confirm it is online and ChatGPT is open.
For Crispy errors, see the troubleshooting guide.

Search documentation