Get started
GrokBot Cursor
Download Exeora's separate Cursor-format plugin and follow the verified Cursor and Grok Bot installation paths.
Connect Exeora remote projects with three guided skills. GrokBot Cursor is this distribution's visible name; grokbot-cursor is its package identifier.
GrokBot Cursor
Version 1.0.0 · Remote MCP + 3 skills
SHA-256 checksum · Package details · All five distributions
Install in Cursor#
- Download and verify the ZIP, then extract its contents into a new
~/.cursor/plugins/local/grokbot-cursorfolder, including the hidden.cursor-plugindirectory. Avoid an extra enclosing folder. - Restart Cursor or run Developer: Reload Window. Open Customize and check the three skills and Exeora MCP. Local imports must be allowed by existing organization policy. A marketplace install with the same name takes precedence.
- Follow Cursor's connection/OAuth prompts. Ask it to list your authorized Exeora projects to verify access.
For repository distribution, Teams/Enterprise can use Dashboard > Plugins & MCPs > Team Marketplaces > Add Marketplace > Import from Repo with https://github.com/leynier/exeora, subject to existing policy. The root Cursor marketplace points to this package. Users install approved entries in Customize. Public listing requires Cursor's separate review.
Grok Bot: catalog availability required#
The official Grok Bot guide describes Plugins > browse/search > add > Authorize or Authenticate > Installed. Use that flow only if Exeora is actually available in your account's catalog; use Reopen if authorization is waiting.
That guide does not document custom ZIP uploads, local Cursor folders or arbitrary repository imports into Grok Bot. This package is prepared in Cursor's format; Grok Bot ingestion, skill loading and availability remain unverified. Installing in Cursor or sharing an account does not establish Bot access.
Remote MCP and verification#
The root mcp.json contains only https://exeora.dev/mcp. Authentication is handled by the host, without packaged headers, static credentials or variables. Exeora projects must be served by exeora connect or Exeora Cloud; they are separate from Cursor's local checkout.
The included Exeora logo uses Cursor's documented relative logo field. The exact visible name uses displayName, as in Cursor's official template; the current reference table omits that field. Host rendering is not verified.
Package, download and browser tests do not prove installation or real OAuth in either surface. No marketplace submission, account grants or persistent permissions were changed. See the bundled README, format reference, installation guide and MCP reference.