Discover Awesome MCP Servers

Canvas Assignment Assistant

Enables interaction with Canvas LMS courses and assignments directly from your LLM, allowing you to retrieve, search, and summarize course information, check due dates, and access assignment details without leaving your AI assistant.

MCP MGit Server

Enables executing mgit push operations to manage and synchronize multiple Git repositories with batch commit and push capabilities. Supports multiple instances with repository isolation and operation logging.

Enterprise AI Toolkit MCP

An enterprise MCP server that exposes 16 standardized tools for document intelligence, RAG, knowledge graph, SQL analysis, LLM evaluation, cost estimation, and AI architecture design, enabling AI agents to securely access and compose enterprise AI capabilities.

App Store Connect Server

一个 MCP 服务器，用于与 App Store Connect API 通信，为 iOS 开发者服务。

Ask Samin

Enables users to search Samin Yasar's video library and receive full-video recommendations grounded in transcript evidence with links to exact matched caption cues.

dev-browser-mcp

Enables AI agents to control a persistent Chromium browser or attach to an existing Chrome with sandboxed JavaScript and structured tools for web interaction and automation.

TypeScript Prompt MCP Server

Okay, I understand. Here are some pre-defined prompt templates you can use for AI assistants to generate comprehensive plans for TypeScript projects, API architectures, and GitHub workflows. I've included variations and options to make them more flexible. **1. TypeScript Project Plan:** * **Template 1 (General):** ``` Create a comprehensive plan for a TypeScript project named "[Project Name]" that aims to [briefly describe the project's purpose]. The plan should include: * **Project Goals and Objectives:** Clearly defined goals and measurable objectives. * **Technology Stack:** Recommended libraries, frameworks, and tools (e.g., React, Angular, Node.js, Express, testing frameworks, linting tools). Justify each choice. * **Project Structure:** A proposed directory structure and module organization. * **Coding Standards and Conventions:** Guidelines for code style, naming conventions, and documentation. * **Testing Strategy:** A plan for unit, integration, and end-to-end testing. Specify testing frameworks and methodologies. * **Build and Deployment Process:** Steps for building, packaging, and deploying the application. Include CI/CD considerations. * **Dependencies Management:** How dependencies will be managed (e.g., npm, yarn, pnpm). * **Error Handling and Logging:** Strategies for handling errors and logging information. * **Security Considerations:** Potential security vulnerabilities and mitigation strategies. * **Scalability Considerations:** How the application can be scaled to handle increased load. * **Future Enhancements:** Potential future features or improvements. * **Initial Setup Instructions:** Step-by-step instructions for setting up the development environment. The target audience for this project is [describe the target audience, e.g., small businesses, individual users, enterprise clients]. The project should be [describe desired qualities, e.g., maintainable, scalable, performant, secure]. ``` * **Template 2 (Specific Framework):** ``` Develop a detailed plan for a TypeScript project using [Framework Name] (e.g., React, Angular, NestJS) to build [briefly describe the application]. The plan should cover: * **Project Goals and Objectives:** Clearly defined goals and measurable objectives. * **Framework-Specific Architecture:** How to leverage [Framework Name]'s architecture (e.g., components, services, modules) for this project. * **State Management:** Recommended state management solution (e.g., Redux, Zustand, Context API) and justification. * **Routing:** How routing will be implemented (e.g., React Router, Angular Router). * **Data Fetching:** Strategies for fetching data from APIs (e.g., Axios, Fetch API, GraphQL). * **UI Component Library:** Recommended UI component library (e.g., Material UI, Ant Design, Chakra UI) and justification. * **Testing Strategy:** A plan for unit, integration, and end-to-end testing, specific to [Framework Name]. Specify testing frameworks and methodologies (e.g., Jest, Cypress, Testing Library). * **Build and Deployment Process:** Steps for building, packaging, and deploying the application, optimized for [Framework Name]. Include CI/CD considerations. * **Dependencies Management:** How dependencies will be managed (e.g., npm, yarn, pnpm). * **Error Handling and Logging:** Strategies for handling errors and logging information. * **Security Considerations:** Potential security vulnerabilities and mitigation strategies. * **Scalability Considerations:** How the application can be scaled to handle increased load. * **Future Enhancements:** Potential future features or improvements. * **Initial Setup Instructions:** Step-by-step instructions for setting up the development environment. The target audience for this project is [describe the target audience, e.g., small businesses, individual users, enterprise clients]. The project should be [describe desired qualities, e.g., maintainable, scalable, performant, secure]. ``` * **Template 3 (Backend API):** ``` Create a comprehensive plan for a TypeScript backend API project named "[API Name]" that will [briefly describe the API's purpose]. The plan should include: * **API Goals and Objectives:** Clearly defined goals and measurable objectives. * **Technology Stack:** Recommended libraries, frameworks, and tools (e.g., Node.js, Express, NestJS, database, ORM, testing frameworks, linting tools). Justify each choice. * **API Architecture:** A proposed architecture (e.g., REST, GraphQL, gRPC). Explain the chosen architecture's benefits for this project. * **Database Design:** A high-level database schema and data model. Specify the database technology (e.g., PostgreSQL, MongoDB, MySQL). * **Authentication and Authorization:** A plan for securing the API, including authentication and authorization mechanisms (e.g., JWT, OAuth). * **API Documentation:** How the API will be documented (e.g., OpenAPI/Swagger). * **Error Handling and Logging:** Strategies for handling errors and logging information. * **Testing Strategy:** A plan for unit, integration, and end-to-end testing. Specify testing frameworks and methodologies. * **Build and Deployment Process:** Steps for building, packaging, and deploying the API. Include CI/CD considerations. * **Dependencies Management:** How dependencies will be managed (e.g., npm, yarn, pnpm). * **Security Considerations:** Potential security vulnerabilities and mitigation strategies (e.g., input validation, rate limiting). * **Scalability Considerations:** How the API can be scaled to handle increased load (e.g., load balancing, caching). * **Rate Limiting:** A strategy for rate limiting API requests. * **Monitoring and Alerting:** How the API will be monitored and how alerts will be generated. * **Future Enhancements:** Potential future features or improvements. * **Initial Setup Instructions:** Step-by-step instructions for setting up the development environment. The API will be consumed by [describe the consumers of the API, e.g., web applications, mobile apps, other APIs]. The API should be [describe desired qualities, e.g., performant, secure, reliable, well-documented]. ``` **2. API Architecture Plan:** * **Template 1 (General):** ``` Design a robust and scalable API architecture for [briefly describe the application or system the API will support]. The architecture should address the following requirements: * **API Style:** Choose an appropriate API style (e.g., REST, GraphQL, gRPC) and justify the choice based on the project's needs. * **Data Format:** Specify the data format (e.g., JSON, XML, Protocol Buffers). * **Authentication and Authorization:** Describe the authentication and authorization mechanisms (e.g., JWT, OAuth, API keys). Consider different user roles and permissions. * **Rate Limiting:** Implement a rate limiting strategy to prevent abuse and ensure fair usage. * **Versioning:** Plan for API versioning to allow for future changes without breaking existing clients. * **Error Handling:** Define a consistent error handling strategy, including error codes and messages. * **Documentation:** Specify how the API will be documented (e.g., OpenAPI/Swagger, Postman collections). * **Caching:** Implement caching strategies to improve performance and reduce load on the backend. * **Security:** Address common security vulnerabilities, such as injection attacks, cross-site scripting (XSS), and cross-site request forgery (CSRF). * **Scalability:** Design the architecture to be scalable to handle increasing traffic and data volume. Consider load balancing, horizontal scaling, and database optimization. * **Monitoring and Logging:** Implement monitoring and logging to track API performance and identify potential issues. * **Deployment:** Describe the deployment strategy (e.g., cloud-based, on-premise). * **Technology Stack:** Recommend specific technologies and tools for implementing the API (e.g., Node.js, Express, NestJS, databases, message queues). The API will be used by [describe the consumers of the API]. The key performance indicators (KPIs) for the API are [list the KPIs, e.g., response time, error rate, throughput]. ``` * **Template 2 (Microservices):** ``` Design a microservices-based API architecture for [briefly describe the application or system]. The architecture should address the following: * **Service Decomposition:** Identify the key services and their responsibilities. Explain the rationale behind the service decomposition. * **Communication:** Specify the communication protocols between services (e.g., REST, gRPC, message queues). Justify the choice. * **Service Discovery:** Implement a service discovery mechanism to allow services to locate each other. * **API Gateway:** Design an API gateway to handle external requests and route them to the appropriate services. * **Authentication and Authorization:** Implement authentication and authorization across the microservices. * **Data Management:** Describe how data will be managed across the microservices. Consider data consistency and eventual consistency. * **Monitoring and Logging:** Implement centralized monitoring and logging for all microservices. * **Deployment:** Describe the deployment strategy for the microservices (e.g., containers, Kubernetes). * **Fault Tolerance:** Design the architecture to be fault-tolerant and resilient to failures. * **Technology Stack:** Recommend specific technologies and tools for implementing the microservices (e.g., Docker, Kubernetes, message queues, databases). The system will handle [describe the scale and complexity of the system]. The key challenges in this architecture are [list the key challenges, e.g., data consistency, distributed tracing, security]. ``` **3. GitHub Workflow Plan:** * **Template 1 (General):** ``` Create a GitHub workflow plan for a [TypeScript/JavaScript/Python/etc.] project named "[Project Name]". The plan should include: * **Branching Strategy:** Define a branching strategy (e.g., Gitflow, GitHub Flow, Trunk-Based Development). Explain the rationale behind the chosen strategy. * **Pull Request Process:** Describe the pull request process, including code review guidelines and approval requirements. * **Continuous Integration (CI):** Implement CI to automatically build, test, and lint the code on every pull request and push. Specify the CI tools (e.g., GitHub Actions, Jenkins, CircleCI). * **Automated Testing:** Integrate automated testing into the CI pipeline. Specify the testing frameworks and types of tests (e.g., unit tests, integration tests, end-to-end tests). * **Code Linting and Formatting:** Enforce code style and formatting using linters and formatters (e.g., ESLint, Prettier). * **Code Coverage:** Track code coverage to ensure adequate test coverage. * **Continuous Deployment (CD):** Implement CD to automatically deploy the application to production after successful CI. Specify the deployment environment and strategy. * **Release Management:** Define a release management process, including versioning and tagging. * **Issue Tracking:** Use GitHub Issues to track bugs, features, and tasks. * **Security Scanning:** Integrate security scanning tools to identify vulnerabilities in the code and dependencies. * **Documentation Generation:** Automate the generation of documentation from the code. * **Dependency Management:** Automate dependency updates and vulnerability scanning. The project is [describe the project's size and complexity]. The goal of the workflow is to [describe the goals, e.g., improve code quality, automate deployments, reduce errors]. ``` * **Template 2 (GitHub Actions Specific):** ``` Design a GitHub Actions workflow for a [TypeScript/JavaScript/Python/etc.] project named "[Project Name]". The workflow should: * **Trigger:** Specify the triggers for the workflow (e.g., pull requests, pushes to main branch, scheduled events). * **Jobs:** Define the jobs in the workflow, including their dependencies and execution order. * **Steps:** Specify the steps in each job, including the commands to execute and the actions to use. * **Environment Variables:** Use environment variables to configure the workflow. * **Secrets:** Store sensitive information (e.g., API keys, passwords) as secrets. * **Caching:** Use caching to speed up the workflow. * **Artifacts:** Store build artifacts (e.g., compiled code, documentation) for later use. * **Notifications:** Send notifications on workflow completion or failure. * **Error Handling:** Implement error handling to gracefully handle failures. * **Specific Tasks:** Include steps for [list specific tasks, e.g., running unit tests, building the application, deploying to AWS, publishing to npm]. Provide a YAML configuration file for the GitHub Actions workflow. The project is [describe the project's size and complexity]. The goal of the workflow is to [describe the goals, e.g., automate deployments, improve code quality, reduce errors]. ``` **Key Considerations for Using These Templates:** * **Be Specific:** The more specific you are in your prompt, the better the results will be. Provide as much context as possible about the project, its goals, and its requirements. * **Iterate:** Don't expect the AI to generate the perfect plan on the first try. Review the output carefully and iterate on the prompt to refine the plan. * **Customize:** These are just templates. Customize them to fit the specific needs of your project. * **Review and Validate:** Always review and validate the AI-generated plan to ensure that it is accurate, complete, and feasible. Don't blindly trust the AI. * **Consider the AI's Limitations:** AI assistants are good at generating text, but they may not have a deep understanding of software development principles or best practices. Use your own expertise to evaluate the AI's suggestions. By using these templates and following these guidelines, you can effectively leverage AI assistants to generate comprehensive plans for your TypeScript projects, API architectures, and GitHub workflows. Good luck!

MCP Math Tools

Provides basic mathematical operations like addition, subtraction, multiplication, and division via the Model Context Protocol using stdio transport. This project serves as a complete reference implementation for a functional MCP server and client setup.

msteams-local-mcp

Reads the local Microsoft Teams (v2) message cache and exposes it over MCP, enabling AI assistants to list accounts/conversations and search/read messages without Graph API or network.

Hound Web Mcp

Hound MCP Servers Gives your agent actually good fetch + Search for 0$, no catch, no api keys or free tiers, fully free.

Tableau MCP Server

Enables interaction with Tableau Cloud and Tableau Server through the REST API, supporting workbook management, view queries, extract refreshes, and content search operations.

Zoho Timeline MCP Server

Enables Claude Desktop to interactively capture and analyze Zoho CRM timeline screenshots, automatically extracting timeline events, workflows, and functions through OCR and vision API, with export to JSON and Markdown formats.

nwc-mcp

MCP server exposing a Lightning wallet to LLM agents over Nostr Wallet Connect (NIP-47): balance, invoices, LN address/LNURL payments, batch pay, and keysend. All spend tools are wrapped in a defense-in-depth safety stack — budget caps, allowlist, two-step confirmation, audit log.

prts-mcp

Arknights PRTS Wiki MCP Server — queries the PRTS Wiki API for full-text search and article extraction, and serves auto-synced operator archives, voice lines, and story/event scripts from game data. Designed for fan-creation AI agents that need accurate lore, character profiles, and in-character dialogue references.

F4 Crash Doctor

Fallout 4 crash log diagnosis tool for MCP clients. Analyzes crash logs, load order, and game environment to explain crashes and suggest fixes.

mcp-foursquare

Enables place search and discovery via the Foursquare Places API v3, allowing AI assistants to find venues, search near locations, look up place details, and get location context.

Triplewhale MCP Server

Enables natural language queries to Triplewhale for analyzing marketing and financial metrics such as revenue, ROAS, and net profit.

Alibaba Cloud MCP Server

A server that provides access to Alibaba Cloud resources including ECS, VPC, and CloudMonitor through API and OOS implementations, enabling resource management and monitoring via a unified interface.

React Native Debugger MCP

一个 MCP 服务器，用于连接到你的 React Native 应用程序调试器。 (Yī gè MCP fúwùqì, yòng yú liánjiē dào nǐ de React Native yìngyòng chéngxù tiáoshì qì.)

Excel MCP Server

An MCP server for manipulating Excel files that features a headless engine for real-time formula calculation and data validation. It enables users to create, read, and manage workbooks, sheets, and charts without requiring Microsoft Excel installed.

voice-bridge

Multi-engine text-to-speech for AI coding assistants. Speaks responses aloud from Claude Code, Cursor, or VS Code via a Claude Code plugin, MCP server, or CLI pipe.

Zaxy

Zaxy turns agent work into durable, auditable memory: a hash-chained Eventloom log as the source of truth, an embedded temporal knowledge graph for reasoning (local-first, no sidecar; Neo4j/Postgres optional), cited Memory Checkout for compact context, and MCP tools for model-facing retrieval, capture, and feedback.

Fabric Ontology MCP Server

Enables full CRUD control of Ontology items in Microsoft Fabric, including entity types, relationships, data bindings, and workspace discovery through natural language.

AutoBuildMCP

A profile-based build automation server powered by MCP that manages, executes, and monitors build processes across multiple projects with features like build queuing, asynchronous execution, and file-watching for automatic rebuilds.

Solar MCP

An MCP server that enables AI assistants to look up solar permitting authorities, estimate solar production via PVWatts, and retrieve irradiance data. It streamlines the creation of solar-aware workflows by integrating industry-standard APIs like NREL.

mcp-agent-tool-adapter

使用现代 Agent 框架将 MCP 工具转换为协作式推理 Agent。

MCP Orquestrador

Advanced task automation system that reads codebases, divides complex tasks into specific steps, and rigorously executes them with complete testing, documentation, validation and automatic correction.

ae-meta-mcp

Lightweight MCP server for After Effects that enables Cursor Agent to execute ExtendScript code inside AE via a single tool, similar to Blender MCP.

semaphore-mcp

A curated MCP server for Semaphore UI that enables driving Ansible and Terraform automation from Claude with a safe, read-first tool surface.

Prompt Manager

通过简化的SOLID架构，实现提示词的创建、管理和模板化，允许用户按类别组织提示词，并在运行时填充模板。