Give Grok Bot a Searchable Bookmark Library

Grok Bot is xAI's persistent cloud-computer teammate, not an ordinary grok.com chat, the grok developer CLI, or an unofficial Discord bot. Its browser sessions, files, and command-line credentials are shared by all Bots on your account, so connecting a personal bookmark library has a broader trust boundary than attaching a connector to one chat.

What xAI officially supports—and what it does not document

xAI says Grok Bot supports the same MCP servers, plugins, and skills as Cursor. Current Grok Bot setup documentation, however, tells users to install connectors as plugins from Marketplace; it does not document a general “paste any MCP URL” screen or guarantee that an arbitrary Cursor ~/.cursor/mcp.json is imported into the Bot's cloud computer.

Therefore, do not use the ordinary Grok New Connector → Custom instructions here and do not assume a local Cursor configuration automatically reaches Grok Bot. Use the supported Marketplace/plugin path when Save This One is available. If it is absent, the current official Grok Bot docs do not establish a supported direct custom-server installation path; use Grok's custom connector or another MCP client instead until Grok Bot exposes one. This avoids asking a cloud agent to install an unverified bridge or handle a copied OAuth token.

Eligibility

Grok Bot is in beta. xAI currently lists access for individual SuperGrok tiers and paid individual Cursor plans, plus Cursor Teams; Enterprise availability and controls can differ and may require a rollout/waitlist. Consult the live plan page for the exact matrix. Availability on desktop/mobile does not imply that every connector can be installed from every surface.

Connect through Grok Bot Marketplace

When a trusted Save This One plugin/connector is listed:

1. Open Marketplace from the Grok Bot sidebar.
2. Search for Save This One. Verify that the listing points to the official endpoint https://mcp.savethisone.com/mcp; do not choose a look-alike publisher.
3. Choose Add.
4. Complete authentication in the browser. Sign in to Save This One directly; never give a Bot your password, one-time code, or raw OAuth token in chat.
5. In the task, type @ and attach the Save This One connector.
6. Run the read-only verification below before delegating ongoing work.

If the listing is missing, stop here. The generic Cursor JSON and grok mcp add commands found in other product documentation are not documented as Grok Bot installation methods.

Verify account and capability

Ask the Bot:

Using the attached Save This One connector, call whoami, list the available tool names, then call list_tags. Do not change anything. If those exact tools are unavailable, stop and report that instead of using the browser.

For a direct connection to the current server, the exact expected tools are:

whoami              list_bookmarks       search_bookmarks
get_bookmark         save_bookmark        archive_bookmark
delete_bookmark      list_tags            create_tag
delete_tag           tag_bookmarks        list_comments
add_comment          delete_comment

The plugin could expose a restricted subset. Do not assume write access merely because the Bot can search, and do not let the Bot silently fall back to clicking around the Save This One website when you intended auditable MCP calls.

Delegation patterns for a persistent Bot

A bounded weekly research digest

Use only search_bookmarks, list_bookmarks, and get_bookmark from Save This One. Find active bookmarks tagged market-watch from the newest 50 and draft a digest with source URLs. Do not save, tag, comment, archive, delete, browse the web, or send the digest.

The server does not expose creation-date range filtering, so the Bot should page/list and reason over returned saved dates rather than inventing a “this week” query.

Save reviewed research

I approve saving these three public URLs. Call save_bookmark once per URL with tag bot-research. Do not add comments or create other tags. Report whether each result says Saved or Already saved.

Saving is idempotent for an existing normalized URL and fetches metadata automatically.

Prepare, but do not execute, cleanup

List active bookmarks tagged bot-research, including IDs. Propose an archive list. Wait for my explicit approval of the IDs. Never call a delete tool.

Capture handoff context

Find the exact bookmark for the deployment guide. Show its ID and existing comments. Ask me to approve the exact comment text before calling add_comment.

Safety for an autonomous cloud computer

• Create a dedicated Bot for bookmark workflows and attach the connector only to tasks that need it.
• Remember that all Bots on the account share the same cloud computer, browser cookies, files, and command-line credentials. Do not assume isolation between Bots.
• Use Grok Bot's approval/Auto Review controls for sensitive actions. Keep human approval for any write, especially archives and deletes.
• Prefer archive_bookmark, which can be reversed, over delete_bookmark.
• Never authorize delete_bookmark, delete_tag, or delete_comment in a routine. Bookmark deletion also removes comments and tag links.
• add_comment is non-idempotent; verify with list_comments before retrying after an ambiguous failure.
• Do not put passwords, 2FA codes, or OAuth tokens in chat. For human-only browser steps, take over the cloud computer and complete only that step.
• Avoid unattended routines with mutation tools. A schedule can repeat a misunderstood instruction long after the original review.

Troubleshooting

Save This One is not in Marketplace. There is no verified generic custom-MCP path in the current Grok Bot docs. Use Grok's custom MCP connector or Claude/Cursor instead; recheck Marketplace after product updates.

Authentication opens in the wrong account. Disconnect/remove the plugin, take over the browser to sign out of the unintended account, reconnect, and verify with whoami.

The Bot browses the website instead of calling tools. Stop the task. Reattach the connector with @, name an exact tool, and say browser fallback is forbidden. Browser automation has different audit and confirmation properties.

Only retrieval works. Treat the plugin as read-only. Grok Bot entitlement, plugin design, or organization policy may limit writes even though the underlying server advertises them.

A search misses saved material. search_bookmarks checks active bookmark metadata only. Ask for list_bookmarks with archived: true or browse by an exact list_tags result.

The cloud computer needs a secret or 2FA. Take control for the sensitive step; do not paste it into the Bot conversation. xAI explicitly recommends handoff for passwords, passkeys, 2FA, CAPTCHAs, and similar checks.

Official references

• xAI: Grok Bot overview
• xAI: Grok Bot computer and apps
• xAI: Introducing Grok Bot
• xAI: Grok Bot 101
• Cursor: MCP configuration (background on the compatibility claim; not proof that Grok Bot imports local config)