Skip to main content
The Inkbox Cursor plugin connects Cursor to an Inkbox identity through a remote MCP server. It gives Cursor 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 you can use the same Inkbox integration in Cursor and Grok Bot.
The video shows an earlier Grok Bot interface. Follow the routine setup steps below for the current flow.

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. Choose an Inkbox organization and identity in your browser.
  5. Select Allow.
No local gateway, API key, or separate process is required for the Cursor connection.

​
Connect Grok Bot

  1. Open Plugins in Grok Bot’s sidebar.
  2. Search for Inkbox and add it.
  3. Complete the browser authorization flow.
  4. Choose the organization and identity and select Allow.
To let your bot react to incoming messages automatically, finish setting up its routine after connecting. If your team has disabled the plugin, ask your team administrator to allow it. See Connect plugins in Grok Bot.

​
Connect another identity

Authorize another connection and choose the identity you want that bot to use. Existing connections stay signed in, including other connections using the same identity. There is no add-or-replace choice on the authorization page. Reauthorizing does not revoke an earlier connection. The Inkbox Console does not currently provide an OAuth connection management page.

​
Start an automation from Inkbox events

Connecting authorizes tool access without creating or replacing webhook subscriptions. Set up event-triggered routines after connecting.

​
Let Grok Bot set up its webhooks

Connecting Inkbox alone does not enable automatic reactions to incoming messages. Grok Bot can create the routine, but you need to copy its URL and key from the routine’s details and paste them into your chat.
  1. Ask your bot to create the routine. After connecting Inkbox, send this prompt in your Grok Bot chat:
  2. Find the routine’s URL and key. Once your bot has created the routine, click your bot’s name at the top of the chat. Open Details → Routines → Inkbox events. Copy the values labeled POST to and key.
  3. Paste both into the same chat. Your bot uses them to finish the Inkbox webhook setup. Wait for it to confirm that the webhook subscription is configured and the routine is active.
Use the routine’s key, not an Inkbox API key. Review any existing webhook configuration before approving replacement. Your bot’s actions still follow your existing instructions and approval requirements. Read the Grok Bot docs on routines.

​
Verify setup

The bot registers the routine through inkbox_grokbot_set_webhooks, available on https://inkbox.ai/mcp/cursor. It passes the POST to URL as webhook_url and the raw key as secret, without the Bearer prefix. Initial setup leaves replace_existing at its default, false. A successful registration returns the expected identity_id, a positive subscription_count, and has_secret: true. The bot should also confirm that the routine is active in Grok Bot. Registration alone does not prove that an event was delivered. Ask your bot to perform a test only when you are ready for the routine to run. If inkbox_identity_get omits webhook_setup, that does not prove that this bot’s routine is active. Existing or partial subscriptions can also cause the setup guidance to be omitted.

​
Routine instructions

The routine uses these default instructions:

​
Default events

The setup tool subscribes to these events using the routine’s URL and secret: Inkbox added the SMS events to existing subscriptions that still used the earlier preset, so you don’t need to rerun setup to receive texts.

​
Replace webhooks from a connected bot

In Cursor or Grok Bot, use inkbox_grokbot_set_webhooks to send the connected identity’s notifications to a new HTTPS webhook URL. This tool is available only through https://inkbox.ai/mcp/cursor, including identity-scoped API-key connections. Supply webhook_url and the receiver’s raw bearer token as secret. The general tool also supports receivers without bearer authentication: omitting secret configures delivery without a bearer token. replace_existing defaults to false. If any active subscription already exists for the connected identity, its mailbox, or its phone number, the tool refuses to change the configuration. This protects custom receivers and presets created by another bot alike. To deliberately replace an existing setup, first review the affected subscriptions and approve the reset. The bot can then call the tool with replace_existing: true. This replaces all existing webhook subscriptions for the connected identity, including its mailbox and phone number. It affects every connection sharing that identity, not just the bot making the change. Supplying the argument does not replace your permission or any approval card. When identity-wide subscriptions are available (supports_identity_subscriptions: true in GET /webhooks/catalog), replacement creates one identity-owned subscription with the default event preset above, regardless of which channels are enabled. This includes the SMS events, so the routine starts when a text arrives. Otherwise, it creates separate subscriptions for iMessage, call-lifecycle, and Agent2Agent events, plus email events if the identity has a mailbox. This fallback mode does not add SMS subscriptions. Both modes replace the selected identity’s existing subscriptions. Both modes also remove existing Slack subscriptions without adding Slack events. Neither mode changes how incoming calls are answered.

​
What Cursor can do

Depending on the capabilities configured for the selected identity, Cursor 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.