Discover Awesome MCP Servers

SudoMock

Product mockup rendering API for e-commerce and print-on-demand. Upload Photoshop PSD templates, render photorealistic mockups by placing your designs onto smart object layers. 9 tools including AI-powered render (no PSD needed), template management, and account info. Supports remote HTTP (OAuth) and local stdio (npx) transports.

🤖 Laravel Vibes

머신 컨트롤 프로토콜(MCP) 서버를 구현하기 위한 라라벨 패키지

MCP Printer Server

Enables AI assistants to print documents, manage print queues, and control printers on macOS/Linux systems via the CUPS printing system. Supports printing PDFs, text files, and other formats with options like duplex printing, landscape orientation, and multiple copies.

Chaitin Rivers Radar

Rivers Radar MCP Based on large language models, provides data querying, analysis and operation capabilities for Chaitin Rivers Cloud - Website Security Monitoring through MCP Tools.

MCP WeChat Official Accounts Spider

Enables AI agents to crawl, access, and analyze WeChat Official Account articles using Selenium and the Model Context Protocol. It provides specialized tools for dynamic content retrieval, image processing, and automated article analysis.

cwtwb

ai generate tableau file

MCP Helm Chart

MCP 서버용 Helm 차트

macOS Native OCR MCP Server

Provides offline, high-accuracy OCR capabilities for images and PDFs using macOS's built-in Vision framework. Supports multi-language text extraction with intelligent block aggregation for tables and paragraphs, outputting structured JSON data suitable for document reconstruction.

MCP Login Server

Provides automated login functionality for localhost web applications using predefined credentials, designed to work with browser automation tools like the Playwright MCP server.

MCP Server.exe

A powerful executable server for running Model Context Protocol services that supports tool chain execution, multiple MCP services management, and a pluggable tool system for complex automation workflows.

fmod-mcp

An MCP server that enables AI coding agents to control FMOD Studio for audio import, event creation, and bank building via TCP scripting.

Giphy API MCP Server

An auto-generated Multi-Agent Conversation Protocol (MCP) Server that enables interaction with Giphy's API through natural language, allowing users to search, retrieve, and work with GIF content programmatically.

Street View Publish API MCP Server

Enables interaction with Google's Street View Publish API for publishing and managing 360 photos on Google Street View through natural language commands.

mcp-api-tester Tools & Interfaces

LLM API 테스트를 위한 MCP 서버

Master MCP Server

Aggregates multiple MCP servers behind a single, secure endpoint with unified tool/resource discovery, OAuth authentication, and resilient request routing. Enables users to manage and interact with multiple MCP backends through one centralized interface with load balancing and circuit breakers.

Rovodev MCP Tool

Integrates the Atlassian Rovo Dev CLI with the Model Context Protocol, allowing AI assistants to perform deep code analysis using Rovo Dev's large context capabilities. It enables features like repository-wide queries, file-specific analysis, and specialized coding modes through a standard MCP interface.

MCP Podcast Scraper

An MCP server that scrapes and transcribes podcast episodes from YouTube or RSS feeds using Deepgram's Nova-2 model. It allows users to track podcasts for new episodes, manage transcripts, and generate personalized summaries through Claude.

MCP Google Server

A Model Context Protocol server providing web search capabilities using Google Custom Search API and webpage content extraction functionality.

EdgeOne Geo MCP Server

Enables large language models to retrieve user geolocation data using EdgeOne Pages Functions. It provides a dedicated tool to fetch location information in JSON format through the Model Context Protocol.

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.

Task MCP Server

A simple task management server that enables users to add, list, complete, and delete tasks through natural language interactions in Claude Desktop.

bonnard

Open-source agentic schema layer. Define metrics once in YAML, query governed data from any warehouse (Snowflake, BigQuery, Databricks, PostgreSQL, DuckDB) via MCP.

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.

MCP Server Gemini

A Model Context Protocol server that enables Claude Desktop and other MCP-compatible clients to leverage Google's Gemini AI models with features like thinking models, Google Search grounding, JSON mode, and vision support.

Azure Assistant MCP

Enables natural language exploration of Azure environments by generating and executing KQL queries against Azure Resource Graph. Supports multi-tenant configurations, subscription scoping, and provides direct access to Azure resource information through conversational interactions.

Book4Time MCP Server

Enables interaction with the Book4Time API through an Azure Function-hosted server. It allows users to query product information and manage bookings using MCP-compatible clients like Claude Desktop.

PortalMCP

Universal AI gateway that enables interaction with Ethereum blockchain through natural language across multiple AI platforms (Claude, ChatGPT, Gemini, etc.). Supports contract deployment, token operations, NFT minting, DeFi operations, and general blockchain transactions.