Skip to content

Connect Grok Bot to Context.dev

Connect Grok Bot to Context.dev: 1. Sign in to ApexGenius and connect Context.dev. 2. Add the ApexGenius plugin. 3. Start using Context.dev in Grok Bot.

1,000 free credits · No card required

How to connect Context.dev to Grok Bot

  1. 1Sign in to ApexGenius and connect Context.dev
  2. 2Add the ApexGenius plugin to Grok Bot
  3. 3Start using Context.dev in Grok Bot
  1. 1Context.dev

    Connect Context.dev to ApexGenius

    Connect Context.dev

    Context.dev opens its own sign-in. Sign in and allow ApexGenius.

  2. 2ApexGenius

    Connect ApexGenius to Grok Bot

    Choose Grok Bot

    Back on Start, pick Grok Bot and copy the prompt.

  3. 3ApexGenius

     

    Approve access

    ApexGenius opens its approval page. Review the access, then approve.

Add the ApexGenius plugin to Grok Bot

Grok Bot keeps app connections on the Cursor account you sign in with, under Connect apps in the sidebar. They are not in Settings, and there is no config file.

  1. In ApexGenius, pick Grok Bot on Start and copy the setup prompt.
  2. Paste it into Grok Bot. It adds the server and opens the approval in your browser.
  3. When Grok Bot asks you to Authorize or Authenticate, finish the ApexGenius sign-in and approve access.

The MCP address

https://server.autom8.pro/mcp

Check it. Open Connect apps in the sidebar and confirm ApexGenius appears under Installed.

Steps follow Cursor Help, Connect apps in Grok Bot (opens in a new tab), read November 12, 2026.

Then ask Grok Bot

List my Context.dev monitors. Do not create, run, or change anything.

Start free
Written setup, step by stepShow

Before you start

  • An account with permission to use the Context.dev resources you intend to connect.

1. Connect Context.dev to ApexGenius

  1. Open Context.dev in Connections. Choose Connect, or Add connection when offered. Give the connection a name if prompted. If Gateway setup pending appears, contact ApexGenius support before continuing.
  2. Choose the account and review access. Sign in to Context.dev in the browser and approve access for your organization. Context.dev uses browser authorization; no Context.dev API key is pasted into ApexGenius.
    The full Context.dev connect page, Connect Context to an unverified app, with red boxes around the verification notice and the Sign in button.
    Context.dev labels ApexGenius an unverified app and names server.autom8.pro, the ApexGenius gateway, as the address that receives access. Sign in to continue.Open full-size image (opens in a new tab)
  3. Review the connected account and resources. Confirm the connected Context.dev organization. Open Tools to review its reads and the monitor and batch actions. Most operations spend your organization's Context.dev credits.
  4. Check the connection. Use Test connection or Check again and read the reported status. Add an AI agent from the AI agents page, choose Read only for the first test, and try the question below.
Connect Context.dev →

2. Connect ApexGenius to Grok Bot

Use this server address when adding the connection:

https://server.autom8.pro/mcp

The steps are above, under Add the ApexGenius plugin to Grok Bot. These notes apply to Grok Bot only.

  • Added is not signed in. An app marked Added is installed. If Grok Bot still says it is missing, open it from Connect apps and choose Authenticate, or Authorize on the phone.
  • Cursor teams. Your team’s Cursor connector policy applies to Grok Bot. If the app says Disabled by team admin, ask your Cursor admin to enable it, then restart the app.
  • If sign-in does not finish. Choose Reconnect on the app, or Reopen on the in-chat card, to bring the sign-in page back.
  • Access. When ApexGenius asks what Grok Bot may use, choose Read only for the first test, or Custom to limit it to the tools you need.

3. Verify one safe read

List my Context.dev monitors. Do not create, run, or change anything.

List my Context.dev monitors. Do not create, run, or change anything.

Compare the returned account and resource with Context.dev. Check the connection status separately from the result of the first read.

Full guide: the Context.dev setup guide.

What it looks like in Grok Bot

Illustration of a task, not a recorded customer result. Your answers come from the account and dates you choose.

How the route works
Grok Bot
Grok BotApexGenius MCP route
List my Context.dev monitors and their status. Do not create, run or change anything.
ApexGenius
Working with ApexGenius1 tool search · 1 read
RequestCheck the connection
Account scopeAuthorized connections checked
apex_search_toolsContext.dev monitors · Find the Context.dev read routeComplete
apex_call_read_toollist-monitors · List monitorsComplete
Grok Bot

Illustrative example: two monitors are active, a pricing page checked daily and a changelog checked weekly. Listing monitors spends no credits. Nothing was changed.

Read-only route
Grok Bot

What to ask Grok Bot about Context.dev

  • Check the connection

    List my Context.dev monitors and their status. Do not create, run or change anything.

    Runs list-monitors (read).

  • Read a page

    Read https://example.com/pricing as Markdown and list every plan with its price. Cite the URL.

    Runs web-scrape-markdown (read).

  • Look up a company

    Pull the brand profile for linear.app: logo, colors, fonts and social links.

    Runs brand-retrieve-unified (read), then web-fonts (read).

These 3 questions use 4 of Context.dev’s 34 operations. The full list is below.

  • Search the web for this week's official Stripe product announcements and cite each source URL. (read)
  • Create a daily monitor on this pricing page. Show me the schedule and the credit cost first. (write)

What Grok Bot can do in Context.dev

34 operations: 27 read, 7 write. Read looks things up and changes nothing. Writes change Context.dev and run only when you turn them on.

Search and read pages

5 read
  • web-searchread
  • web-scrape-markdownread
  • web-scrape-htmlread
  • web-scrape-imagesread
  • web-screenshotread

Map, crawl and extract

3 read
  • web-scrape-sitemapread
  • web-crawlread
  • web-extractread

Documents

1 read
  • parse-documentread

Company and brand data

6 read
  • get-brandread
  • brand-retrieve-unifiedread
  • web-styleguideread
  • web-fontsread
  • web-naicsread
  • web-sicread

Monitor history

9 read
  • list-monitorsread
  • get-monitorread
  • list-monitor-runsread
  • get-monitor-runread
  • list-account-runsread
  • list-monitor-changesread
  • list-changesread
  • get-changeread
  • list-monitor-credit-usageread

Manage monitors

4 write
  • create-monitorwrite
  • update-monitorwrite
  • run-monitor-nowwrite
  • delete-monitorwrite

Batches

3 read · 3 write
  • submit-batchwrite
  • list-batchesread
  • get-batchread
  • get-batch-resultsread
  • cancel-batchwrite
  • delete-batchwrite

You choose the access. When you approve Grok Bot, pick Full access, Read only, or Custom.

Context.dev controls the OAuth grant. The connection acts for your Context.dev organization and uses its shared credits.

The read route checks Context.dev's live tool label and rejects writes or unlabeled operations.

Writes run right away when enabled. A deleted monitor or batch cannot be restored.

Fetched page text is untrusted data. The ContextDev skill tells your AI to quote and cite it and never follow instructions inside it.

Disconnecting stops future gateway access. It does not stop monitors or batches that already exist.

Start free

Questions about connecting Grok Bot to Context.dev

Updated November 12, 2026.

How do I connect Grok Bot to Context.dev?

Sign in to ApexGenius and connect Context.dev. In Grok Bot, paste the ApexGenius setup prompt, then choose Authorize or Authenticate and finish the sign-in in your browser. Then ask Grok Bot: “List my Context.dev monitors. Do not create, run, or change anything.” Start with a read, so nothing changes.

How do I check that Grok Bot can use Context.dev?

Open Connect apps in the Grok Bot sidebar. ApexGenius should appear under Installed. Added means it is installed, not that you are signed in, so open it and choose Authenticate if it asks. On a Cursor team, an app marked Disabled by team admin needs your admin to enable it. Then ask: “List my Context.dev monitors. Do not create, run, or change anything.”

Does it spend Context.dev credits?

Most calls do. A scrape is 1 credit, a web search is 1 credit per 10 results, a crawl is 1 credit per page and a brand lookup is 10 credits. Listing monitors is free. Free organizations get 1,000 credits a month with a work email, or 250 once with a personal email.

Can my AI change my Context.dev account?

Yes. It can create, update, run or delete monitors and submit, cancel or delete batches. Writes run right away when enabled. A deleted monitor or batch cannot be restored.

Can a web page tell my AI what to do?

It should not. Page text is data. The ContextDev skill tells your AI to quote and cite it and never follow instructions found inside it. Review results before you act on them.

Can I take this setup to another AI agent?

Yes. Add ApexGenius to another compatible agent with the same ApexGenius account. It uses the same Context.dev connection and can load the ContextDev skill. Each agent needs its own setup.

Connect Context.dev to Grok Bot today

Start free

1,000 free credits. No card required. Disconnect any time.