Get the FREE Ultimate OpenClaw Setup Guide →

servers-archived

Reference MCP servers that are no longer maintained

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add modelcontextprotocol-servers-archived

How to use

This repository is an archival collection of historical MCP server reference implementations. It documents various example servers that demonstrate MCP features and SDK capabilities, but it is no longer maintained and should not be used for production. For current usage and actively maintained servers, refer to the active MCP servers repository linked in the README. To explore, clone this archive to study the implementations and the interfaces they expose, then consult the corresponding active repository for up-to-date guidance and ongoing support. Each archived server typically represents a concrete integration (for example, AWS KV retrieval, Brave Search, Git/GitHub/GitLab, Google Drive, PostgreSQL, Redis, Sentry, Slack, SQLite, and more) and can serve as a reference point for understanding MCP concepts such as data sources, tool invocations, and response shaping. When you need a functioning, supported deployment, rely on the actively maintained servers and their documented setup procedures.

How to install

Prerequisites:

  • A system with Git installed to clone repositories.
  • Optional: Node.js, Python, or other runtimes as required by individual archived server implementations (not guaranteed to be up-to-date or secure).

Installation steps:

  1. Review the README of the specific archived server you want to study to understand its dependencies and runtime requirements.

  2. Clone the archive repository to your local machine:

    git clone https://github.com/modelcontextprotocol/servers-archived.git

  3. Navigate to the desired archived server directory (e.g., servers-archived/Example-Server) and follow its README for any local setup steps, environment variables, or service dependencies.

  4. If the archived server provides a npm or package-based entry point, you can install dependencies (where applicable) using:

    npm install node path/to/server.js

  5. For environments described by the archived examples, configure any required environment variables as documented in the individual server readmes, keeping in mind that this repository is archived and may not reflect current best practices.

Note: Because this repository is archived, there is no guarantee of compatibility, security updates, or active support. Use the actively maintained MCP servers repository for production deployments.

Additional notes

Important: This repository is archived and no longer maintained. Security guarantees are not provided for these archived servers. Treat the code as historical reference only. If you need current features, security fixes, or active support, use the actively maintained MCP servers repository linked in the README. Some common points to be aware of:

  • The list of archived servers includes a variety of integrations (e.g., AWS KB Retrieval, Brave Search, EverArt, Git/GitHub/GitLab, Google Drive, Google Maps, PostgreSQL, Puppeteer, Redis, Sentry, Slack, SQLite, and more).
  • No security updates or bug fixes are guaranteed for these implementations.
  • Environment variables and runtime requirements may differ across archived examples and may be outdated.
  • When exploring, prioritize understanding MCP concepts (data sources, tool invocations, and response formatting) rather than attempting to run these servers in production.

Related MCP Servers

Sponsor this space

Reach thousands of developers