v0 by Vercel
Connect v0 to your memories.sh account via MCP.
v0 is Vercel's AI-powered tool for generating React components and UI. Connect v0 to memories.sh to access your rules and context.
Setup
1. Get Your API Key
- Sign up or log in at memories.sh/app
- In the dashboard, find the MCP API Key section
- Click Generate API Key
- Copy the key (you won't see it again)
2. Configure v0
In v0's MCP settings, add:
{
"mcpServers": {
"memories": {
"url": "https://memories.sh/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Replace YOUR_API_KEY with the key you generated.
3. Verify Connection
Test the connection:
curl -H "Authorization: Bearer YOUR_API_KEY" https://memories.sh/api/mcp
# Should return: {"status":"ok","name":"memories.sh MCP Server","version":"0.4.0"}Using with v0
Once connected, v0 can access your memories:
Get context for a task:
Search my memories for React component patternsSave new learnings:
Save this as a rule: "Use Tailwind's cn() helper for conditional classes"Recall decisions:
What decisions have I made about design system components?Available Tools
The hosted MCP server provides these tools:
| Tool | Description |
|---|---|
get_context | Get rules and relevant memories |
add_memory | Store a new memory (rule, decision, fact, note) |
search_memories | Search by content |
list_memories | List recent memories |
Syncing with CLI
Memories added via v0 sync to your cloud database. To access them locally:
# Login (if not already)
memories login
# Enable sync
memories sync enable
# Pull latest memories
memories sync pullNow your memories are available both in v0 and your local CLI/IDE tools.
Managing Your API Key
In the dashboard:
- Regenerate — Create a new key (invalidates the old one)
- Revoke — Delete the key entirely
API keys are tied to your account. Anyone with your key can read and write to your memories.
Alternative: Local Server (Development)
For local development without cloud sync, you can run a local MCP server:
memories serve --sse --port 3030Then configure v0 to connect to http://localhost:3030/mcp (no auth required for localhost).
Troubleshooting
401 Unauthorized
- Check your API key is correct
- Ensure the
Authorizationheader includesBearerprefix - Regenerate your key in the dashboard
No memories found
- Verify you have memories:
memories list - Check sync is enabled:
memories sync status - Push local memories to cloud:
memories sync push
v0 not using my rules
Make sure your rules are synced to the cloud:
memories sync pushThen verify in the dashboard that your rules appear.