SO-ARM100 Robot Control
Enables control of SO-ARM100 series robots via an MCP server for AI agents and direct manual operation.
Browse 6,627+ Model Context Protocol servers for Claude, Cursor, and VS Code. Find the perfect tools for your AI workflow.
Enables control of SO-ARM100 series robots via an MCP server for AI agents and direct manual operation.
Enables AI assistants to access Tripadvisor data for travel destination and experience discovery via standardized MCP interfaces.
Deploy intelligent multi-agent swarms and coordinate autonomous workflows in an advanced agentic development environment.
Enables human-in-the-loop workflows in tools like Cline and Cursor by providing a simple MCP server.
Connects custom tools to agentic LLMs, providing a single access point for multiple MCP-compatible environments.
Enables AI assistants to initiate and manage voice calls using Twilio and OpenAI.
Generates AI-driven diagrams and interactive prototypes in various styles based on natural language descriptions.
Aggregates multiple Model Context Protocol (MCP) tool calls into a single request, reducing overhead and token usage for AI agents.
Provides comprehensive context for AI models to assist in the development of SAP Cloud Application Programming Model (CAP) applications.
Integrates the Claude Code CLI directly into Emacs, enabling AI-powered coding sessions within your editor.
Integrates Codacy's comprehensive code analysis capabilities into various IDEs and agent-based environments.
Optimizes context for AI coding assistants by enabling them to extract targeted information from files and command outputs, rather than processing large data in its entirety.
Enables AI-assisted debugging by providing a Model Context Protocol (MCP) server for GDB interaction.
Enables AI assistants to interact with and manipulate Google Sheets and Google Drive files.
Enables AI assistants to utilize human capabilities by routing requests to humans and relaying their responses.
Bridges Jenkins with AI language models, enabling secure and contextual interactions.
Gain comprehensive visibility into Apache Iceberg-based data lakehouses, displaying detailed metadata and structural information.
Measures webpage performance metrics using Google's Lighthouse, enabling AI assistants to optimize these metrics.
Automates LinkedIn interactions and extracts data through browser automation, respecting terms of service and rate limits.
Create an interactive AI assistant with Streamlit, NVIDIA NIM/Ollama, and Model Control Protocol (MCP).
Connects Claude AI to real-time Dutch Railways (NS) travel information.
Enables Claude AI to create and modify React applications through the Model Context Protocol.
Generates a structured map of a codebase within a Git repository to aid understanding and navigation, particularly for large language models.
Provides AI coding agents with always-up-to-date, version-specific package documentation as context.
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.