crispy

Search documentation

Jump to any section of the Crispy docs

Guides

Connect Crispy to Grok Bot

Add Crispy as a custom connector, attach it to a task, and keep consequential LinkedIn actions behind human approval.

What Grok Bot can do

Grok Bot uses a persistent cloud computer with a browser, filesystem, and terminal. Bots can use connectors or MCP where those features are available.

Availability

Grok Bot requires an eligible SuperGrok, Cursor, or Cursor Teams plan. Enterprise access is still rolling out. Plan names, regional availability, usage, and administrator controls can change, so check the current xAI access details before setup.

Before you connect

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

Add the custom connector

  1. Open grok.com/connectors.
  2. Choose New Connector, then Custom.
  3. Enter https://crispy.sh/api/mcp as the public MCP URL.
  4. Complete OAuth, select the intended Crispy account, review permissions, and approve.

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

Install Crispy in Grok Bot

Grok Bot installs connectors as plugins. Open Marketplace from the sidebar, find the custom Crispy connector, choose Add, and complete browser authentication if requested. Then type @ in chat to attach Crispy to the task. Private connector visibility can vary with account and workspace policy. If Crispy does not appear, do not assume the connector is available to Grok Bot on that account.

Start with a read-only task

@Crispy Call list_conversations and summarize my recent LinkedIn inbox.
Identify priority replies and prepare drafts for my review.

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.

Begin with research, summaries, and drafts. Require explicit human approval before sends, invitations, posts, campaign launches, deletion, purchases, or any other consequential write.

Bots share one user-scoped computer

Security boundary

Installed connectors are account-wide. Multiple Bots share one user-scoped computer, including its files and app logins. Do not separate sensitive roles merely by creating another Bot. Bots are not security boundaries.

Team and enterprise controls

Team policy can disable MCP, prevent members from adding servers, or require an allowlist. If setup is blocked, ask an administrator to allow https://crispy.sh/api/mcp and confirm members may use the connector.

Advanced Grok Build CLI option

Grok Build CLI supports remote HTTP MCP and handles OAuth automatically. This is an advanced alternative to the Grok Bot connector flow.

grok mcp add --transport http crispy https://crispy.sh/api/mcp
grok mcp doctor crispy

Advanced REST option

Custom workflows can call https://crispy.sh/api/v1. Store secrets securely and use REST for code you control, not for credentials shared in chat.

Troubleshooting

  • If Crispy is absent from Plugins, check connector authentication and workspace policy.
  • If adding the server is blocked, ask a team admin about member-added servers and the MCP allowlist.
  • If a task cannot find Crispy, attach it explicitly with @Crispy.
  • For CLI diagnostics, run grok mcp doctor crispy.
  • For Crispy errors, see the troubleshooting guide.

Platform sources