Skip to content

Cursor and Grok Bot

The Inkbox plugin connects Cursor and Grok Bot to an Inkbox identity through MCP. It gives the selected identity access to configured email, SMS/MMS, voice, iMessage, contacts, notes, and Agent-to-Agent (A2A) capabilities.

The plugin connection belongs to your Cursor account, so the same Inkbox integration can be available in both agent experiences.

Open Inkbox in Cursor

Connect Cursor

  1. Open the Inkbox listing in the Cursor Marketplace.
  2. Install Inkbox from Cursor's Customize view.
  3. Enable the Inkbox MCP server and select Connect.
  4. Authorize an Inkbox organization and identity in your browser.

No local gateway, API key, or separate process is required.

Connect Grok Bot

  1. In Grok Bot, open Plugins from the sidebar.
  2. Search for Inkbox and add the plugin.
  3. When Grok Bot asks you to authorize the connection, complete the browser flow.
  4. Choose the Inkbox organization and identity the Bot should use, then select Allow.

If a team policy disables the plugin, ask your Cursor team administrator to allow Inkbox before connecting it.

Start an automation from Inkbox events

Use a webhook-triggered Cursor Automation when incoming Inkbox events should start an agent run automatically. This setup works with the Inkbox identity you selected for Cursor or Grok Bot.

1. Open Automations

Choose the agent experience you use:

  • Cursor: Open Automations from the left sidebar, then create a new automation named Inkbox Event.
  • Grok Bot: Press Shift + Command + I to open Automations, then create a new routine named Inkbox Event.

You can also open the new automation page directly.

2. Configure the automation

  1. Add a Webhook trigger.
  2. Make the Inkbox MCP server available to the automation.
  3. Paste the prompt below into the automation instructions.
  4. Save the routine or automation.
TextText

3. Copy the webhook credentials

From the automation's Webhook trigger, copy both:

  • the webhook URL, which starts with https://api2.cursor.sh/automations/webhook/
  • the generated Authorization header

Inkbox accepts either the raw crsr_... secret or the complete header:

TextText

4. Configure the selected Inkbox identity

During the Inkbox authorization flow:

  1. Choose the organization and identity the automation should use.
  2. Leave Set up webhook automation enabled. It is on by default.
  3. Paste the automation webhook URL.
  4. Paste the raw auth secret or complete Authorization header.
  5. Copy the automation prompt if you still need it, then select Allow.

Inkbox replaces the selected identity's existing webhook subscriptions with the following preset in one operation:

ChannelEvents
Callscall.ended
Agent2Agenta2a.task.created, a2a.task.message, a2a.task.canceled, a2a.sent_task.updated
iMessageimessage.received, imessage.reaction_received, imessage.delivered, imessage.delivery_failed
Emailmessage.received, message.bounced, message.failed

All four subscriptions use the same automation URL and auth secret. If the setup fails, Inkbox leaves the connection on the authorization page so you can correct the values and try again.

5. Activate the routine or automation

Return to the routine or automation page and turn on the toggle at the top. Confirm that it shows as active before waiting for a new Inkbox event.

What the connected agent can do

Depending on the capabilities configured for the selected identity, the agent can:

  • Search, read, send, reply to, and forward email
  • Read and send SMS/MMS and iMessage
  • Place phone calls and review call history and transcripts
  • Look up, create, and update contacts and notes
  • Find other agents and delegate work over A2A

Every action follows the selected identity's Inkbox access and reachability controls.