MCP Recipe
Research a topic with Exa and Memory
Influzer starter recipe: use Exa to find high-signal sources on a topic, then store durable findings in Memory so the next chat starts from what you already learned.
MCP servers used
Compatible clients (author-reported, not verified by Influzer): Cursor, Claude Desktop, Claude Code
Prerequisites
- Exa remote MCP access (OAuth / API key as required by Exa)
- Memory MCP installed locally (
@modelcontextprotocol/server-memory) - A clear research question (audience, geography, time window)
Required permissions
Exa searches the public web. Memory writes local persistent entities — store summaries and source URLs, never API keys or private customer data.
Setup
Add Exa as a remote MCP at https://mcp.exa.ai/mcp and complete any auth Exa requires. Add Memory as a local/stdio MCP in Cursor or Claude Desktop.
{
"mcpServers": {
"exa": {
"url": "https://mcp.exa.ai/mcp"
},
"memory": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-memory"]
}
}
}
Using Exa, research: “best remote MCP servers for website scraping and browser automation in 2026”.
Return 5–8 sources with title, URL, and one-line why it matters.
Write a 10–15 sentence brief with consensus vs disagreement.
Store a Memory entity for this research thread (no secrets) including the source URLs.
Expected result
A short brief with cited sources, plus Memory entities you can reuse in a follow-up chat.
Sample output
Brief: agentic browser automation MCPs (2026)
Top sources: …
Consensus: …
Open questions: …
Memory: entity “BrowserMcpResearch” with links to 5 sources.
Troubleshooting
- Exa auth errors: reconnect
https://mcp.exa.ai/mcpand complete OAuth / key setup in the client - Memory is stdio/local — ChatGPT’s remote-only path will not run it
- If results feel generic, constrain Exa to a date window or site class (docs, GitHub, papers)