Discover Awesome MCP Servers

MySQL-Performance-Tuner-Mcp

MySQL MCP Performance Tuning Server - AI-powered MySQL performance tuning capabilities

lightwave-mcp

Enables AI agents to discover and control LightwaveRF Smart Series devices (lights, switches, sockets) via the official REST API, using natural language commands like 'turn off the kitchen light'.

mcp-memory-gateway

An MCP server that provides memory management and gateway capabilities, enabling persistent storage and retrieval of contextual information across sessions.

repo-index-mcp

A local codebase retrieval tool that indexes a git repository into SQLite and provides query and retrieval capabilities over MCP stdio, enabling coding agents to search and retrieve code chunks from local repositories without external data transmission.

PiKVM MCP

A safety-first Model Context Protocol server for controlling a single PiKVM device, enabling keyboard, mouse, and power operations with strong security and audit.

frontend-mcp

Enables frontend navigation and browser automation through a deterministic MCP server, integrating Browser Use and optional code graph hints for coding agents.

Cryptocurrency Market Data Server

Fornece dados do mercado de criptomoedas em tempo real e históricos através da integração com as principais bolsas. Este servidor permite que LLMs como o Claude busquem preços atuais, analisem tendências de mercado e acessem informações detalhadas de negociação.

codebase-memory-mcp

Local-first repository memory for AI coding agents that indexes codebases into SQLite and exposes it through MCP tools, with a browser dashboard for architecture inspection.

Ninja MCP

MCP server for AI agents to interact with the Ninja/AnaNinja mobile API, enabling mobile-compatible auth, address management, retail/grocery product search, draft order validation, and checkout/payment flows.

docdex

Docdex is a lightweight, local documentation indexer/search daemon. It runs per-project, keeps an on-disk index of your markdown/text docs, and serves top-k snippets over HTTP or CLI for any coding assistant or tool—no external services or uploads required.

DALL-E MCP Server

An MCP (Model Context Protocol) server that allows generating, editing, and creating variations of images using OpenAI's DALL-E APIs.

TPLCP Reference MCP

Turns the 2026 CLCP orientation corpus into a searchable, citation-preserving reference source for TPLCP report work.

Luxembourgish Competition MCP

Enables querying Luxembourgish competition data, including regulations, decisions, and requirements from the Conseil de la concurrence, directly from MCP-compatible clients.

Aden Aggregates MCP Server

Exposes Aden Aggregates submittal data as tools callable by Claude, enabling retrieval of location, material, pricing, and lab report information to build submittal packages.

Canvas AIGC

A MCP server that bridges web canvas with local Codex/Claude, exposing 23 tools for reading, creating, modifying, connecting, and generating canvas content via local HTTP bridge and stdio MCP.

Agentic Travel Recommendations Service

Enables agents to discover and invoke travel recommendations with partner-specific caps and exclusions via MCP JSON-RPC.

Semantic Mesh Memory (SEM) MCP Server

Provides a coherent memory layer for LLM agents that models beliefs as nodes in a constraint network to detect and surface semantic contradictions. It uses local embeddings and a hybrid geometric-logical energy model to identify conflicting information that requires review.

duplicacy-mcp

MCP server that reads Duplicacy backup metrics from a Prometheus exporter and exposes them to LLMs for monitoring backup status, progress, and health.

globus-mcp

MCP server enabling LLMs to manage Globus data transfers and compute tasks.

TradingView-MCP

Enables AI to analyze and manipulate TradingView charts via Chrome DevTools Protocol, and access market data through public scanner API.

freshrss-mcp-server

MCP server for interacting with FreshRSS via the Google Reader API, enabling subscription management, content reading, and item operations.

odoo-mcp-uvx

A read-only MCP server that enables AI assistants to query Odoo instances via XML-RPC, supporting search, read, count, and field inspection without requiring custom modules.

azure-devops-mcp

Here's a breakdown of what "Azure DevOps MCP C# server and client code" likely refers to, along with explanations and examples. It's important to understand that "MCP" (Microsoft Certified Professional) is a broad term, and Azure DevOps is a complex system. Therefore, I'll provide a general overview and then suggest how to narrow down your search for more specific code examples. **Understanding the Terms** * **Azure DevOps:** A suite of services from Microsoft that covers the entire software development lifecycle. Key components include: * **Azure Boards:** Work item tracking (tasks, bugs, user stories). * **Azure Repos:** Source code management (Git). * **Azure Pipelines:** Continuous integration and continuous delivery (CI/CD). * **Azure Test Plans:** Test management. * **Azure Artifacts:** Package management (NuGet, npm, Maven, etc.). * **MCP (Microsoft Certified Professional):** A general term for someone who has passed a Microsoft certification exam. It doesn't directly imply specific code skills. It *suggests* the person has a certain level of understanding of Microsoft technologies. * **C#:** A modern, object-oriented programming language widely used for developing applications on the .NET platform. * **Server Code:** Code that runs on a server (e.g., a web server, an application server, an Azure Function). In the context of Azure DevOps, this might be code that interacts with the Azure DevOps REST API or handles webhooks. * **Client Code:** Code that runs on a client device (e.g., a web browser, a desktop application, a mobile app). This code typically interacts with a server to retrieve data or perform actions. In the context of Azure DevOps, this might be a web application that displays work items or a command-line tool that automates tasks. **What "Azure DevOps MCP C# server and client code" Likely Means** Someone with an MCP certification who is proficient in C# might write code to: 1. **Interact with the Azure DevOps REST API:** This is the most common scenario. The Azure DevOps REST API allows you to programmatically access and manage almost everything in Azure DevOps. 2. **Create Azure DevOps Extensions:** You can extend the functionality of Azure DevOps by creating extensions that add new features to the web interface or integrate with other services. 3. **Build Custom Build/Release Tasks:** You can create custom tasks for Azure Pipelines to automate specific steps in your CI/CD process. 4. **Develop Integrations with Other Systems:** You might write code to integrate Azure DevOps with other tools, such as Slack, Microsoft Teams, or Jira. 5. **Automate Azure DevOps Administration:** You can use the REST API to automate tasks such as creating projects, managing users, and configuring permissions. **General Examples (Illustrative)** These are simplified examples to give you an idea. Real-world code would be more complex and handle error conditions, authentication, and other details. **1. Server-Side C# Code (Azure Function) to Get Work Items:** ```csharp using System; using System.IO; using System.Threading.Tasks; using Microsoft.AspNetCore.Mvc; using Microsoft.Azure.WebJobs; using Microsoft.Azure.WebJobs.Extensions.Http; using Microsoft.AspNetCore.Http; using Microsoft.Extensions.Logging; using Newtonsoft.Json; using System.Net.Http; using System.Net.Http.Headers; public static class GetWorkItems { [FunctionName("GetWorkItems")] public static async Task<IActionResult> Run( [HttpTrigger(AuthorizationLevel.Function, "get", Route = null)] HttpRequest req, ILogger log) { log.LogInformation("C# HTTP trigger function processed a request."); string organization = "your-organization"; // Replace with your Azure DevOps organization string project = "your-project"; // Replace with your Azure DevOps project string pat = "your-personal-access-token"; // Replace with your PAT string requestUrl = $"https://dev.azure.com/{organization}/{project}/_apis/wit/workitems?api-version=7.0"; using (HttpClient client = new HttpClient()) { client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json")); client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Basic", Convert.ToBase64String(System.Text.ASCIIEncoding.ASCII.GetBytes($":{pat}"))); using (HttpResponseMessage response = await client.GetAsync(requestUrl)) { response.EnsureSuccessStatusCode(); // Throw exception if not successful string responseBody = await response.Content.ReadAsStringAsync(); // Deserialize the JSON response into a C# object (you'll need to define a class to represent the work item structure) // Example: // var workItems = JsonConvert.DeserializeObject<WorkItem[]>(responseBody); return new OkObjectResult(responseBody); // Return the JSON response } } } } ``` **Explanation:** * This is an Azure Function triggered by an HTTP request. * It uses the `HttpClient` class to make a GET request to the Azure DevOps REST API. * It uses a Personal Access Token (PAT) for authentication. **Important:** Never hardcode PATs in production code. Use environment variables or Azure Key Vault. * It retrieves work items from a specified organization and project. * It deserializes the JSON response (you'll need to define a `WorkItem` class to match the structure of the JSON). * It returns the JSON response as an `OkObjectResult`. **2. Client-Side C# Code (Console Application) to Create a Work Item:** ```csharp using System; using System.Net.Http; using System.Net.Http.Headers; using System.Text; using System.Threading.Tasks; using Newtonsoft.Json; public class Program { public static async Task Main(string[] args) { string organization = "your-organization"; // Replace with your Azure DevOps organization string project = "your-project"; // Replace with your Azure DevOps project string pat = "your-personal-access-token"; // Replace with your PAT string requestUrl = $"https://dev.azure.com/{organization}/{project}/_apis/wit/workitems/$Task?api-version=7.0"; using (HttpClient client = new HttpClient()) { client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json")); client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Basic", Convert.ToBase64String(System.Text.ASCIIEncoding.ASCII.GetBytes($":{pat}"))); // Define the work item fields var workItem = new[] { new { op = "add", path = "/fields/System.Title", value = "My New Task" }, new { op = "add", path = "/fields/System.Description", value = "This is a description of the task." } }; string jsonContent = JsonConvert.SerializeObject(workItem); var content = new StringContent(jsonContent, Encoding.UTF8, "application/json-patch+json"); using (HttpResponseMessage response = await client.PatchAsync(requestUrl, content)) { response.EnsureSuccessStatusCode(); string responseBody = await response.Content.ReadAsStringAsync(); Console.WriteLine(responseBody); // Print the response (e.g., the created work item) } } } } ``` **Explanation:** * This is a console application. * It uses the `HttpClient` class to make a PATCH request to the Azure DevOps REST API (PATCH is used for creating or updating work items). * It uses a Personal Access Token (PAT) for authentication. * It defines the fields for the new work item (title and description). * It serializes the work item data into JSON. * It sends the JSON data in the request body. * It prints the response from the server (which will typically include the ID of the newly created work item). **Important Considerations:** * **Authentication:** Using Personal Access Tokens (PATs) is common for development and testing, but for production applications, you should use more secure authentication methods, such as Azure Active Directory (Azure AD) or Managed Identities. * **Error Handling:** The examples above lack robust error handling. You should always include `try-catch` blocks to handle exceptions and log errors. * **JSON Serialization/Deserialization:** Use a library like `Newtonsoft.Json` (Json.NET) or `System.Text.Json` to serialize and deserialize JSON data. Define C# classes that match the structure of the JSON data you're working with. * **NuGet Packages:** You'll need to install the `Newtonsoft.Json` NuGet package (or `System.Text.Json`) in your C# projects. * **API Versions:** The Azure DevOps REST API is versioned. Make sure you're using a supported API version (e.g., `api-version=7.0`). * **Rate Limiting:** Be aware of Azure DevOps rate limits. Implement retry logic to handle rate limiting errors. * **Security:** Never store sensitive information (like PATs) directly in your code. Use environment variables, Azure Key Vault, or other secure storage mechanisms. **How to Find More Specific Code Examples** To find more specific code examples, try these approaches: 1. **Microsoft Documentation:** The official Microsoft documentation for the Azure DevOps REST API is your best resource. It includes code samples in C# and other languages. Start here: [https://learn.microsoft.com/en-us/rest/api/azure/devops/](https://learn.microsoft.com/en-us/rest/api/azure/devops/) 2. **GitHub:** Search GitHub for repositories that contain Azure DevOps C# code. Use keywords like: * `azure devops rest api c#` * `azure devops extension c#` * `azure pipelines task c#` * `vsts api c#` (VSTS was the previous name for Azure DevOps) 3. **Stack Overflow:** Search Stack Overflow for questions and answers related to Azure DevOps C# development. 4. **Azure DevOps Samples:** Microsoft provides some official sample projects. Look for these on GitHub. 5. **Specific Use Cases:** Think about the specific tasks you want to automate or the integrations you want to build. Search for code examples that address those specific use cases. For example: * "C# Azure DevOps create work item" * "C# Azure DevOps get build status" * "C# Azure DevOps trigger pipeline" **Example Search on GitHub:** Go to GitHub and search for: `azure devops rest api c#` You'll find many repositories that contain C# code for interacting with the Azure DevOps REST API. Browse through the repositories to find code that matches your needs. Pay attention to the license of the code before using it in your own projects. **In summary:** The term "Azure DevOps MCP C# server and client code" is quite broad. Focus on the specific tasks you want to accomplish with Azure DevOps, and then search for code examples that address those tasks. The Microsoft documentation and GitHub are your best resources. Remember to prioritize security and error handling in your code.

Calendar MCP Server

A production-quality MCP server for calendar management with robust timezone handling, recurrence support, and idempotency guarantees.

OmniDocs MCP

An intelligent MCP server that enables AI agents to crawl, index, and semantically search official framework documentation using local RAG. It prevents hallucinations by providing precise, up-to-date documentation excerpts directly into the AI's context window.

iai-mcp

A local MCP server that gives AI assistants a long-term memory by capturing sessions verbatim and surfacing relevant context automatically.

DigitalOcean MCP Server

Provides access to all 471+ DigitalOcean API endpoints through an MCP server that dynamically extracts them from the OpenAPI specification, enabling search, filtering, and direct API calls with proper authentication.

RetireGolden MCP

Headless MCP server for the RetireGolden retirement-planning calculator, providing typed tools to build/validate plans, run projections, Monte Carlo simulations, and optimization via stdio.

Ultimath

Stop hallucinating numbers. An MCP server that runs every math expression through four independent numeric engines in parallel and returns all four results side by side — so when they disagree, you know the answer is numerically unreliable.

fs-mcp

Hosted filesystem MCP server over HTTP with auth. Enables reading, writing, editing, searching, and listing files via MCP tools like grep, glob, and tree.