"Building a solid memory base for AI development" matching MCP servers:

A Model Context Protocol server that enables seamless integration between Claude AI and development tools like VSCode, Augment, Vercel, Airtable, and Square.

A CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.

MCP server that launches Mesen/MesenCE headlessly and exposes the emulator's debugger-face Lua API over MCP JSON-RPC, enabling AI agents to load ROMs, step frames, inspect memory/registers, manage breakpoints/watches, trace execution, and export Code/Data Logger maps for SNES, NES, PC Engine, and Game Boy Advance.

Turn editor chat history (Cursor/Claude Code/Windsurf/Copilot/Codex CLI) into typed Markdown memories + AGENTS.md + Cursor Rules via MCP. Local-first, git-trackable.

MCP server for Next2D application development that generates code following MVVM + Clean Architecture + Atomic Design patterns, validates architecture, and provides API references.

A local-first MCP server that manages developer memory for coding agents, enabling shared project context, permissions, and audit trails across different agents.

Enables AI-first DevOps management of multi-tenant Solid SaaS platforms through natural language conversation. Monitor thousands of tenant instances, track AI agent performance, handle errors, manage billing, and provision new tenants directly through Claude Desktop.

Local memory for coding agents that can refuse, not only recall. A rule carrying a machine-checkable proof blocks the matching command before it runs, while prose-only rules can warn but never block.

An MCP server for managing work logs, research results, and task checkpoints to enable seamless collaboration and state recovery between AI agents. It provides a persistent memory layer for tracking project history and resuming workflows across different sessions or tools.

Provides comprehensive development tools for FastMCP projects including documentation access, NPM package version management, and TypeScript type definitions retrieval. Enables developers to fetch FastMCP documentation, analyze NPM packages, and access MCP architecture information through natural language.

Provides comprehensive code analysis (quality, complexity, linting, dependencies, security) and web scraping capabilities (static/dynamic content, API discovery) for development workflows.

A TypeScript-based template for rapidly developing MCP servers with modular tool architecture, built-in validation using Zod schemas, and comprehensive error handling.

Enables AI agents to manage n8n workflow automation instances through tools for workflow CRUD operations, execution monitoring, and webhook triggering. It facilitates programmatic interaction with n8n instances via the n8n API with AI-optimized descriptions and error handling.

A Model Context Protocol server that provides LLMs with read and write access to Feishu Base (飞书多维表格) databases, enabling them to inspect schemas and manipulate records through natural language.

An MCP server providing deterministic base conversions (binary, hex, octal, decimal, base64) for AI agents, eliminating hallucination risks in low-level data processing.

Auto-captured, auto-recalled, path-scoped memory for AI coding agents and teams.

MCP server for managing project memory in AGENTS.md. Allows agents to record and remove durable facts using save/forget tools.

Hand a project over — to your next session, to Cursor/Codex/Gemini, to your successor — with the reasons attached. Local-first memory MCP for coding agents: decisions re-injected before the agent acts, drift detection across every project you run. One SQLite file, nothing leaves your machine.

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

Enables building MCP servers in TypeScript where tool schemas, descriptions, and validation are automatically generated from class methods, their TypeScript types, and JSDoc comments at compile time.