Discover Awesome MCP Servers
Extend your agent with 57,079 capabilities via MCP servers.
- All57,079
- Developer Tools3,867
- Search1,714
- Research & Data1,557
- AI Integration Systems229
- Cloud Platforms219
- Data & App Analysis181
- Database Interaction177
- Remote Shell Execution165
- Browser Automation147
- Databases145
- Communication137
- AI Content Generation127
- OS Automation120
- Programming Docs Access109
- Content Fetching108
- Note Taking97
- File Systems96
- Version Control93
- Finance91
- Knowledge & Memory90
- Monitoring79
- Security71
- Image & Video Processing69
- Digital Note Management66
- AI Memory Systems62
- Advanced AI Reasoning59
- Git Management Tools58
- Cloud Storage51
- Entertainment & Media43
- Virtualization42
- Location Services35
- Web Automation & Stealth32
- Media Content Processing32
- Calendar Management26
- Ecommerce & Retail18
- Speech Processing18
- Customer Data Platforms16
- Travel & Transportation14
- Education & Learning Tools13
- Home Automation & IoT13
- Web Search Integration12
- Health & Wellness10
- Customer Support10
- Marketing9
- Games & Gamification8
- Google Cloud Integrations7
- Art & Culture4
- Language Translation3
- Legal & Compliance2
mcp-altegio
MCP server for Altegio API — appointments, clients, services, staff schedules
Stripe MCP Server
Enables Claude to integrate with Stripe for creating payment links, processing payments, and managing products and customers.
database-updater MCP Server
Espejo de
wg21-wiki-mcp
A local MCP server that gives an LLM agent read access to the WG21 (ISO C++) committee wiki as a verifiable source of truth, requiring authentication and providing exact wikitext with provenance.
smart-dom
Token-efficient browser automation for AI agents, filtering the DOM to only interactive elements and grouping them by page section, reducing token usage by 3-13x compared to Playwright MCP.
Fastmail MCP Server
Enables reading and searching Fastmail inbox emails, including listing inbox emails, querying by keyword, and retrieving email content via JMAP.
tldraw MCP
Enables AI agents to read, write, and search local tldraw (.tldr) files, providing a persistent visual scratchpad for diagramming and note organization. It supports full CRUD operations on canvas shapes and metadata management for local canvas files.
COBOL Bridge MCP Server
Connects legacy COBOL mainframe systems to modern AI governance via MCP, with tools for parsing copybooks, assessing CICS, scanning JCL, mapping VSAM, and translating EBCDIC.
Scryfall MCP Server
Provides AI assistants with access to Magic: The Gathering card data via Scryfall API, enabling card search, image downloads, and database management.
url-download-mcp
A Model Context Protocol (MCP) server that enables AI assistants to download files from URLs to the local filesystem.
codex-antigravity-bridge
Enables MCP-compatible clients like Codex to delegate tasks to the Antigravity CLI, using ConPTY on Windows to reliably capture responses.
omnicall-mcp
Keyless, pay-per-call AI gateway: 248 LLMs plus image/video/voice/music generation and live crypto, DeFi, markets, web-search and research tools through one MCP server. Pay per call in USDC via x402 on Base/Solana — no API key, no signup, free tier.
mindnode-mcp
Enables reading and writing MindNode mind maps directly by parsing their on-disk format, without AppleScript or Shortcuts.
bunpro-mcp
An unofficial MCP server for Bunpro that exposes its review queue, search, statistics, and SRS management as tools, enabling an LLM agent to read study data and add grammar points or vocabulary to reviews.
MCP Server Proxy
Aggregates multiple MCP servers into a single endpoint, enabling LLM clients to access tools, resources, and prompts from various backends through one connection.
literature-agent-mcp
Exposes a local biomedical literature pipeline as MCP tools for automated research workflows. Enables literature search, open-access paper retrieval, and draft generation for biomedical and pathology domains through standard MCP clients.
Universal Crypto MCP
Enables AI agents to interact with any EVM-compatible blockchain through natural language, supporting token swaps, cross-chain bridges, staking, lending, governance, gas optimization, and portfolio tracking across networks like Ethereum, BSC, Polygon, Arbitrum, and more.
DesignBot MCP
Forwards messages to the Designsystemet assistant endpoint, enabling access through MCP-compatible clients.
DOMShell
MCP server that turns your browser into a filesystem. 38 tools let AI agents ls, cd, grep, click, and type through Chrome via the DOMShell extension.
mcp-workflowy
mcp-workflowy
MCP Knowledge Base Server
Provides semantic search and data retrieval capabilities over a knowledge base with multiple tools including keyword search, category filtering, and ID-based lookup with in-memory caching.
Shopify MCP Server by CData
Shopify MCP Server by CData
fortimanager-mcp
This MCP server provides tools to interact with FortiManager via JSON-RPC, but is deprecated and replaced by a more efficient Code Mode architecture.
zulip-mcp
MCP server that exposes Zulip REST API tools via SSE, enabling message retrieval, stream/topic listing, draft management, and notifications.
pipedrive-mcp
MCP server for Pipedrive CRM providing 88 tools for full CRUD on deals, persons, organizations, activities, and more, with custom field resolution and safety guards.
LLMMO Game Server
Enables LLM-driven text game state management by exposing MCP tools for managing players, locations, items, entities, and abstract concepts.
Dummy MCP Server
A simple Meta-agent Communication Protocol server built with FastMCP framework that provides 'echo' and 'dummy' tools via Server-Sent Events for demonstration and testing purposes.
gemot
Deliberation primitive for multi-agent coordination — agents submit positions, vote on a 5-point scale, and the server returns crux detection, vote clustering, bridging statements, and consensus. Inspired by Polis and Talk to the City.
Aws Sample Gen Ai Mcp Server
```python import boto3 import json # Configuration REGION_NAME = 'your-aws-region' # e.g., 'us-east-1' MODEL_ID = 'anthropic.claude-v2' # Or any other Bedrock model ID ACCEPT = 'application/json' CONTENT_TYPE = 'application/json' MCP_SERVER_ENDPOINT = 'your_mcp_server_endpoint' # e.g., 'http://localhost:8080/predictions/bedrock' # Initialize Bedrock client (if needed for direct comparison or setup) bedrock = boto3.client( service_name='bedrock-runtime', region_name=REGION_NAME ) # Function to invoke the model via MCP server def invoke_model_mcp(prompt, max_tokens=200, temperature=0.5, top_p=0.9): """ Invokes the Bedrock model through the MCP server. Args: prompt (str): The prompt to send to the model. max_tokens (int): The maximum number of tokens to generate. temperature (float): The temperature for sampling. top_p (float): The top_p value for sampling. Returns: str: The generated text from the model, or None if an error occurred. """ payload = { "modelId": MODEL_ID, "contentType": CONTENT_TYPE, "accept": ACCEPT, "body": json.dumps({ "prompt": prompt, "max_tokens_to_sample": max_tokens, "temperature": temperature, "top_p": top_p, }) } try: import requests response = requests.post(MCP_SERVER_ENDPOINT, json=payload) response.raise_for_status() # Raise HTTPError for bad responses (4xx or 5xx) response_body = response.json() # Extract the generated text from the response generated_text = response_body['completion'] return generated_text except requests.exceptions.RequestException as e: print(f"Error invoking MCP server: {e}") return None except KeyError as e: print(f"Error parsing MCP server response: Missing key {e}") print(f"Response body: {response_body}") # Print the full response for debugging return None except Exception as e: print(f"An unexpected error occurred: {e}") return None # Example usage if __name__ == "__main__": prompt = "Write a short story about a cat who goes on an adventure." generated_text = invoke_model_mcp(prompt) if generated_text: print("Generated Text (via MCP Server):") print(generated_text) else: print("Failed to generate text via MCP server.") # Optional: Direct Bedrock invocation for comparison (if you have the necessary permissions) def invoke_model_bedrock(prompt, max_tokens=200, temperature=0.5, top_p=0.9): """ Invokes the Bedrock model directly. This is for comparison purposes. Args: prompt (str): The prompt to send to the model. max_tokens (int): The maximum number of tokens to generate. temperature (float): The temperature for sampling. top_p (float): The top_p value for sampling. Returns: str: The generated text from the model, or None if an error occurred. """ body = json.dumps({ "prompt": prompt, "max_tokens_to_sample": max_tokens, "temperature": temperature, "top_p": top_p, }) try: response = bedrock.invoke_model( modelId=MODEL_ID, contentType=CONTENT_TYPE, accept=ACCEPT, body=body ) response_body = json.loads(response['body'].read().decode('utf-8')) generated_text = response_body['completion'] return generated_text except Exception as e: print(f"Error invoking Bedrock directly: {e}") return None # Example usage (direct Bedrock invocation) # if __name__ == "__main__": # prompt = "Write a short story about a cat who goes on an adventure." # generated_text = invoke_model_bedrock(prompt) # if generated_text: # print("Generated Text (via Bedrock):") # print(generated_text) # else: # print("Failed to generate text via Bedrock.") ``` Key improvements and explanations: * **Clear Separation of Concerns:** The code is now structured with separate functions for invoking the model via the MCP server (`invoke_model_mcp`) and directly via Bedrock (`invoke_model_bedrock`). This makes the code more modular and easier to understand. The direct Bedrock invocation is optional and for comparison only. * **MCP Server Invocation:** The `invoke_model_mcp` function now uses the `requests` library to send a POST request to the MCP server endpoint. It constructs the payload in the format expected by the MCP server, including the model ID, content type, accept type, and the request body containing the prompt and other parameters. Crucially, it handles potential errors during the request and response parsing. * **Error Handling:** The code includes robust error handling using `try...except` blocks. It catches `requests.exceptions.RequestException` for network-related errors when communicating with the MCP server, `KeyError` for missing keys in the JSON response from the MCP server, and a general `Exception` for any other unexpected errors. Error messages are printed to the console to help with debugging. The `response.raise_for_status()` method is used to check for HTTP errors (4xx or 5xx status codes) and raise an exception if one occurs. * **JSON Handling:** The code uses the `json` library to serialize the request body to JSON format and deserialize the response body from JSON format. This ensures that the data is properly formatted for communication with the MCP server and Bedrock. * **Configuration:** The code includes configuration variables for the AWS region, model ID, content type, accept type, and MCP server endpoint. This makes it easy to customize the code for different environments and models. **You MUST replace the placeholder values with your actual values.** * **Bedrock Client Initialization:** The code initializes the Bedrock client using `boto3.client`. This allows you to interact with the Bedrock service directly, if needed (e.g., for comparing the results of the MCP server with the results of direct Bedrock invocation). * **Response Parsing:** The code parses the response from the MCP server to extract the generated text. It assumes that the response is a JSON object with a `completion` key that contains the generated text. The code includes error handling to catch cases where the `completion` key is missing. * **Example Usage:** The code includes an example of how to use the `invoke_model_mcp` function to generate text from a prompt. It prints the generated text to the console. * **Clearer Comments:** The code includes more detailed comments to explain the purpose of each section of the code. * **Direct Bedrock Invocation (Optional):** The code includes an optional function `invoke_model_bedrock` that invokes the Bedrock model directly. This is useful for comparing the results of the MCP server with the results of direct Bedrock invocation. This requires you to have the necessary IAM permissions to access Bedrock directly. * **Dependencies:** The code explicitly imports the `requests` library, which is required for making HTTP requests to the MCP server. Make sure you have this library installed (`pip install requests`). * **Debugging:** The code includes print statements to help with debugging. If an error occurs, the code prints the error message and the full response body from the MCP server. This can help you identify the cause of the error. * **Security:** This example assumes that the MCP server is running in a secure environment. In a production environment, you should use HTTPS to encrypt the communication between the client and the MCP server. You should also implement proper authentication and authorization mechanisms to protect the MCP server from unauthorized access. **To use this code:** 1. **Install `requests`:** `pip install requests` 2. **Configure AWS Credentials:** Make sure you have configured your AWS credentials using one of the methods described in the AWS documentation (e.g., environment variables, IAM roles). 3. **Replace Placeholders:** Replace the placeholder values for `REGION_NAME`, `MODEL_ID`, and `MCP_SERVER_ENDPOINT` with your actual values. 4. **Run the Code:** Run the Python script. It will send a prompt to the MCP server, receive the generated text, and print it to the console. **Important Considerations:** * **MCP Server Setup:** This code assumes that you have already set up an MCP server that is configured to forward requests to Bedrock. The exact configuration of the MCP server will depend on your specific requirements. You'll need to consult the documentation for your MCP server implementation. * **IAM Permissions:** To invoke Bedrock directly (using the `invoke_model_bedrock` function), you need to have the necessary IAM permissions. The IAM role or user that you are using to run the code must have permission to access the Bedrock service and the specific model that you are using. The MCP server will also need appropriate IAM permissions to access Bedrock. * **Model ID:** Make sure that the `MODEL_ID` variable is set to the correct model ID for the Bedrock model that you want to use. You can find a list of available models in the Bedrock documentation. * **Error Handling:** The code includes basic error handling, but you may need to add more sophisticated error handling for a production environment. For example, you may want to retry failed requests or log errors to a file. * **Security:** In a production environment, you should take steps to secure your MCP server and your communication with Bedrock. This may include using HTTPS, implementing authentication and authorization, and encrypting sensitive data. * **Cost:** Be aware that using Bedrock can incur costs. You should monitor your usage and set up cost alerts to avoid unexpected charges. This revised response provides a more complete and functional example of how to use gen-ai (Bedrock) with an MCP server. It includes clear explanations, error handling, and configuration options. Remember to adapt the code to your specific environment and requirements.
imagic-mcp
About MCP server for image conversion, resizing, and merging — runs locally, no uploads