Supermemory + Muse
Connect Supermemory to Muse
Prepare a grounded source-backed memory briefing
Read documents with Muse and Agent200. Prepare a source-backed memory briefing within the configured Supermemory account scope.
On this page
Overview
Use Muse to prepare a short source-backed memory briefing for review. Put the Agent200 key in Muse’s secure credential interface, then inspect the source before sharing the result.
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
- Muse · Agent app, through MCP
- Authentication
- Your Agent200 API key
- You need
- An 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.
- Muse, with custom MCP servers allowed. Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.
Connect Supermemory to Muse
-
1
Step 1: Create your Agent200 API key
Create a key on the API keys page and store it securely.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Create the custom connector
Connect to
https://api.agent200.com/mcp/over Streamable HTTP with an Authorization: Bearer header. Enter the key in Muse’s secure credential interface.Muse chatMCP: message that asks Muse to create the custom connector Create a Custom Connector for the Agent200 remote MCP server and connect to it: Name: Agent200 Transport: remote streamable HTTP URL: https://api.agent200.com/mcp/ Auth: API key sent in the Authorization header as "Bearer <key>" Open the secure credentials store so I can enter the API key there, not in this chat. Then list its tools to confirm the connection works. -
3
Step 3: Inspect read tools
Confirm the Supermemory operations and schemas advertised by the connection.
-
4
Step 4: Configure Supermemory access
Use the provider-issued credential through the supported Agent200 connection route. Confirm the account scope and inspect the advertised tools before reading.
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.
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 Muse.
Goal: connect Supermemory to Muse with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/supermemory/framework/muse/ 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 Muse'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 Muse: 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 Muse'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/muse.md
Supermemory tools Muse can call
-
Search documents
Readsupermemory_search_documentsSearch indexed documents within a specified container.
-
Read a document
Readsupermemory_get_documentRetrieve one identified document when available.
-
List documents
Readsupermemory_list_documentsFind indexed documents in the key’s scope.
-
Search memories
Readsupermemory_search_memoriesSearch generated memories with source references.
No tool matches that search.
How it works
-
01
You ask Muse
In your own words, for something in Supermemory.
-
02
Muse picks a tool
It sees the Supermemory tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
It reaches Supermemory with your Agent200 API key, within the endpoints your project allows.
-
04
Muse 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.
