Extensions & Ecosystem Reference
Extensions & Ecosystem Reference
Last verified: October 2026. This page covers MCP servers, IDE integrations, skills and plugin systems, memory tools, and community resources for staying current. For a practical guide to setting these up, see Module 8.
MCP Servers (Model Context Protocol)
MCP is a protocol that lets AI agents call external tools over a standardized JSON-RPC transport. The USB-C analogy holds: one protocol, many compatible servers. Thousands of servers now exist.
MCP Servers by Category
Anthropic’s original reference servers for GitHub, GitLab, Postgres, SQLite, Slack, Google Drive, and Puppeteer are archived and no longer maintained. The reference repo now holds only a few servers (everything, fetch, filesystem, git, memory, sequentialthinking, time). For most services, use the server the vendor maintains.
Productivity
- Notion: Official server from Notion. Read and write pages, query databases.
Development
- GitHub: GitHub’s official server (MIT license) for repositories, issues, and pull requests.
- Git and Filesystem: Reference servers. Filesystem gives read/write access to directories you specify.
Data
- MCP Toolbox for Databases: Google’s open-source (Apache 2.0) MCP server for querying databases.
Browser
- Playwright MCP: Microsoft’s server (Apache 2.0) for driving a browser to read pages or test UIs. It replaces the archived Puppeteer server.
Discovery Resources
- MCP Registry: The official registry of published MCP servers, linked from the reference repo.
- mcp.so: Directory of community-submitted MCP servers, searchable by category.
- Smithery: MCP server registry and marketplace. It lists over 27,000 servers and handles authentication so agents can connect to them.
- Glama: Curated list of MCP servers with quality ratings and install guides.
IDE Context Integration
Your code editor gives the AI immediate access to your files and project structure.
Skills and Plugins
AI coding tools each have their own extension system. They differ in where rules live and what they can do.
Claude Code uses skills: a directory with a SKILL.md file, stored in .claude/skills/<name>/ (project) or ~/.claude/skills/<name>/ (personal), that appears as /name in the terminal. Older .claude/commands/*.md files still work. You can also add hooks (shell scripts that run before or after agent actions) via .claude/settings.json.
Cursor keeps project rules in .cursor/rules as .mdc files that are version-controlled with the repo. They set persistent instructions about code style, conventions, and tech stack. Older projects used a single .cursorrules file at the root.
GitHub Copilot reads repository-wide instructions from .github/copilot-instructions.md, and also supports AGENTS.md files and a CLAUDE.md in the repository root.
Windsurf was renamed Devin Desktop (from Cognition) in 2026. It has its own rules files; check its docs for the current file name.
Project Instruction Files
To make an agent effective, give it explicit instructions about the current repository’s style, tech stack, and conventions.
- Usage: Cursor reads
.cursor/rules. Claude Code readsCLAUDE.md(and can also readAGENTS.md). Both act as persistent instructions loaded at the start of every session. - Discovery: cursorrules.com collects crowd-sourced rulesets for frameworks like Astro, Next.js, and Svelte.
Many developers run a terminal-native agent and an editor-integrated assistant side by side.
- Cursor: A fully integrated AI-native IDE. You act as the “driver,” with the AI acting as a context-aware pair-programmer inside your editor.
- Claude Code: An execution-first terminal agent. You act as the “architect,” telling the agent to execute large multi-file refactors autonomously in the terminal.
A common split is Cursor for day-to-day edits and Claude Code for large refactors or debugging in the terminal.
Memory and Context Tooling
Long-term memory is what turns a single-session chat into an assistant that remembers you.
- Mem0 is a memory layer for agents (Apache 2.0). It extracts preferences and facts from conversations and stores them for later sessions. MemStack is a smaller project for Claude Code: session diary, fact recall, and a set of skills.
- GraphRAG: Uses knowledge graphs instead of simple vector similarity. The practical difference: on questions that require connecting multiple related entities (e.g., “which customers had issues with product X after the Q3 price change?”), GraphRAG returns more coherent answers because the graph structure captures relationships that a flat vector index misses.
Community Hubs
These are the places where practitioners share findings, discuss new models, and post benchmarks.
- r/LocalLLaMA (Reddit): Daily discussion of local model releases, hardware requirements, and benchmark results. Good for seeing how new models actually perform before trying them yourself.
- Hugging Face (huggingface.co): Model hosting, dataset hosting, research papers, and community spaces. The canonical place to download open-weight models.
- Simon Willison’s blog (simonwillison.net): Practical coverage of AI tools, MCP servers, and prompting techniques. Updated frequently with hands-on notes.
For a hands-on guide to setting up MCP servers and IDE integrations, see Module 8.