Discover Awesome MCP Servers

MCP Documentation Server

A server that provides organized documentation content for various applications using the Model Context Protocol, enabling AI assistants to access quickstart guides and code examples.

Easy MCP GitHub Tools Application

MCP를 통해 GitHub와 원활하게 통합되도록 설계된 강력한 도구 세트

steampipe-mcp

steampipe-mcp

İhale MCP

Enables users to search and access Turkish public procurement data from EKAP v2 portal. Provides comprehensive tender search, detailed tender information, announcements, and authority/classification code lookups through natural language interactions.

Local Scanner MCP Server

로컬 코드 및 localhost URL을 스캔하는 MCP 서버

nUR MCP Server

An intelligent middleware system that enables natural language interactive control of Universal Robots collaborative robots, allowing users to connect to and control industrial robots through voice/text commands with MCP-compatible LLMs.

Zendesk MCP Server

A server implementation that provides Claude AI with the ability to interact with Zendesk ticketing systems through various functions including retrieving, searching, creating, and updating tickets.

Avalara AvaTax MCP Server by CData

This read-only MCP Server allows you to connect to Avalara AvaTax data from Claude Desktop through CData JDBC Drivers. Free (beta) read/write servers available at https://www.cdata.com/solutions/mcp

Oracle Service Cloud MCP Server by CData

This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Oracle Service Cloud (beta): https://www.cdata.com/download/download.aspx?sku=KOZK-V&type=beta

webdev-mcp

An MCP server providing web development tools such as screen capturing capabilities that let AI agents take and work with screenshots of the user's screen.

Weather MCP Tool

An India-focused MCP server that provides real-time weather conditions, forecasts, air quality data, and location search capabilities using the OpenWeatherMap API.

Teams MCP

A Model Context Protocol server that provides AI assistants with access to Microsoft Teams, enabling interaction with teams, channels, chats, and organizational data through Microsoft Graph APIs.

Lindorm MCP Server

An example server that enables interaction with Alibaba Cloud's Lindorm multi-model NoSQL database, allowing applications to perform vector searches, full-text searches, and SQL operations through a unified interface.

聚义厅MCP

An AI personality collaboration tool based on Model Context Protocol (MCP) that enables users to summon and collaborate with multiple AI personas for intelligent analysis and problem-solving.

MCP Server Template (

이 템플릿은 권장 사례를 기반으로 새로운 MCP(Model Context Protocol) 서버 프로젝트를 빠르게 시작할 수 있도록 도와줍니다.

On Running MCP

On Running API와 상호 작용하기 위한 MCP 서버

OMNI-Sales

Sales MCP Server

Remote MCP Server on Cloudflare

A deployable Model Context Protocol server that runs on Cloudflare Workers without requiring authentication, allowing users to create custom AI tools and connect them to clients like Claude Desktop and Cloudflare AI Playground.

MCP TypeScript SDK

A toolkit for building Model Context Protocol servers and clients that provide standardized context for LLMs, allowing applications to expose resources, tools, and prompts through stdio or Streamable HTTP transports.

RT-Prompt-MCP

A Model Context Protocol server that provides specialized prompt suggestions for backend development, frontend development, and general tasks to help LLMs generate better content.

Hello Service MCP Server

A unified HTTP/HTTPS service that exposes Model Context Protocol (MCP) functionality over HTTP endpoints, allowing clients to list available tools and call them through a standardized API.

LayerZero OFT MCP Server

A TypeScript/Node.js server that enables creating, deploying, and bridging Omnichain Fungible Tokens (OFTs) across multiple blockchains using LayerZero protocols.

Untappd MCP Server using Azure Functions

Okay, here's an example of a minimal, complete, and verifiable (MCP) Azure Function written in F# that uses the Azure Functions programming model (isolated process): ```fsharp namespace MyFunctionApp open Microsoft.Azure.Functions.Worker open Microsoft.Azure.Functions.Worker.Http open System.Net [<EntryPoint>] let Run([<HttpTrigger(AuthorizationLevel.Anonymous, "get", "post")>] req: HttpRequestData, context: FunctionContext) : HttpResponseData = context.GetLogger "HttpExample" |> ignore let name = req.Query.GetValues("name") |> Seq.tryHead |> Option.defaultValue "Azure Functions" let response = req.CreateResponse(HttpStatusCode.OK) response.Headers.Add("Content-Type", "text/plain; charset=utf-8") response.WriteString($"Welcome to F#, {name}!") response ``` **Explanation:** * **`namespace MyFunctionApp`**: Defines the namespace for your function. Important for organization and potential dependency resolution. * **`open Microsoft.Azure.Functions.Worker`**: Imports the core Azure Functions Worker SDK. This is essential for isolated process functions. * **`open Microsoft.Azure.Functions.Worker.Http`**: Imports the HTTP-specific types for working with HTTP triggers and responses. * **`open System.Net`**: Imports the `System.Net` namespace, which provides access to network-related classes, including `HttpStatusCode`. * **`[<EntryPoint>]`**: This attribute marks the `Run` function as the entry point for the Azure Function. It's crucial. * **`let Run([<HttpTrigger(AuthorizationLevel.Anonymous, "get", "post")>] req: HttpRequestData, context: FunctionContext) : HttpResponseData =`**: * **`let Run(...)`**: Defines the function named `Run`. This is the standard name for an Azure Function. * **`[<HttpTrigger(AuthorizationLevel.Anonymous, "get", "post")>]`**: This attribute defines the trigger for the function. In this case, it's an HTTP trigger that responds to both GET and POST requests. `AuthorizationLevel.Anonymous` means no authentication is required. You can change this to `Function`, `Admin`, or `User` if you need authentication. * **`req: HttpRequestData`**: The `req` parameter is an `HttpRequestData` object, which represents the incoming HTTP request. It provides access to headers, query parameters, the request body, etc. * **`context: FunctionContext`**: The `context` parameter is a `FunctionContext` object, which provides access to the function's execution context, including logging, invocation ID, and other metadata. * **`: HttpResponseData`**: Specifies that the function returns an `HttpResponseData` object, which represents the HTTP response. * **`context.GetLogger "HttpExample" |> ignore`**: Gets a logger instance (named "HttpExample") from the context. The `ignore` function discards the logger instance, but in a real-world function, you would use the logger to write log messages. * **`let name = ...`**: This section extracts the `name` query parameter from the request. * **`req.Query.GetValues("name")`**: Gets a sequence of values associated with the query parameter "name". Query parameters are part of the URL (e.g., `?name=John`). * **`|> Seq.tryHead`**: Attempts to get the first element of the sequence. If the sequence is empty (i.e., the "name" parameter is not present), it returns `None`. * **`|> Option.defaultValue "Azure Functions"`**: If the `tryHead` returns `None`, this provides a default value of "Azure Functions". So, if the `name` parameter is missing, the function will use the default name. * **`let response = req.CreateResponse(HttpStatusCode.OK)`**: Creates an `HttpResponseData` object with an HTTP status code of 200 (OK). The `req.CreateResponse` method is the recommended way to create a response object. * **`response.Headers.Add("Content-Type", "text/plain; charset=utf-8")`**: Sets the `Content-Type` header of the response to `text/plain; charset=utf-8`. This tells the client that the response body is plain text encoded in UTF-8. * **`response.WriteString($"Welcome to F#, {name}!")`**: Writes the response body. The `$` indicates an interpolated string, which allows you to embed variables directly into the string. * **`response`**: Returns the `HttpResponseData` object. **How to Deploy and Test:** 1. **Create an Azure Functions Project:** Use the Azure Functions extension in VS Code or the Azure CLI to create a new F# Azure Functions project using the isolated process model. Make sure you select the `.NET 6.0` or later runtime. 2. **Replace the Default Function:** Replace the contents of the default function file (usually `Function1.fs`) with the code above. 3. **Publish to Azure:** Use the Azure Functions extension in VS Code or the Azure CLI to publish your project to an Azure Functions app. 4. **Test:** After deployment, you can test the function by sending an HTTP request to its URL. For example: * `https://<your-function-app-name>.azurewebsites.net/api/Function1?name=YourName` * If you don't provide the `name` parameter, it will default to "Azure Functions". **Key Considerations for Isolated Process Functions:** * **Isolated Process:** Isolated process functions run in a separate process from the Azure Functions host. This provides better isolation and allows you to use different .NET runtimes. * **`Microsoft.Azure.Functions.Worker` Package:** You *must* use the `Microsoft.Azure.Functions.Worker` NuGet package for isolated process functions. Do *not* use the `Microsoft.Azure.WebJobs.Extensions.*` packages, which are for in-process functions. * **`FunctionContext`:** The `FunctionContext` is essential for accessing logging and other function-specific information. * **`HttpRequestData` and `HttpResponseData`:** Use these types for working with HTTP requests and responses in isolated process functions. They provide a more streamlined and efficient way to handle HTTP data. * **Startup Class (Optional):** For more complex scenarios (dependency injection, configuration), you can create a `Startup.fs` file to configure your function app. This example provides a solid foundation for building more complex Azure Functions in F#. Remember to adjust the trigger type, authorization level, and function logic to meet your specific requirements.

Gotas Commerce MCP Server

A bridge between AI assistants and cryptocurrency payment services that enables creating and verifying USDT transactions through the Gotas Commerce API.

SFCC Development MCP Server

Provides comprehensive access to Salesforce B2C Commerce Cloud development tools including SFCC API documentation, best practices guides, log analysis, and system object definitions. Enables AI assistants to help with SFCC development tasks through both documentation-only mode and full credential-based mode.