Discover Awesome MCP Servers

admitad-mcp

Enables AI assistants to browse Admitad affiliate programs, discover product feeds, and search products directly from chat.

MCP All-in-One Server

A versatile MCP server providing tools for arithmetic operations, n8n webhook integration, and access to a customer support playbook resource. It also includes specialized prompt templates for converting webinar transcripts into engaging blog posts.

Influship MCP

Enables AI-native creator discovery for influencer marketing, including creator search, lookalikes, profile lookup, and Instagram post transcript analysis.

FreightUtils MCP Server

AI agent access to 11 freight calculation and reference tools — LDM, CBM, chargeable weight, pallet fitting, ADR dangerous goods (2,939 entries), airline codes (6,352), HS codes (6,940), INCOTERMS, container specs, unit converter, and ADR 1.1.3.6 exemption calculator.

Sequential Thinking Tool API

A Node.js/TypeScript backend for managing sequential thinking sessions, allowing users to create sessions and post thoughts in a structured sequence with support for real-time updates via Server-Sent Events.

MCP Documentation Server

Enables semantic search and retrieval of MCP (Model Context Protocol) documentation using Redis-backed embeddings, allowing users to query and access documentation content through natural language.

groowooth

MCP server that enables AI agents to assess child growth, plot growth curves, and interpret z-scores using WHO and China NHC standards.

Remote MCP Server

A Cloudflare Workers-based MCP server that enables tool integration with Claude AI through OAuth login, allowing users to extend Claude's capabilities with custom tools like mathematical operations.

threadwork

A multi-agent collaboration tool for Claude Code that supports hot-swappable role YAML, persistent memory with SQLite and FTS5, and step-level replay in a single-file HTML viewer.

mcpserver-ts

Here's a basic MCP (Minimal, Complete, and Verifiable) server template in TypeScript for quick mock data, along with explanations to help you understand and adapt it: ```typescript // Dependencies import express, { Request, Response } from 'express'; import cors from 'cors'; // Optional, but useful for local development import bodyParser from 'body-parser'; // For parsing request bodies // Configuration const port = process.env.PORT || 3000; // Use environment variable or default to 3000 const app = express(); // Middleware app.use(cors()); // Enable CORS for all origins (for development - be careful in production) app.use(bodyParser.json()); // Parse JSON request bodies // Mock Data (Replace with your actual data) const mockData = [ { id: 1, name: 'Item 1', description: 'This is the first item.' }, { id: 2, name: 'Item 2', description: 'This is the second item.' }, { id: 3, name: 'Item 3', description: 'This is the third item.' }, ]; // Routes app.get('/items', (req: Request, res: Response) => { res.json(mockData); }); app.get('/items/:id', (req: Request, res: Response) => { const id = parseInt(req.params.id); // Convert ID to number const item = mockData.find(item => item.id === id); if (item) { res.json(item); } else { res.status(404).json({ message: 'Item not found' }); } }); app.post('/items', (req: Request, res: Response) => { const newItem = { id: mockData.length + 1, // Simple ID generation (not suitable for production) ...req.body, }; mockData.push(newItem); res.status(201).json(newItem); // 201 Created }); app.put('/items/:id', (req: Request, res: Response) => { const id = parseInt(req.params.id); const itemIndex = mockData.findIndex(item => item.id === id); if (itemIndex !== -1) { mockData[itemIndex] = { ...mockData[itemIndex], ...req.body, id: id }; // Update with request body res.json(mockData[itemIndex]); } else { res.status(404).json({ message: 'Item not found' }); } }); app.delete('/items/:id', (req: Request, res: Response) => { const id = parseInt(req.params.id); const itemIndex = mockData.findIndex(item => item.id === id); if (itemIndex !== -1) { mockData.splice(itemIndex, 1); res.status(204).send(); // 204 No Content (successful deletion) } else { res.status(404).json({ message: 'Item not found' }); } }); // Start the server app.listen(port, () => { console.log(`Server listening on port ${port}`); }); ``` **Explanation:** 1. **Dependencies:** - `express`: The core web framework for Node.js. - `cors`: Middleware to enable Cross-Origin Resource Sharing (CORS). Crucial for allowing your frontend (running on a different port) to access the server. **Important:** In production, you should configure CORS to only allow specific origins for security. - `body-parser`: Middleware to parse the body of incoming requests. Specifically, `bodyParser.json()` parses JSON data. 2. **Configuration:** - `port`: Sets the port the server will listen on. It tries to use the `PORT` environment variable (useful for deployment) and defaults to 3000 if the environment variable isn't set. - `app = express()`: Creates an Express application instance. 3. **Middleware:** - `app.use(cors())`: Enables CORS for all origins. **Use with caution in production!** Configure it properly. - `app.use(bodyParser.json())`: Tells Express to use the `body-parser` middleware to parse JSON request bodies. This is necessary so you can access data sent in the body of `POST`, `PUT`, and `PATCH` requests. 4. **Mock Data:** - `mockData`: This is where you define your sample data. It's a simple JavaScript array of objects. **Replace this with your actual mock data.** You can load this data from a file (e.g., a JSON file) if you have a lot of data. 5. **Routes:** - `app.get('/items', ...)`: Defines a route that handles `GET` requests to `/items`. It returns the entire `mockData` array as a JSON response. - `app.get('/items/:id', ...)`: Defines a route that handles `GET` requests to `/items/:id`, where `:id` is a route parameter. It extracts the `id` from the URL, finds the corresponding item in `mockData`, and returns it as a JSON response. If the item is not found, it returns a 404 (Not Found) error. - `app.post('/items', ...)`: Handles `POST` requests to `/items`. It creates a new item by taking the data from the request body (`req.body`), assigning it a new ID, adding it to the `mockData` array, and returning the new item with a 201 (Created) status code. - `app.put('/items/:id', ...)`: Handles `PUT` requests to `/items/:id`. It updates an existing item. It finds the item by ID, merges the data from the request body into the existing item, and returns the updated item. If the item is not found, it returns a 404 error. - `app.delete('/items/:id', ...)`: Handles `DELETE` requests to `/items/:id`. It deletes an item. It finds the item by ID, removes it from the `mockData` array, and returns a 204 (No Content) status code. 6. **Start the Server:** - `app.listen(port, ...)`: Starts the Express server and listens for incoming requests on the specified port. The callback function logs a message to the console indicating that the server is running. **How to Use:** 1. **Install Node.js and npm:** Make sure you have Node.js and npm (Node Package Manager) installed. 2. **Create a Project Directory:** Create a new directory for your project. 3. **Initialize the Project:** ```bash npm init -y ``` 4. **Install Dependencies:** ```bash npm install express cors body-parser typescript @types/express @types/node --save-dev ``` 5. **Create `tsconfig.json`:** Create a `tsconfig.json` file in your project root to configure the TypeScript compiler. A basic configuration would be: ```json { "compilerOptions": { "target": "es6", "module": "commonjs", "outDir": "./dist", "strict": true, "esModuleInterop": true, "skipLibCheck": true, "forceConsistentCasingInFileNames": true }, "include": ["src/**/*"], "exclude": ["node_modules"] } ``` 6. **Create `src/index.ts`:** Create a directory named `src` and save the TypeScript code above as `src/index.ts`. 7. **Compile the TypeScript:** ```bash npx tsc ``` This will compile your TypeScript code into JavaScript files in the `dist` directory. 8. **Run the Server:** ```bash node dist/index.js ``` Or, if you want to use `ts-node` for direct execution (without compiling first, useful for development): ```bash npm install -g ts-node # Install globally (if you haven't already) ts-node src/index.ts ``` 9. **Test the API:** Use a tool like `curl`, `Postman`, or a browser to test your API endpoints. For example: - `GET http://localhost:3000/items` - `GET http://localhost:3000/items/1` - `POST http://localhost:3000/items` (with a JSON body) **Key Improvements and Considerations:** * **TypeScript:** Using TypeScript provides type safety and helps catch errors early. * **CORS:** `cors` is essential for local development when your frontend is running on a different port. **Configure CORS properly for production!** Don't use `cors()` without any options in a production environment. * **Error Handling:** The example includes basic error handling (e.g., 404 Not Found). You should add more robust error handling for a production application. * **ID Generation:** The ID generation in the `POST` route is very basic and not suitable for production. Use a proper ID generation strategy (e.g., UUIDs, database auto-increment). * **Data Persistence:** This example uses in-memory data. For a real application, you'll need to connect to a database (e.g., MongoDB, PostgreSQL). * **Validation:** You should validate the data in the request body to ensure it's in the correct format and meets your requirements. Libraries like `joi` or `express-validator` can help with this. * **Environment Variables:** Use environment variables for configuration (e.g., database connection strings, API keys). * **Logging:** Add logging to your application to help with debugging and monitoring. * **Testing:** Write unit tests and integration tests to ensure your API is working correctly. * **Asynchronous Operations:** For more complex operations (e.g., database access), use asynchronous functions (`async/await`) to avoid blocking the event loop. **Portuguese Translation of Key Terms:** * **Server:** Servidor * **Template:** Modelo * **Mock Data:** Dados simulados / Dados de teste * **TypeScript:** TypeScript (the name remains the same) * **Dependencies:** Dependências * **Configuration:** Configuração * **Middleware:** Middleware (the name remains the same) * **Routes:** Rotas * **Request:** Requisição * **Response:** Resposta * **Port:** Porta * **Error:** Erro * **Not Found:** Não encontrado * **Created:** Criado * **No Content:** Sem conteúdo * **Environment Variables:** Variáveis de ambiente * **Logging:** Registro (de logs) * **Testing:** Teste * **Asynchronous:** Assíncrono This template provides a solid foundation for building a mock API server in TypeScript. Remember to adapt it to your specific needs and add the necessary features for your application.

ZiweiAI

紫微AI，是一个紫微斗数解盘AI应用。Ziwei AI is an AI application for Ziwei Doushu chart interpretation.紫微AIは、紫微斗数のチャート解読のためのAIアプリケーションです。

Weather MCP Agent

Enables querying real-time weather data for Israeli cities through natural language, using Playwright to scrape weather2day and Gemini LLM to answer.

Alayman MCP Server

Enables access to articles from alayman.io, allowing users to fetch, search, and filter technical content through natural language. It supports pagination and keyword-based filtering for specific topics like React, Angular, and TypeScript.

go-mcp-server-mds

Uma implementação em Go de um servidor Model Context Protocol (MCP) que serve arquivos Markdown com suporte a frontmatter a partir de um sistema de arquivos.

bps-webapi-mcp

Enables AI assistants to access official Indonesian statistical data (BPS) through MCP, providing tools for dynamic data queries, foreign trade, publications, and more.

Fed Speech MCP

Retrieves, parses, and analyzes speeches and testimonies from Federal Reserve officers, enabling searches by speaker, topic, and keyword with automatic RSS feed discovery and intelligent relevance scoring.

Reddit MCP Server

Enables read-only access to Reddit for searching posts within specific subreddits using OAuth2 authentication. It allows users to search by query and sort results by relevance, popularity, or date.

MCP Servers Search

Enables discovery and querying of available MCP servers from the official repository. Supports searching by name, description, features, categories, and provides random server suggestions for exploration.

portaljs-mcp-server

A remote MCP server deployed on Cloudflare Workers without authentication, enabling tools via SSE for use with AI playgrounds and desktop clients.

Mini+ Agent Kit MCP Server

Enables driving a BitRobot-compatible ground robot (e.g., Earth Rover Mini+ or Waveshare UGV) through high-level verbs like move, turn, look, and capture work, with optional on-chain recording of verifiable robotic work.

Bink MCP Server

Enables AI agents to perform blockchain operations like wallet management, token info, DeFi swaps, cross-chain bridging, and price checking across Ethereum, BNB Chain, and Solana.

agentfi-mcp-server

DeFi execution and agent-to-agent economy tools for AI agents — swaps, yield, transfers, policy enforcement, trust scoring, A2A jobs, and P\&L across Ethereum, Base, Arbitrum, and Polygon.

Harvest MCP Server

Provides MCP integration for Harvest's time tracking, project management, and invoicing functionality, enabling natural language interaction with Harvest API through tools for managing clients, time entries, projects, tasks, and users.

axiom8-mcp

AI-powered n8n documentation server that enables intelligent semantic search and retrieval of node configurations, workflows, and templates for AI assistants.

getterdone-mcp-server

Enables AI agents to post tasks, manage escrow, approve work, and pay human gig workers on the GetterDone physical-task marketplace.

SkyeNet-MCP-ACE

Enables AI agents to execute server-side JavaScript and perform CRUD operations directly on ServiceNow instances with context bloat reduction features for efficient token usage.

rxjs-mcp-server

Execute, debug, and visualize RxJS streams directly from AI assistants like Claude.

google-calendar-mcp-server

Enables interaction with Google Calendar via MCP, allowing users to list, get, search, and create events as well as list accessible calendars.

VOICEVOX MCP Server

Enables Claude Desktop and Claude Code to synthesize and play speech using VOICEVOX text-to-speech engine. Supports multiple voice characters, session-based voice assignment, and queue management for audio playback.