"Strategies for enhancing coding efficiency with cursor agent optimization" matching MCP servers:

Provides 10 structured reasoning strategies (Chain of Thought, ReAct, Tree of Thoughts, etc.) for complex problem-solving with session persistence, branching, and tool integration capabilities.

MCP server for Obsidian vaults, optimised for Cursor agents — safe note editing, lean tool surface, direct filesystem access.

MCP server for coding-os, a cognitive operating system that gives AI agents memory, structure, and discipline. It exposes tools for project management, task tracking, knowledge graphs, and cognition traces to Claude Code and Codex.

Enables AI harnesses to maintain a persistent memory layer backed by a local SQLite file, providing MCP tools to add, search, deprecate, and synchronize facts without deleting history.

Provides a local long-term memory layer for AI coding tools like Cursor and Claude Code, enabling cross-session, cross-tool sharing of project facts, user preferences, decisions, and workflows.

Provides structured external memory for AI assistants, enabling persistent context, branch notes, tacit knowledge, and checklists to overcome AI memory loss and context confusion.

An MCP server that provides shared memory, kanban board, and agent registry for AI agents to collaborate as a team, with a live dashboard for human oversight.

Read-only bridge between Claude Code and Cursor on Windows. Exposes Cursor's local chat database via 7 MCP tools, plus a 5-min background poller. The server starts and responds to introspection in a container, but tool calls require a Windows host with Cursor installed (the container is for directory checks only).

A stateful MCP server that provides persistent memory, deterministic static analysis, and evolving conventions for AI coding assistants.

Turns a codebase into a persistent knowledge graph so AI coding agents can answer structural questions about functions, call chains, routes, and cross-service links through graph queries instead of reading files one by one.

Enables hybrid retrieval over interpretable Gemini documentation knowledge graphs through eight MCP tools, combining vector, keyword, and graph-boosted search with deprecation filtering.

Enables searching local OpenAI Codex conversation history by keywords, project, date, or role, listing sessions, and retrieving exact supporting messages through MCP tools.

Persists Claude Code sessions to Notion as team memory, enabling queryable recall of decisions, work state, and project architecture.

A persistent SQLite-backed storage server that enables Cursor IDE's AI assistant to remember information across sessions with global or project-specific scopes. It supports complete CRUD operations, tag-based organization, and keyword search to manage user preferences and context effectively.

Local-first shared memory and coordination layer for AI coding agents, with repository evidence, reservations, handoffs, code graph context, and dashboard review backed by PostgreSQL/pgvector.

Local, searchable project memory for AI coding agents. Markdown source of truth, MCP interface, safe structured updates

A self-improving knowledge agent that provides local retrieval, web research, and structured answer synthesis for Claude Code and VS Code Copilot via MCP. It enables AI tools to manage a project-specific knowledge lifecycle through automated research and indexing.

Exposes tools that let an agent search a local Markdown-based memory store, fetch full cards by id, write new knowledge cards that are indexed immediately, and inspect or rebuild the SQLite index. All retrieval runs locally over Chinese-friendly full-text search with graded exact/prefix matching, so agents without a memory system can recall prior notes while existing Markdown files stay read-only.

An MCP server that enables AI agents to compile, refine, and interlink knowledge into a persistent wiki, replacing RAG with structured, curated knowledge.

MCP server that exposes agent-memory-daemon to any MCP-compatible client — Kiro (CLI & IDE), Claude Desktop, Cursor, and others. The daemon does the thinking (consolidation + extraction); this server is a thin filesystem bridge so agents can read, append, and search memory through the Model Context Protocol.