Skip to main content

How it works

Clearskies publishes an official plugin for Cursor and Grok Bot. It connects to your Clearskies Context Graph through one MCP server, so account research, meeting prep, pipeline review, and workflow building work from the same context as every other AI client you use: Salesforce or HubSpot records, call transcripts, Gmail and Outlook threads, calendar events, Slack conversations, and support tickets, already resolved to the right account, contact, and deal. Grok Bot is xAI’s persistent AI teammate. Each Bot runs on a persistent cloud computer, keeps context across sessions, and finishes work inside your real tools. There are two ways to connect, and both reach the same Clearskies MCP server:
  • Clearskies plugin (recommended): bundles the MCP server with skills for account research, meeting prep, pipeline review, call recaps, workflow building, and Salesforce field updates.
  • Custom MCP server: add the Clearskies MCP URL directly. Use this when your workspace has not enabled the plugin, or when a team admin manages MCP access through an allowlist.
Either way, Clearskies reads the systems your team has chosen to sync and cites its sources in every answer. Outreach is drafted for your approval; it is not sent on your behalf.

What you’ll need

  • Cursor 3.13 or newer, or the Grok Bot desktop app (macOS, Windows, or Linux) or mobile app, signed in. Grok Bot is included with paid Cursor plans and with linked SuperGrok subscriptions. See xAI’s plans page for the current matrix.
  • A Clearskies account with at least one data source connected
  • For the custom MCP route: the Clearskies MCP URL (view it here)

Install the Clearskies plugin

1

Open Plugins

In Cursor, open Settings, then Plugins. You can also run /add-plugin clearskies.
2

Install Clearskies

Search for Clearskies and select Install.
3

Sign in to Clearskies

A browser window opens. Sign in with Google or Microsoft using the email domain your Clearskies workspace is registered under. There is no client ID, secret, or token to paste, and the plugin does not store your credentials.
Installing in one app does not carry over to the other.

Add Clearskies as a custom MCP server

Copy your MCP URL from MCP in the Clearskies sidebar and add it as an MCP server in Cursor. See MCP server.

What the plugin includes

One MCP server and three skills. You do not need to remember skill names; describe the outcome and your AI picks the right one. The custom MCP route gives you the same data access with no skills attached.

For Grok Bot team admins

On Grok Bot team plans, admins control which plugins members can install and which MCP servers a Bot may reach.
  1. Enable Clearskies on the team plugins page so members can add it from Connect apps.
  2. If your team enforces an MCP allowlist, add https://mcp.clearskies.cc/mcp to it.
  3. Each member then signs in to Clearskies with their own work email. Each member only gets answers from what their Clearskies workspace has synced.

Start asking

Once connected, ask in plain language. For example:
  • “Research Acme Corp before my call tomorrow: stakeholders, deal status, and what is unresolved.”
  • “Prep me for my next meeting: pull the last call, the open items, and suggest an agenda.”
  • “Review my pipeline and rank open deals by risk. Which one needs attention today?”
  • “Recap that call with Acme and draft the follow up.”
  • “What changed in this deal over the last 30 days?”
  • “Build a workflow that posts a Slack summary after customer calls.”
Because a Grok Bot keeps context across sessions, you can also give it a standing job: “Every Monday at 8am, review my pipeline in Clearskies and leave me a risk summary.” Grok Bot saves the path as a routine and reruns it on schedule.

Good to know

  • Results reflect what your team syncs. “Not found” can mean the information is not synced into Clearskies, not that it is missing from the source system. See Data governance and controls.
  • Your data sources stay in Clearskies. Salesforce, Gong, Google, Microsoft, Slack, and your other sources are connected in your Clearskies workspace settings, not in Cursor or Grok Bot.
  • Read before write. Outreach is drafted, never sent. Workflow changes are drafted, validated, and tested before publication, and a live workflow is published only with your explicit approval.
  • Builder actions (creating or publishing workflows and agents) require Clearskies workspace admin access, separate from any Grok Bot team admin role.
  • Credits. Data tools use workspace credits. A workspace that is out of credit gets a refusal instead of an answer.
  • Grok Bot, not Grok chat or Grok Build. The Grok Bot steps on this page cover the Grok Bot app only.

Other clients

The plugin follows the open Agent Plugins format, so it also loads in Claude, ChatGPT, and other compatible clients. See the Claude and ChatGPT pages.

You’re all set

Cursor and Grok Bot now have access to your unified Context Graph. See what your AI can access over MCP for the full list of capabilities. For Grok Bot’s own documentation on plugins and the shared computer, see Use the computer and apps. Questions? We’re here to help at support@clearskies.cc