← Back to blog
GuideOctober 8, 20266 min read

How to connect LinkedIn to OpenAI dots with Crispy

Connect LinkedIn to OpenAI dots through Crispy with MCP and OAuth. Check eligibility, follow the setup, and keep external actions under human review.

By Daan

An OpenAI dot can coordinate ongoing work, and Crispy can provide the LinkedIn tools it uses for research, inbox triage, content drafting, and reviewed outreach. The connection is conditional: Crispy must be available as an enabled custom MCP app for the dot and account you intend to use.

Check eligibility before setup. OpenAI says dots are rolling out by plan, age, region, and workspace, while administrator policy can control whether a workspace may use them. Read the OpenAI dots documentation beside those conditions. Custom MCP access has its own plan and workspace restrictions, described in OpenAI's developer mode and MCP app guidance. Availability can change, so those first-party pages are the current source of truth.

The preferred route is MCP with OAuth. In ChatGPT settings, enable developer mode if your workspace permits it, create a custom app, enter `https://crispy.sh/api/mcp`, choose OAuth, scan the available tools, and review the permissions before creating the app. Then confirm that Crispy appears as an enabled plugin for the dot. The step-by-step screens and troubleshooting paths are in the OpenAI dots guide.

OAuth keeps the authorization step outside the conversation. It lets you sign in to Crispy, choose the intended account, and review access without putting an API key into a prompt or message. If the custom app is missing from the dot, treat that as unavailable on the current account rather than assuming that installation succeeded.

Start with work that does not contact anyone: research relevant people, summarize recent conversations, group inbox items by urgency, or draft a post for review. A useful first instruction should explicitly forbid sending messages or invitations, publishing posts, deleting data, buying anything, and launching campaigns.

Add write actions only after the read-only result is correct. Before every consequential action, review the target account, intended audience, exact copy, and scope. A person should explicitly approve messages, invitations, posts, deletions, purchases, campaign launches, and any other external change.

For an already-authenticated connected computer, the Crispy CLI is an advanced alternative. Custom software can use Crispy's REST API at `https://crispy.sh/api/v1` with secrets held in secure storage. Neither route changes OpenAI's eligibility rules, and MCP with OAuth remains the clearest starting point for a dot.

Crispy is an independent product. It is not affiliated with or endorsed by LinkedIn or OpenAI, is not claimed to be publicly listed in an OpenAI marketplace, and is not guaranteed to be available to every dot, plan, region, or workspace.

Frequently asked questions

Can I connect LinkedIn to an OpenAI dot?

You can connect a dot to LinkedIn through Crispy when the Crispy custom MCP app is available, installed, and enabled for that dot. Plan, rollout, region, age, and workspace policy can still restrict access.

How should an OpenAI dot connect to Crispy?

Use Crispy's MCP endpoint with OAuth. Complete authorization outside the conversation, select the intended Crispy account, review the discovered tools and permissions, and confirm the app is enabled for the dot.

What should an OpenAI dot do first on LinkedIn?

Begin with research, inbox summaries, and drafts. Require explicit human approval before messages, invitations, posts, deletion, purchases, campaign launches, or any other action that changes LinkedIn or contacts another person.

What if Crispy does not appear for my dot?

Check the current OpenAI plan, regional rollout, developer-mode setting, and workspace policy. If Crispy still does not appear as an enabled plugin, do not assume the dot can use it on that account.

Run LinkedIn workflows from the AI client you already use.

Create your account, connect LinkedIn, create an API key, then add Crispy to your client. Review the docs for supported workflows and safety controls.