How to connect LinkedIn to Grok Bot with Crispy
Connect LinkedIn to Grok Bot through Crispy with MCP and OAuth. Check connector access, follow the setup, and keep external actions under human review.
By Daan
Grok Bot can plan and coordinate tasks in its cloud environment. Crispy adds a focused LinkedIn interface for finding people, reviewing conversations, preparing content, and carrying out approved outreach. This works only when the signed-in Grok account can use the custom Crispy connector.
Confirm access before relying on the integration. The xAI Grok Bot overview describes the product and its current access model. Plans, regional availability, rollout status, team policy, and administrator controls may differ by account. xAI's connector documentation and MCP server documentation are the first-party sources for current connector and MCP behavior.
For the preferred setup, open `grok.com/connectors`, create a custom connector, and enter `https://crispy.sh/api/mcp` as the public MCP URL. Complete Crispy's OAuth flow, select the correct Crispy account, inspect the requested access, and approve it. Install the private connector for Grok Bot only if it is visible to your account, then attach Crispy to the task with `@Crispy`. Follow the detailed Grok Bot guide for the full sequence.
OAuth prevents a credential from becoming chat content and gives you a deliberate account-selection and permission-review step. If the connector is absent from Grok Bot's plugins or cannot be attached to a task, treat it as unavailable under the current account or workspace policy.
Good first jobs are narrow and reversible: collect background on a prospect list, summarize an inbox, identify conversations that need attention, or prepare alternative replies. Tell Grok Bot to stop at drafts and state which actions it must not perform without another approval.
When you later allow writes, approve the precise action instead of granting a broad standing instruction. Verify the LinkedIn account, recipients, wording, and batch size before messages, invitations, posts, deletions, purchases, or campaign launches can proceed.
Grok Build CLI can connect to remote HTTP MCP servers and is an advanced option for developer-controlled work. Crispy's REST API is available for custom applications that keep secrets outside chat. These alternatives do not guarantee that the Grok Bot connector is enabled for a particular account.
Crispy has no affiliation with or endorsement from LinkedIn or xAI. Creating a private connector does not mean Crispy has public Grok marketplace placement, and no claim of universal connector availability is made.
Frequently asked questions
Can I connect LinkedIn to Grok Bot?
You can connect Grok Bot to LinkedIn through Crispy when the custom Crispy connector is available to the signed-in Grok account and can be attached to the task. Account, plan, region, rollout, and team controls may restrict access.
How should Grok Bot connect to Crispy?
Create a custom connector with Crispy's public MCP endpoint, authorize it through OAuth, review the selected account and permissions, and attach Crispy to the task only after the plugin is available.
What is a safe first Grok Bot task for LinkedIn?
Ask for research, an inbox summary, or drafts, and prohibit external writes. Require a person to approve the exact recipients and copy before any send, invitation, post, deletion, purchase, or campaign launch.
What if the Crispy connector is missing in Grok Bot?
Check connector authentication, plan and regional access, and workspace policy. If the plugin remains absent, do not infer that a private connector is automatically available to Grok Bot on that account.
Related articles
OpenAI dots vs Grok Bot for LinkedIn with Crispy
Compare OpenAI dots and Grok Bot for LinkedIn work with Crispy, then choose the focused setup guide for your AI platform.
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.