Model Context Protocol Server Catalog

This collection comprises canonical examples illustrating the implementation of the Model Context Protocol (MCP). It also includes pointers to community-contributed servers and supplementary materials.

The servers herein emphasize the versatility and inherent extensibility of MCP, demonstrating secure, governed connectivity between Large Language Models (LLMs) and various data endpoints or operational tools. Every server within this repository leverages either the Typescript MCP SDK or the Python MCP SDK.

Note: The directory listings below are maintained in lexicographical sequence to minimize conflicts during updates.

🌟 Exemplary Servers

These implementations are designed to thoroughly showcase MCP functionalities and the capabilities of the Typescript and Python SDKs.

AWS KB Retrieval - Facilitates retrieval from AWS Knowledge Bases utilizing the Bedrock Agent Runtime.
Brave Search - Executes web and localized searches leveraging Brave's dedicated Search API.
EverArt - Provides AI-driven image synthesis using a variety of underlying models.
Everything - A foundational/testing server incorporating standard prompts, resources, and generic tooling.
Fetch - Acquires and transforms web content for optimized LLM consumption.
Filesystem - Manages secure interactions with the local file system, subject to customizable permission policies.
Git - Offers utilities for inspecting, querying, and modifying Git repository contents.
GitHub - Enables repository administration, file manipulation, and direct integration with the GitHub API.
GitLab - Provides access to the GitLab API for project oversight and management tasks.
Google Drive - Grants file access and search functionality across a user's Google Drive.
Google Maps - Supports location lookups, route calculation, and detailed place information retrieval.
Memory - Implements a persistent knowledge retention system built upon a graph structure.
PostgreSQL - Offers read-only connectivity to PostgreSQL databases, including schema introspection features.
Puppeteer - Controls headless or headful web browsers for automation and data extraction.
Sentry - Fetches and analyzes diagnostic data and issues reported via Sentry.io.
Sequential Thinking - Supports reflective and iterative problem-solving by structuring agent actions into explicit thought chains.
Slack - Manages communication channels and facilitates message posting within Slack workspaces.
Sqlite - Handles direct database querying and supports business intelligence operations on SQLite files.
Time - Provides accurate time zone conversions and temporal data querying.

🤝 Externally Maintained Servers

🎖️ Vendor-Supported Integrations

Official integrations are maintained by organizations offering production-grade MCP server solutions for their respective ecosystems.

Axiom - Natural language querying and analysis of Axiom logs, traces, and event data.
Browserbase - Cloud-based automation for browser tasks: navigation, data scraping, form submission, etc.
Cloudflare - Deployment, configuration, and interrogation of Cloudflare platform resources (Workers, KV, R2, D1).
E2B - Execution environment for running arbitrary code within secure, isolated sandboxes provided by E2B.
Exa - A search engine specifically engineered for AI agent consumption by Exa.
Fireproof - An immutable, ledger-based database solution featuring real-time synchronization capabilities.
JetBrains – Facilitates code interaction and development workflows within JetBrains IDEs.
Kagi Search - Accessing web search results via Kagi's premium search API.
Meilisearch - Interface for querying and interacting with Meilisearch's full-text and semantic search engine.
Metoro - Query and operational interface for Kubernetes clusters monitored by Metoro.
MotherDuck - Data querying and analytics leveraging the MotherDuck cloud data platform or local DuckDB instances.
Needle - Provides production-ready Retrieval-Augmented Generation (RAG) capabilities for searching proprietary documents.
Neo4j - Server for the Neo4j graph database, supporting schema inspection and Cypher read/write operations, plus a separate graph-backed memory store.
Neon - Interface for managing and querying data within the Neon serverless Postgres environment.
Qdrant - Implements a semantic knowledge layer utilizing the Qdrant vector search engine.
Raygun - Accessing operational and crash monitoring data from a Raygun account.
Search1API - Unified API access for web searching, crawling, and sitemap processing.
Tinybird - Interface for interacting with the Tinybird serverless ClickHouse platform.

🌎 Community Contributions

A rapidly expanding collection of community-developed servers demonstrating MCP's broad utility across various application domains.

Caution: Community servers are unverified. Deployment and usage are strictly at your own liability. They do not imply affiliation with or endorsement by Anthropic.

AWS S3 - A demonstrative server for fetching diverse objects (e.g., PDFs) from AWS S3 buckets.
AWS - Executes operations against user-defined AWS infrastructure via an LLM interface.
Airtable - Read/write capabilities for Airtable databases, including data schema exposure.
Airtable - An alternative Airtable Model Context Protocol Server implementation.
AlphaVantage - MCP server interface for accessing financial market data via the AlphaVantage API.
Anki - Utility for interacting with Anki flashcard decks and individual cards.
Any Chat Completions - Connects to any API compliant with the OpenAI Chat Completions specification (e.g., Perplexity, Groq, xAI).
Atlassian - Interface for Atlassian Cloud products (Jira and Confluence), supporting issue querying and space/page retrieval.
BigQuery (by LucasHild) - Enables schema introspection and SQL execution against Google BigQuery datasets.
BigQuery (by ergut) - Server implementation granting direct query access to Google BigQuery.
ChatMCP – A cross-platform, open-source GUI desktop application for seamless management of MCP services across various selectable LLMs, developed by AIQL.
ChatSum - LLM-assisted querying and summarization of message transcripts, by mcpso.
Chroma - Vector database server offering semantic search capabilities with advanced metadata filtering, built atop Chroma.
Cloudinary - Server to upload digital assets to Cloudinary and retrieve their resultant URLs and metadata.
cognee-mcp - A GraphRAG memory server featuring configurable ingestion pipelines, data transformation, and retrieval mechanisms.
coin_api_mcp - Access point for cryptocurrency market data sourced from coinmarketcap.
Contentful-mcp - Allows remote management (read, modify, publish) of content entries within Contentful spaces.
Data Exploration - Autonomous data analysis server for datasets stored in CSV format, aiming to yield immediate high-level insights. WARNING: Executes arbitrary Python logic on the host machine.
Dataset Viewer - Tool for browsing and analyzing public Hugging Face datasets, including search, statistical summaries, and data export.
DevRev - Integration server for querying the DevRev Knowledge Graph, supporting object imports from various sources listed here.
Dify - A straightforward MCP server implementation tailored for Dify workflow execution.
Docker - Provides Docker integration for managing container images, volumes, and network configurations.
Drupal - Server interfacing with Drupal via the STDIO transport protocol.
Elasticsearch - MCP server module providing generalized interaction with Elasticsearch clusters.
Fetch - A utility server capable of fetching and normalizing content from URLs into HTML, JSON, Markdown, or raw text.
FireCrawl - Advanced web scraping service supporting JavaScript rendering, document conversion (PDFs), and intelligent request throttling.
FlightRadar24 - A Claude Desktop-compatible server for real-time flight tracking using Flightradar24 data.
Glean - Server leveraging the Glean API for enterprise search and Q&A functionalities.
Google Calendar - Synchronization layer for Google Calendar, enabling schedule checks, time slot discovery, and event lifecycle management.
Google Tasks - Model Context Protocol Server for managing tasks within Google Tasks.
Home Assistant - Control and state monitoring for entities (lights, sensors, switches) within a Home Assistant installation.
HuggingFace Spaces - Server facilitating the utilization of HuggingFace Spaces for running various models (Image, Audio, Text). Includes Claude Desktop compatibility.
Inoyu - Interface for interacting with an Apache Unomi Customer Data Platform (CDP) to fetch and update user profiles.
Keycloak MCP - Enables natural language management of Keycloak realms and users (creation, deletion, listing).
Kubernetes - Connects to Kubernetes clusters to manage core resources like pods, deployments, and services.
Linear - Allows LLM operations on Linear's API for project management tasks (issue search, creation, updates).
LlamaCloud (by marcusschiesser) - Integration point for querying data indexed within a managed index hosted on LlamaCloud.
MCP Installer - A specialized server designed to facilitate the automated installation of other MCP servers.
mcp-k8s-go - A Golang-based Kubernetes server implementation for browsing pod logs, inspecting events, and managing namespaces within MCP context.
MSSQL - Integration module for Microsoft SQL Server, featuring access governance and schema discovery.
Markdownify - Converts a wide array of document types (PPTX, HTML, PDF, YouTube transcripts) into standardized Markdown format.
Minima - A local file-based RAG server solution.
MongoDB - A Model Context Protocol Server dedicated to MongoDB interaction.
MySQL (by benborla) - MySQL database connectivity implemented in NodeJS, supporting access control and schema inspection.
MySQL (by DesignComputer) - MySQL database connectivity implemented in Python, featuring configurable access rules and schema visibility.
NS Travel Information - Accesses real-time Dutch Railways (NS) transit data, including service disruptions, via the official NS API.
Notion (by suekou) - Interface for interacting with the Notion API for page manipulation.
Notion (by v-3) - Notion MCP integration focused on searching, reading, updating, and creating pages via chat interface.
oatpp-mcp - Framework enabling the construction of MCP servers using the C++ Oat++ library.
Obsidian Markdown Notes - Utility for reading and searching content stored in an Obsidian vault or any designated Markdown directory.
OpenAPI - Server for dynamic interaction with services defined by the OpenAPI specification.
OpenCTI - Retrieves cyber threat intelligence data (reports, indicators, actors) from an OpenCTI platform.
OpenRPC - Tooling to explore and invoke JSON-RPC services described via OpenRPC.
Pandoc - Conversion server using Pandoc, primarily supporting Markdown and HTML output formats, with other document types forthcoming.
Pinecone - Server for indexed data management (upload, query) in Pinecone, enabling simplified RAG workflows via its Inference API.
Placid.app - Generates custom visual assets (images/videos) from templates hosted on Placid.app.
Playwright - MCP Server instance designed to execute browser automation and scraping tasks using the Playwright library.
Postman - Server that executes Postman Collections locally via Newman, reporting the success or failure of integrated test suites.
RAG Web Browser - An MCP server utilizing Apify's RAG Web Browser Actor to perform web searches, URL scraping, and return results formatted as Markdown.
Rememberizer AI - Specialized MCP server dedicated to knowledge retrieval from the Rememberizer data repository.
Salesforce MCP - Facilitates interaction with Salesforce data models and metadata structures.
Scholarly - A server dedicated to searching academic literature and scholarly publications.
Snowflake - Provides LLMs with controlled access for data operations within Snowflake data warehouses.
Spotify - Enables LLM control over Spotify playback and library management features.
TMDB - Integrates with The Movie Database (TMDB) API to furnish film details, search results, and content suggestions.
Tavily search - MCP server wrapping Tavily's search/news API, allowing for explicit domain inclusion or exclusion lists.
Todoist - Interface for task management operations within the Todoist ecosystem.
Vega-Lite - Generates static visualizations from provided dataset structures using the VegaLite specification and an integrated renderer.
Windows CLI - Secure server for executing commands on Windows environments, granting controlled access to PowerShell, CMD, and Git Bash shells.
X (Twitter) (by EnesCinr) - Interface for posting updates and searching the X (Twitter) platform via its API.
X (Twitter) (by vidhupv) - Allows direct creation and publishing of content to X/Twitter from the chat interface.
XMind - Utility for reading and searching through XMind files located within a specified directory structure.

📚 Auxiliary Frameworks

These higher-level toolkits simplify the process of developing custom MCP servers.

EasyMCP (TypeScript)
FastMCP (TypeScript)

📚 Informational Resources

Supplemental materials pertaining to the Model Context Protocol.

AiMCP - A directory of MCP clients and servers for tool discovery, curated by Hekmon.
Awesome Crypto MCP Servers by badkk - A specialized list focused on cryptocurrency servers, maintained by Luke Fan.
Awesome MCP Servers by appcypher - A general collection of MCP servers by Stephen Akinyemi.
Awesome MCP Servers by punkpeye (website) - A comprehensive listing by Frank Fiegel.
Awesome MCP Servers by wong2 (website) - A comprehensive listing by wong2.
Discord Server – The official community Discord server for MCP discussions, hosted by Frank Fiegel.
MCP Badges – Tools to quickly affix standardized visual badges to MCP project repositories, provided by Ironben.
MCP X Community – A dedicated X (formerly Twitter) community for MCP engagement by Xiaoyi.
mcp-cli - A command-line interface utility for inspecting the Model Context Protocol traffic, developed by wong2.
mcp-get - A command-line utility suite for simplified installation and lifecycle management of MCP servers by Michael Latman.
mcp-manager - A lightweight Web UI for installing and overseeing MCP servers utilized by Claude Desktop, built by Zue.
MCPHub – An Open Source desktop application (macOS & Windows) for discovering, installing, and managing MCP servers, created by Jeamee.
mcp.run - A centralized, hosted registry and control plane for deploying secure and portable MCP server instances.
Open-Sourced MCP Servers Directory - A curated index of community-contributed MCP servers by mcpso.
PulseMCP (API) - Community news aggregator providing weekly updates on servers, clients, articles, and developments, managed by Tadas Antanavicius, Mike Coughlin, and Ravina Patel.
r/mcp – The official Reddit forum for MCP discussions, moderated by Frank Fiegel.
Smithery - A registry service designed to help agents locate appropriate MCP tools, maintained by Henry Mao.

🚀 Deployment Instructions

Utilizing Servers within This Repository

Servers implemented in Typescript can often be launched directly via npx.

For instance, to activate the Memory server: sh npx -y @modelcontextprotocol/server-memory

Python-based servers are best initiated using uvx or standard package management via pip. uvx is the preferred method for streamlined setup.

For example, initiating the Git server: sh

Using uvx

uvx mcp-server-git

Using pip

pip install mcp-server-git python -m mcp_server_git

Instructions for installing uv / uvx are located here, and for pip here.

Integrating with an MCP Client

Running a server in isolation is functionally limited; it must be configured within an MCP client application. The following demonstrates the necessary setup for Claude Desktop to recognize the server initiated above:

{ "mcpServers": { "memory": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-memory"] } } }

Further configuration examples illustrating client integration (e.g., Claude Desktop) include:

{ "mcpServers": { "filesystem": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/allowed/files"] }, "git": { "command": "uvx", "args": ["mcp-server-git", "--repository", "path/to/git/repo"] }, "github": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"], "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "" } }, "postgres": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-postgres", "postgresql://localhost/mydb"] } } }

🛠️ Developing Custom Servers

If you intend to engineer a novel MCP server, consult the official documentation at modelcontextprotocol.io for thorough guides, established architectural patterns, and the necessary technical specifications for implementation.

🤝 Submitting Contributions

Please review the guidelines detailed in [CONTRIBUTING.md] before submitting any proposed changes to this repository.

🔒 Security Posture

Procedures for disclosing potential security vulnerabilities are documented in [SECURITY.md].

📜 Licensing

This software is distributed under the terms of the MIT License; refer to the [LICENSE] file for complete details.

💬 Community Channels

GitHub Discussions

⭐ Support & Encouragement

If you find the utility of MCP servers beneficial, we encourage you to star the main repository and contribute by submitting new server implementations or enhancements.

This project is managed by Anthropic but is fundamentally a collaborative effort with the wider community. The Model Context Protocol is open source, and we actively welcome contributions spanning new servers and protocol enhancements!

WIKIPEDIA: XMLHttpRequest (XHR) is an API defined as a JavaScript object that provides methods for sending HTTP requests from a web client to a server. These methods permit a client-side application to dispatch requests subsequent to page loading and receive data back asynchronously. XMLHttpRequest is a core constituent of the Ajax programming paradigm. Prior to Ajax, server interaction was predominantly achieved via standard hyperlink clicks or form submissions, actions that typically resulted in a full page refresh.

== Historical Context == The underlying concept for XMLHttpRequest was first formulated in 2000 by developers associated with Microsoft Outlook. This concept was subsequently integrated into the Internet Explorer 5 browser release (1999). However, the initial syntax did not utilize the standardized XMLHttpRequest object name. Instead, developers relied on instantiating COM objects via ActiveXObject("Msxml2.XMLHTTP") or ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), consistent support for the XMLHttpRequest object identifier is present across all major browser engines, including Mozilla’s Gecko (2002), Safari 1.2 (2004), and Opera 8.0 (2005).

=== Standardization Efforts === The World Wide Web Consortium (W3C) published the initial Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C advanced this to a Level 2 Working Draft, introducing features like progress monitoring, support for cross-site requests, and binary stream handling. By late 2011, the Level 2 features were integrated back into the primary specification. Development responsibilities were subsequently transferred to WHATWG near the end of 2012, where it is maintained as a living standard using Web IDL definitions.

== Operational Use == Executing a request via XMLHttpRequest typically involves a sequence of distinct programming actions.

Instantiate the XMLHttpRequest object via its constructor:
Invoke the "open" method to define the request method (GET, POST, etc.), specify the target resource URI, and set the operation mode to synchronous or asynchronous:
For asynchronous operations, assign a callback function (listener) to handle state transition events:
Initiate the data transmission by calling the "send" method:
Process events in the registered listener. Upon successful data receipt, the payload is usually accessible via the "responseText" property. When the process completes, the object transitions to state 4, signifying completion ("done"). Beyond these core steps, XMLHttpRequest offers controls for customizing request behavior. Request headers can be added to convey specific server instructions, and payload data can be passed directly into the "send" call for uploads. Responses can be automatically parsed from JSON into native JavaScript structures or processed incrementally as data chunks arrive. Furthermore, requests can be terminated prematurely or configured with a timeout limit.

== Cross-Origin Transactions == In the nascent stages of the World Wide Web, it was recognized that mechanisms existed to bypass security restrictions that prevent a script loaded from one domain from initiating requests to another domain, a topic addressed in later iterations of the standard.

mcp-server-implementations

Author

w-jeon

Quick Info

Actions

Tags