Discover Awesome MCP Servers

CSMAR MCP Server

Enables direct access to CSMAR financial databases through Claude Code. Supports 240+ databases including financial statements, stock trading data, and company information with intelligent login management and 11 MCP tools.

Outline MCP Server

An MCP server that enables reading, writing, and searching documents in Outline via its API. It supports document management, full-text search, and collection organization using Markdown formatting.

reddit-mcp

A read-only Model Context Protocol server that enables browsing subreddits, searching within subreddits, retrieving comment trees, and looking up user activity on Reddit via natural language.

mcp-server-demo

✨ Demonstração do Servidor MCP

TanStack MCP Server

Wraps the TanStack CLI to provide programmatic access to documentation, library listings, and project scaffolding for the TanStack ecosystem. It enables AI assistants to search documentation and create new TanStack applications through the Model Context Protocol.

MCP WPPConnect Server

Enables WhatsApp automation through MCP protocol, allowing users to manage sessions, send messages, handle groups/communities, and access contacts through natural language interactions with AI agents.

Whoop MCP Server

Integrates WHOOP biometric data into Claude and other MCP-compatible applications, providing access to sleep analysis, recovery metrics, strain tracking, and biological age data through natural language queries.

SharePoint MCP: The .NET MCP Server with Graph API & Semantic Kernel

Okay, let's clarify what you mean by "MCP server." It's likely you're referring to creating a *Microsoft Cloud Proxy* (MCP) server or a similar solution to securely access SharePoint Online. There isn't a single, pre-built "MCP server" product from Microsoft specifically for SharePoint Online access in the way you might be thinking. Instead, you'll need to configure a solution that acts as a proxy and potentially adds security layers. Here's a breakdown of how you can achieve secure access to SharePoint Online, along with explanations and code examples where applicable. I'll cover several approaches, from simpler to more complex, and explain the trade-offs: **Understanding the Problem** Directly exposing SharePoint Online to the internet without proper security measures is risky. You want to: * **Control Access:** Restrict who can access SharePoint Online. * **Secure Authentication:** Use strong authentication methods (e.g., Multi-Factor Authentication - MFA). * **Protect Against Threats:** Mitigate risks like data exfiltration, unauthorized access, and malware. * **Audit and Monitor:** Track access and identify potential security incidents. **Solutions** Here are several approaches, ranging from simpler to more complex, to create a secure access point for SharePoint Online: **1. Azure Application Proxy (Simplest, Recommended for Many Scenarios)** * **What it is:** Azure Application Proxy is a feature of Azure Active Directory (Azure AD) that allows you to publish on-premises web applications (or, in this case, act as a reverse proxy for SharePoint Online) to users outside your network. It provides secure remote access without requiring a VPN. * **How it works:** 1. **Azure AD Authentication:** Users authenticate against Azure AD. 2. **Application Proxy Connector:** A lightweight agent installed on an on-premises server (or an Azure VM) establishes an outbound connection to Azure. *Important: This connector does NOT require inbound ports to be opened on your firewall.* 3. **Reverse Proxy:** The Application Proxy service acts as a reverse proxy, forwarding requests from authenticated users to SharePoint Online. * **Why it's good:** * **Easy to set up:** Relatively straightforward configuration in the Azure portal. * **Secure:** Leverages Azure AD's security features, including MFA. * **No VPN required:** Users can access SharePoint Online from anywhere with an internet connection. * **Cost-effective:** Part of Azure AD Premium P1 or P2. * **How to set it up (High-Level):** 1. **Azure AD Premium:** Ensure you have Azure AD Premium P1 or P2. 2. **Install Application Proxy Connector:** Download and install the Application Proxy Connector on a Windows Server (or Azure VM) within your network. Make sure the server has outbound internet access. 3. **Configure Application Proxy:** * In the Azure portal, go to Azure Active Directory > Enterprise applications > Application Proxy. * Click "New application." * Choose "On-premises application." * **Name:** Give your application a descriptive name (e.g., "SharePoint Online Proxy"). * **Internal URL:** `https://yourtenant.sharepoint.com` (replace `yourtenant` with your actual SharePoint Online tenant name). * **External URL:** Choose a URL for users to access the application (e.g., `https://sharepoint.yourdomain.com`). You'll need to configure a DNS record for this URL. * **Pre Authentication:** Set to "Azure Active Directory." * **Connector Group:** Select the connector group you created when installing the Application Proxy Connector. * Click "Create." 4. **Assign Users:** Assign users or groups to the application in Azure AD. 5. **Configure Conditional Access (Recommended):** Implement Conditional Access policies to enforce MFA, device compliance, and other security requirements. * **Example Conditional Access Policy (MFA Requirement):** * **Conditions:** * **Users and groups:** Select the users or groups you want to protect. * **Cloud apps or actions:** Select the Application Proxy application you created. * **Access controls:** * **Grant:** Require multi-factor authentication. **2. Reverse Proxy with a Web Application Firewall (WAF) (More Control, More Complex)** * **What it is:** This involves setting up a dedicated reverse proxy server (e.g., using Nginx, Apache, or Azure Application Gateway) in front of SharePoint Online, combined with a Web Application Firewall (WAF) to protect against web attacks. * **How it works:** 1. **User Request:** A user sends a request to the reverse proxy. 2. **Authentication/Authorization:** The reverse proxy can authenticate the user (e.g., using Azure AD authentication flows) and authorize access based on roles or groups. 3. **WAF Inspection:** The WAF inspects the request for malicious content or patterns. 4. **Forward to SharePoint Online:** If the request is deemed safe, the reverse proxy forwards it to SharePoint Online. 5. **SharePoint Online Response:** SharePoint Online processes the request and sends the response back through the reverse proxy to the user. * **Why it's good:** * **Granular Control:** You have more control over authentication, authorization, and security policies. * **Advanced Security:** WAF provides protection against a wide range of web attacks (e.g., SQL injection, cross-site scripting). * **Customization:** You can customize the reverse proxy and WAF configuration to meet your specific requirements. * **How to set it up (High-Level - Example using Azure Application Gateway):** 1. **Create an Azure Application Gateway:** In the Azure portal, create an Application Gateway. 2. **Configure Backend Pool:** Add `yourtenant.sharepoint.com` (replace `yourtenant`) to the backend pool. Use HTTPS on port 443. 3. **Configure HTTP Settings:** Create an HTTP setting with HTTPS protocol and port 443. Set "Override host name" to "Pick host name from backend address." 4. **Configure Listener:** Create a listener with a public IP address or a custom domain name. 5. **Configure Routing Rule:** Create a routing rule that forwards requests from the listener to the backend pool using the HTTP setting. 6. **Enable WAF (Optional but Highly Recommended):** Enable the Web Application Firewall (WAF) on the Application Gateway. Configure the WAF rules to protect against common web attacks. 7. **Authentication (Example using Azure AD):** * Register an application in Azure AD. * Configure the Application Gateway to use Azure AD for authentication. This typically involves using OpenID Connect (OIDC) or OAuth 2.0 flows. This is a more complex configuration. * **Example Nginx Configuration (Basic Reverse Proxy - No WAF):** ```nginx server { listen 443 ssl; server_name sharepoint.yourdomain.com; # Replace with your domain ssl_certificate /path/to/your/certificate.pem; # Replace with your certificate path ssl_certificate_key /path/to/your/private.key; # Replace with your key path location / { proxy_pass https://yourtenant.sharepoint.com; # Replace with your tenant proxy_set_header Host yourtenant.sharepoint.com; # Replace with your tenant proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } ``` **Important Considerations for Nginx/Apache:** * **SSL/TLS:** Always use HTTPS and configure SSL/TLS certificates correctly. * **Security Hardening:** Harden your Nginx/Apache server to prevent vulnerabilities. * **Authentication:** Implementing authentication with Nginx/Apache requires more complex configuration, often involving modules like `mod_auth_openidc` (for Apache) or similar solutions for Nginx to integrate with Azure AD or other identity providers. **3. Custom Proxy Application (Most Control, Most Complex)** * **What it is:** You develop your own proxy application using a programming language like C#, Python, or Node.js. This gives you the most control over the proxy logic, authentication, and security. * **How it works:** 1. **User Request:** A user sends a request to your custom proxy application. 2. **Authentication/Authorization:** Your application authenticates the user (e.g., using Azure AD authentication libraries) and authorizes access. 3. **Request Transformation:** Your application can modify the request before forwarding it to SharePoint Online (e.g., adding headers, transforming data). 4. **Forward to SharePoint Online:** Your application forwards the request to SharePoint Online. 5. **SharePoint Online Response:** SharePoint Online processes the request and sends the response back to your application. 6. **Response Transformation:** Your application can modify the response before sending it to the user. * **Why it's good:** * **Maximum Control:** You have complete control over the proxy logic and security features. * **Customization:** You can implement highly customized authentication, authorization, and request/response transformation logic. * **Integration:** You can integrate the proxy with other systems and services. * **How to set it up (High-Level - Example using C# and Azure AD):** 1. **Create an Azure AD Application Registration:** Register an application in Azure AD. 2. **Develop the Proxy Application:** * Use a framework like ASP.NET Core or a similar framework in your chosen language. * Implement authentication using the Microsoft Authentication Library (MSAL) to authenticate users against Azure AD. * Implement authorization logic to control access to SharePoint Online resources. * Use the `HttpClient` class to forward requests to SharePoint Online. * Handle responses from SharePoint Online and forward them to the user. 3. **Deploy the Application:** Deploy the application to a server or cloud platform (e.g., Azure App Service). * **Example C# Code (Simplified - Authentication and Proxy):** ```csharp using Microsoft.AspNetCore.Authentication.OpenIdConnect; using Microsoft.AspNetCore.Authorization; using Microsoft.AspNetCore.Mvc; using Microsoft.Identity.Web; using Microsoft.Identity.Web.UI; using System.Net.Http; using System.Net.Http.Headers; using System.Threading.Tasks; namespace SharePointProxy.Controllers { [Authorize] public class SharePointController : Controller { private readonly IHttpClientFactory _httpClientFactory; private readonly ITokenAcquisition _tokenAcquisition; public SharePointController(IHttpClientFactory httpClientFactory, ITokenAcquisition tokenAcquisition) { _httpClientFactory = httpClientFactory; _tokenAcquisition = tokenAcquisition; } [HttpGet("/sharepoint")] public async Task<IActionResult> GetSharePointData() { string[] scopes = new string[] { "https://yourtenant.sharepoint.com/.default" }; // Replace with your SharePoint Online URL string accessToken = await _tokenAcquisition.GetAccessTokenForUserAsync(scopes); var client = _httpClientFactory.CreateClient(); client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", accessToken); string sharePointUrl = "https://yourtenant.sharepoint.com/_api/web/title"; // Replace with the SharePoint API endpoint you want to access var response = await client.GetAsync(sharePointUrl); if (response.IsSuccessStatusCode) { var content = await response.Content.ReadAsStringAsync(); return Ok(content); } else { return StatusCode((int)response.StatusCode, response.ReasonPhrase); } } } } ``` **Important Considerations for Custom Proxies:** * **Security:** Implement robust security measures to protect against vulnerabilities. * **Performance:** Optimize the proxy application for performance to minimize latency. * **Maintainability:** Design the application for maintainability and scalability. * **Error Handling:** Implement comprehensive error handling and logging. **Choosing the Right Solution** * **Azure Application Proxy:** The easiest and often the best option for simple scenarios where you just need to provide secure remote access to SharePoint Online. * **Reverse Proxy with WAF:** A good choice when you need more control over authentication, authorization, and security policies, and you want to protect against web attacks. * **Custom Proxy Application:** The most flexible option, but also the most complex to develop and maintain. Use this when you have very specific requirements that cannot be met by the other solutions. **Key Considerations for All Solutions** * **Authentication:** Use strong authentication methods, such as Azure AD with MFA. * **Authorization:** Implement granular authorization policies to control access to SharePoint Online resources. * **Logging and Monitoring:** Enable logging and monitoring to track access and identify potential security incidents. * **Regular Updates:** Keep your proxy server and related software up to date with the latest security patches. * **Least Privilege:** Grant users only the minimum necessary permissions. * **Network Segmentation:** Segment your network to isolate the proxy server from other systems. **In summary, there's no single "MCP server" button to push. You need to build a solution that acts as a secure gateway to SharePoint Online. Azure Application Proxy is often the best starting point, but consider the other options if you have more complex requirements.** Remember to replace placeholders like `yourtenant.sharepoint.com` and `/path/to/your/certificate.pem` with your actual values. Also, the code examples are simplified and may require further customization to meet your specific needs. Consult the official Microsoft documentation for detailed instructions and best practices.

MCP Text Editor Server

A Model Context Protocol (MCP) server that provides line-oriented text file editing capabilities through a standardized API. Optimized for LLM tools with efficient partial file access to minimize token usage.

simple-mcp-runner

Simple MCP Runner makes it effortless to safely expose system commands to language models via a lightweight MCP server—all configurable with a clean, minimal YAML file and zero boilerplate.

Code Search MCP

Enables LLMs to perform high-performance code search and analysis across multiple languages using symbol indexing, regex text search, and structural AST pattern matching. It also provides tools for technology stack detection and dependency analysis with persistent caching for optimized performance.

Azure Service Bus MCP Server

MCP server for Azure Service Bus that enables sending messages, inspecting queues and subscriptions, and purging test data. Complements the built-in Azure MCP server by adding write operations.

3dspace-mcp-server

Converts OpenAPI specifications into MCP tools to access 3DSpace Engineering Web Services APIs, enabling natural language interaction with 45+ services for engineering, manufacturing, and project management.

Personal MCP Server

Enables AI assistants to fetch and process YouTube video transcripts in multiple formats and languages, with built-in caching and rate limiting for efficient video content analysis.

Memory Palace

Persistent semantic memory for AI agents, enabling storage, semantic search, knowledge graph connections, and inter-instance messaging across conversations using local models via Ollama.

BetterMCPFileServer

Espelho de

TradeX MCP Server

Enables AI agents to research, analyze, and trade Pokemon card perpetual futures on the TradeX platform. It supports market data retrieval, trading simulations, and secure transaction execution using local Solana keypairs.

Browserbase MCP Server

Enables AI to control cloud browsers and automate web interactions through Browserbase and Stagehand. Supports web navigation, form filling, data extraction, screenshots, and automated actions with natural language commands.

mcp-toolselect

An MCP server that recommends specific tools for tasks by learning from usage patterns and historical success rates. It enables users to register tool capabilities and provides ranked recommendations that adapt based on feedback and execution data.

AI Agent Marketplace Index Search

Permite pesquisar agentes de IA por palavras-chave ou categorias, permitindo que os usuários descubram ferramentas como agentes de codificação, agentes de GUI ou assistentes específicos do setor em diversos marketplaces.

Chotu Robo Server

An MCP server that integrates Arduino-based robotics (ESP32 or Arduino Nano) with AI, allowing control of hardware components like LEDs, motors, servos, and sensors through AI assistants.

Findymail MCP Server

An MCP server integrating with Findymail API that enables email validation and finding work emails using names, companies, or profile URLs.

tsrs-mcp-server

Here are a few possible translations, depending on the context and what you want to emphasize: **More literal translations:** * **Servidor MCP Tushare em Rust** (This is a straightforward translation, good if you want to be clear and concise.) * **Servidor MCP Rust para Tushare** (This emphasizes that the Rust server is *for* Tushare.) **More descriptive translations (if you want to add context):** * **Servidor MCP implementado em Rust para a plataforma Tushare** (This is more descriptive, saying the server is *implemented* in Rust and *for* the Tushare platform.) * **Servidor MCP escrito em Rust para uso com Tushare** (This emphasizes that the server is *written* in Rust and *for use with* Tushare.) **Explanation of terms:** * **Tushare:** This is likely a proper noun and should remain as "Tushare" in Portuguese. * **Rust:** This is a programming language and should remain as "Rust" in Portuguese. * **MCP Server:** "MCP Server" is likely an abbreviation. Without knowing what "MCP" stands for, it's best to leave it as "Servidor MCP" in Portuguese. If you know what MCP stands for, you could translate that part. For example, if MCP stands for "Message Control Protocol," you could use "Servidor de Protocolo de Controle de Mensagens." However, keeping it as "Servidor MCP" is generally safer if you're unsure. Therefore, the best translation depends on the context. If you want a simple and direct translation, **"Servidor MCP Tushare em Rust"** is a good choice. If you want to be more descriptive, use one of the longer options.

Fabric MCP Server

An MCP server that exposes Fabric patterns as tools for Cline, enabling AI-driven pattern execution directly within Cline tasks.

OpenSCAD MCP Server

Enables AI assistants to render 3D models from OpenSCAD code, generating single views or multiple perspectives with full camera control. Supports animations, custom parameters, and returns base64-encoded PNG images for seamless integration.

Gmail MCP Server

A Model Context Protocol server that enables Claude AI to interact with Gmail, supporting email sending, reading, searching, labeling, draft management, and batch operations through natural language commands.

macOS Defaults MCP Server

Enables reading and writing macOS system defaults and settings through commands equivalent to the defaults command-line tool. Supports listing domains, searching for settings, and modifying system preferences programmatically.

autoglm-mcp

Enables AI agents to analyze and interact with Android phone screens via ADB, using the AutoGLM model to answer queries about screen content and coordinates.

Google Workspace MCP Server

Exposes a curated set of Google Workspace CLI operations as tools for managing Drive, Sheets, Calendar, Docs, and Gmail. It provides a focused set of high-value operations to avoid context window bloat while enabling file management, spreadsheet updates, and email interactions.

Superset MCP Server - TypeScript

Enables AI assistants to interact with Apache Superset instances programmatically, providing 45+ tools for dashboard management, chart creation, database operations, SQL execution, and complete Superset API coverage. Supports multiple transport modes including stdio, SSE, and HTTP streaming for flexible deployment options.