Supermemory + Grok Bot

Connect Supermemory to Grok Bot Prepare a grounded source-backed memory briefing

Read documents with Grok Bot and Agent200. Prepare a source-backed memory briefing within the configured Supermemory account scope.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Supermemory tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Identify the selected document and ask Grok Bot to use the Agent200 connection. Inspect tool activity so browser context or another app does not replace the requested read.

Start with one identified document. Preserve returned document content, source and container tags; report missing data and keep the workflow read-only.

Provider reference: Supermemory API.

Use the provider credential described on the Supermemory parent page. Keep it in secure configuration and verify the selected tenant or account before reading.

Connector
Supermemory
Works with
Grok Bot · Agent app, through MCP
Authentication
Your Agent200 API key
Tools
4 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Supermemory enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.

Connect Supermemory to Grok Bot

  1. 1

    Step 1: Create your Agent200 API key

    Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers Supermemory and every other connector enabled for your project. Keep it out of chats and source control.

  2. 2

    Step 2: Open the custom connector form

    In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.

  3. 3

    Step 3: Fill in the server and your key

    Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header: Authorization with the value Bearer followed by your key. Leave Client ID empty, then choose Add plugin.

    Add a custom connector
    MCP: Grok Bot custom connector form
    Name:          Agent200
    Type:          Remote HTTPS
    Server URL:    https://api.agent200.com/mcp/
    HTTP headers:  Authorization: Bearer YOUR_AGENT200_API_KEY
  4. 4

    Step 4: Attach Agent200 in a chat

    In a Bot chat, type @ and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it.

Test your connection

Run one request to check everything is wired up.

Ask

Read the Supermemory document I identify and prepare a source-backed memory briefing. Name the source and use only document content, source and container tags. State access gaps; do not change records.

What should come back

  • The selected document is identified.
  • Only the returned document content, source and container tags are reported.
  • Access gaps and missing context are explicit; no source data is changed.

Check the selected document ID, account scope, read permission and pagination. A semantic match is not proof of complete recall. Name returned sources and container scope, and allow for indexing or processing lag.

Get your API key

Create a key in the Agent200 dashboard. It reaches Supermemory and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Supermemory to Grok Bot.

Agent brief
Goal: connect Supermemory to Grok Bot with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/supermemory/framework/grok-bot/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Grok Bot's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Supermemory is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Grok Bot: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Grok Bot's exact menus or commands.
4. Check it works with this request: "Read the Supermemory document I identify and prepare a source-backed memory briefing. Name the source and use only document content, source and container tags. State access gaps; do not change records."
   What should come back:
   - The selected document is identified.
   - Only the returned document content, source and container tags are reported.
   - Access gaps and missing context are explicit; no source data is changed.
5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/supermemory/framework/grok-bot.md

Supermemory tools Grok Bot can call

  • Search documents

    Read
    supermemory_search_documents

    Search indexed documents within a specified container.

  • Read a document

    Read
    supermemory_get_document

    Retrieve one identified document when available.

  • List documents

    Read
    supermemory_list_documents

    Find indexed documents in the key’s scope.

  • Search memories

    Read
    supermemory_search_memories

    Search generated memories with source references.

How it works

  1. 01

    You ask Grok Bot

    In your own words, for something in Supermemory.

  2. 02

    Grok Bot picks a tool

    It sees the Supermemory tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    It reaches Supermemory with your Agent200 API key, within the endpoints your project allows.

  4. 04

    Grok Bot answers

    It gets the result back from the MCP server and uses it in its reply or its next step.

Permissions at every level. Your project settings decide which services and endpoints the agent may use.

Troubleshooting

The source cannot be read

Check the selected document ID, account scope, read permission and pagination. A semantic match is not proof of complete recall. Name returned sources and container scope, and allow for indexing or processing lag.

FAQ

How do I verify this result?

Compare the named document and returned document content, source and container tags with the source. Treat missing information as missing, not as a fact.

Use Supermemory with another framework

200 OK

Supermemory, connected to Grok Bot.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)