Bricks Use
Executes Databricks SQL queries and facilitates comparison of table data via a Model Context Protocol server.
Browse 6,627+ Model Context Protocol servers for Claude, Cursor, and VS Code. Find the perfect tools for your AI workflow.
Executes Databricks SQL queries and facilitates comparison of table data via a Model Context Protocol server.
Provides real-time cross-chain bridge metrics for analyzing liquidity, transaction flows, and performance across blockchain networks.
Connects Purdue students' Brightspace accounts to access academic data via web scraping, handling Duo Mobile 2FA.
Exposes the Bring! shopping list API functionalities via a local Model Context Protocol (MCP) server.
Captures scrolling screenshots of webpages using Playwright, offering intelligent section identification, multiple output formats, and Model Context Protocol (MCP) integration.
Automates browser interactions via HTTP API or MCP, enabling co-browsing with AI as you code.
Automates the programmatic generation of Bruno API testing collections, environments, and requests using Model Context Protocol.
Exposes Bruno API collections as Model Context Protocol (MCP) tools for AI agents and other MCP clients.
Provides a Model Context Protocol (MCP) server for managing feature flags within the Bucketeer platform.
Provides an AI agent communication interface and a REST API server for automating bug bounty hunting workflows.
Facilitates comprehensive security testing and bug bounty hunting through natural language interaction with large language models.
Enables secure, natural language interaction with the Bugcrowd API through a high-performance Model Context Protocol (MCP) server for various AI agent platforms.
Provides precipitation forecasts for a given latitude and longitude using Buienradar data.
Transforms The Build Podcast into a searchable AI-powered knowledge base, enabling discovery of business ideas and product strategies through natural language queries.
Connects AI assistants to Buildable projects for contextual understanding, task management, and real-time collaboration.
Queries the BuiltWith API to retrieve information about website technology stacks.
Enables querying of live Bullhorn CRM data from Large Language Models (LLMs) like Claude Desktop through CData JDBC Drivers.
Enables AI assistants to interact with Burpsuite Professional for web security testing and vulnerability scanning.
Enforces standardized development rules and context for Business Central projects.
Manages BandwagonHost (KiwiVM) VPS instances through a Go SDK, command-line interface, and an integrated MCP server, providing access to a wide range of features.
Enables AI assistants to integrate with Bybit cryptocurrency exchange APIs for automated trading, market data access, and account management.
Provides a convenient interface for interacting with the Bybit cryptocurrency exchange API.
Enables text completion with local LLama.cpp models by acting as a Model Context Protocol server.
Provides a ChatGPT-like memory system for Cursor IDE using the Model Context Protocol (MCP).
MCP (Model Context Protocol) servers are tools that connect AI assistants like Claude, Cursor, and other AI coding tools to external data sources, APIs, and services. They enable AI models to access real-time information, execute code, interact with databases, and perform actions beyond their base capabilities. Check out our curated collection of the best MCP servers for Cursor →
MCP servers act as intermediaries between AI assistants and external systems. When you ask Claude or Cursor to perform a task requiring external data, the MCP server handles the request, fetches the data, and returns it in a format the AI can understand and use.
When selecting an MCP server, consider:
For detailed setup guides, see our Complete MCP Server Setup Guide →
Everything you need to know about installing, using, and troubleshooting Model Context Protocol.
To install MCP servers in Cursor: 1) Open Cursor settings (Cmd+,), 2) Navigate to MCP Servers section, 3) Click 'Add Server', 4) Enter server configuration (name and command), 5) Restart Cursor. Check out our curated collection of the best MCP servers for Cursor with detailed setup guides.
MCP servers are protocol-level integrations that work across multiple AI assistants (Claude, Cursor, etc.), while VS Code extensions are editor-specific. MCP servers provide context to AI models, whereas extensions add IDE functionality. MCP is more portable and AI-focused.
Most MCP servers listed are open-source and free. Some enterprise connectors (like Salesforce or Jira) may require paid API access to the underlying service, but the MCP server code itself is usually free.
Yes! The Model Context Protocol is open standard. You can build servers in Python or TypeScript/Node.js to expose your own internal APIs or databases to Claude and Cursor.
An MCP server is a lightweight program that exposes specific capabilities (data access, tool execution, prompts) to AI assistants through a standardized protocol. MCP servers allow Claude and other AI models to securely interact with external systems like databases, APIs, file systems, and web services while maintaining security boundaries.
MCP servers connect to Claude Desktop or other MCP-compatible clients through a standardized JSON-RPC protocol. When you configure an MCP server in Claude Desktop, Claude can access its resources (data/content), use its tools (functions to execute), and leverage its prompts (templated interactions). The protocol ensures secure, controlled access to external capabilities.
Essential MCP servers for beginners include: Filesystem (local file access), SQLite/PostgreSQL (database queries), GitHub (repository access), Brave Search (web search), and Memory (persistent context). These cover common use cases and have excellent documentation. Start with 2-3 servers and expand based on your needs.
Most MCP servers install via npm (npx) or Python (uvx/pip). Configure them in Claude Desktop's config file (claude_desktop_config.json) by specifying the command, arguments, and any required environment variables like API keys. Our directory links to each server's documentation with specific installation instructions.
MCP servers run locally on your machine with explicit permissions you configure. They can only access resources you authorize, and Claude cannot bypass these boundaries. However, always review server code, use official/verified servers when possible, limit permissions to what's necessary, and be cautious with servers that request broad access.
Resources are data sources Claude can read (files, database results, API responses). Tools are functions Claude can execute (run queries, send messages, create files). Prompts are pre-defined templates for common interactions. Most MCP servers expose one or more of these capability types.
MCP is supported by Claude Desktop (official), Cursor IDE, Continue (VS Code extension), and various community implementations. The protocol is open, so support is expanding to more AI development tools. Check our compatibility filters to find servers tested with your preferred client.
Our MCP servers directory is updated weekly with new servers, documentation improvements, and compatibility updates. We monitor GitHub releases, community contributions, and Anthropic announcements to ensure our listings reflect the latest MCP ecosystem developments.