Oneda MCP server
{
"mcpServers": {
"freeelatech-oneda": {
"type": "http",
"url": "https://oneda.freeelatech.com/mcp"
}
}
}{
"mcpServers": {
"freeelatech-oneda": {
"type": "http",
"url": "https://oneda.freeelatech.com/mcp"
}
}
}{
"mcpServers": {
"freeelatech-oneda": {
"type": "http",
"url": "https://oneda.freeelatech.com/mcp"
}
}
}{
"servers": {
"freeelatech-oneda": {
"type": "http",
"url": "https://oneda.freeelatech.com/mcp"
}
}
}{
"mcpServers": {
"freeelatech-oneda": {
"type": "http",
"url": "https://oneda.freeelatech.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.1.3
What it does
Nova Oneda is an MCP server that stores institutional memory—decisions, specifications, and learnings—for Claude Code across sessions. It automatically retrieves relevant past context before Claude starts substantial work and records new decisions as you go, preventing Claude from repeating past choices or forgetting institutional knowledge.
- Ask Claude Code to build a feature weeks later and have it remember architectural decisions or rejected approaches from earlier work without you restating them.
- Record why your team chose a particular technology (e.g., Postgres for billing, no Redux) so Claude retrieves that rationale the next time it considers alternatives.
- Maintain knowledge continuity across session resets, team turnover, and context limits by storing decisions in a persistent, searchable memory store.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.