Discover Awesome MCP Servers

Extend your agent with 84,517 capabilities via MCP servers.

All84,517
Electron MCP Server

Electron MCP Server

A Model Context Protocol server that provides comprehensive Electron application automation, debugging, and observability capabilities through Chrome DevTools Protocol integration.

MCP OAuth Server

MCP OAuth Server

A production-ready MCP server with OAuth 2.1 and PKCE for secure third-party API access, featuring GitHub user info retrieval and LLM-powered code analysis.

Smithsonian Open Access MCP Server

Smithsonian Open Access MCP Server

Provides AI assistants with access to search, explore, and analyze over 3 million collection objects from the Smithsonian Institution's museums. Enables finding objects currently on exhibit, retrieving detailed metadata, high-resolution images, and 3D models from America's national museums.

Slack MCP Server

Slack MCP Server

Enables complete Slack integration through natural language in Cursor IDE, supporting message sending, channel management, direct messaging, user lookup, reactions, and message search using the Slack API.

contrastapi

contrastapi

Security intelligence API for AI models. CVE lookup with EPSS/KEV, domain recon (DNS, WHOIS, SSL, subdomains, WAF), and code security checks (secrets, injection, headers). 16 tools, no API key required.

Postgres MCP Server

Postgres MCP Server

Enables comprehensive PostgreSQL database management through natural language including queries, schema operations, user management, and administrative tasks. Features enterprise-grade connection pooling, transaction support, and full database administration capabilities.

WorkOS MCP Server

WorkOS MCP Server

MCP server for WorkOS User Management API. Enables Claude to manage users, organizations, memberships, invitations, and sessions in WorkOS.

mcp-tool-filter

mcp-tool-filter

A generic MCP proxy that filters which tools are exposed from a remote MCP server, reducing context window token usage by only loading the tools you actually need.

Benin OpenData MCP

Benin OpenData MCP

MCP server to navigate and consume public data from Benin's OpenData portal.

RedTeam MCP

RedTeam MCP

Autonomous penetration testing powered by a local LLM, automating tool chaining for recon, vulnerability scanning, exploit research, and reporting.

Order Status Server

Order Status Server

Laravel MCP server that provides a tool to look up order status by order ID from a MySQL database.

FastAPI MCP Server

FastAPI MCP Server

Wraps FastAPI REST endpoints as MCP tools, enabling natural language interaction with user management, task management, and mathematical calculations through Gemini CLI.

JSer.info MCP Server

JSer.info MCP Server

A Model Context Protocol server that provides search and retrieval capabilities for JSer.info's JavaScript resource database, enabling access to items, posts, product information, and timeline data through various specialized tools.

Dental Clinic Loan Verification MCP Server

Dental Clinic Loan Verification MCP Server

Enables automated dental clinic loan verification by combining rule-based ID validation with LLM-powered document analysis and fraud detection. It supports provider-agnostic vision and reasoning tools to assess document consistency, verify credentials like PAN and GST, and generate comprehensive risk narratives.

MCP

MCP

Okay, I understand. You want to set up your MCP (presumably a custom application or system) to display company information and stock prices, leveraging the Claude model (likely for natural language processing or data retrieval). Here's a breakdown of the steps and considerations, along with a conceptual outline. Keep in mind that the specific implementation will depend heavily on the architecture of your MCP system and the available APIs for Claude and financial data. **Conceptual Outline** 1. **Data Sources:** * **Company Information:** Identify a reliable source of company information. This could be a database you maintain, a commercial API (e.g., Crunchbase, Clearbit), or a web scraping solution (less reliable but sometimes necessary). * **Stock Prices:** Choose a stock market data provider. Popular options include: * **IEX Cloud:** Relatively affordable and easy to use. * **Alpha Vantage:** Offers a free tier with limitations. * **Financial Modeling Prep:** Another option with various data points. * **Refinitiv (formerly Thomson Reuters):** More expensive but provides comprehensive data. * **Bloomberg:** High-end, professional-grade data. * **Claude API:** You'll need access to the Claude API. This usually involves signing up for an account and obtaining an API key. 2. **MCP System Integration:** * **API Endpoints:** Design API endpoints within your MCP system to handle requests for company information and stock prices. For example: * `/company/{company_name}`: Returns company details. * `/stock/{ticker_symbol}`: Returns stock price information. * **Data Storage (Optional):** Consider caching frequently accessed data in a database within your MCP system to reduce API calls to external services and improve response times. 3. **Claude Integration:** * **Natural Language Understanding (NLU):** Use Claude to understand user queries. For example, if a user types "Tell me about Apple's stock," Claude should identify the intent ("get stock information") and the entity ("Apple"). * **Data Retrieval:** Based on the NLU results, construct the appropriate API calls to your data sources (company information and stock price APIs). * **Response Formatting:** Use Claude to format the retrieved data into a human-readable response. This is where Claude's natural language generation (NLG) capabilities shine. 4. **Error Handling:** * Implement robust error handling to gracefully handle API failures, invalid user input, and other potential issues. **Detailed Steps and Considerations** 1. **Choose Your Data Sources:** * **Company Information:** * **API:** If you choose an API, review its documentation to understand how to query for company information (e.g., by name, ticker symbol, or domain). Consider the API's rate limits and pricing. * **Database:** If you have a database, ensure it's well-structured and indexed for efficient querying. * **Web Scraping:** Use a library like Beautiful Soup (Python) or Cheerio (Node.js) to scrape data from websites. Be aware of the legal and ethical implications of web scraping. Websites can change their structure, breaking your scraper. * **Stock Prices:** * **API:** Select a stock market data API based on your budget and data requirements. Pay attention to: * **Real-time vs. Delayed Data:** Real-time data is more expensive. Delayed data (e.g., 15-minute delay) may be sufficient for some use cases. * **Historical Data:** If you need historical stock prices, ensure the API provides it. * **API Limits:** Understand the API's rate limits and usage restrictions. 2. **Set Up Your MCP API Endpoints:** * Use a framework like Flask (Python), Express.js (Node.js), or Spring Boot (Java) to create your API endpoints. * Implement authentication and authorization if necessary to protect your API. * Use a consistent API design (e.g., RESTful principles). 3. **Integrate with Claude:** * **Install the Claude API client:** Follow the instructions in the Claude API documentation to install the appropriate client library for your programming language. * **Authentication:** Use your Claude API key to authenticate your requests. * **NLU (Natural Language Understanding):** * Send the user's query to the Claude API. * Use Claude's NLU capabilities to extract the intent and entities. You might need to fine-tune Claude for your specific use case. Consider using prompt engineering to guide Claude's understanding. For example: ```python import anthropic client = anthropic.Anthropic(api_key="YOUR_ANTHROPIC_API_KEY") def get_intent_and_entities(query): prompt = f"""You are a helpful assistant that analyzes user queries to determine their intent and extract relevant entities. User Query: {query} Intent: (The user's goal, e.g., "get stock information", "get company details") Entities: (A list of relevant entities, e.g., "Apple", "AAPL") """ response = client.completions.create( model="claude-v1.3", # Or the latest Claude model prompt=prompt, max_tokens_to_sample=200, ) # Parse the response to extract the intent and entities. This will require some string manipulation. # You might want to use regular expressions to make this easier. # Example: # intent = response.completion.split("Intent: ")[1].split("\n")[0].strip() # entities = response.completion.split("Entities: ")[1].split("\n")[0].strip().split(", ") # Return the intent and entities return intent, entities ``` * **Data Retrieval:** * Based on the extracted intent and entities, construct the appropriate API calls to your data sources. * Handle potential errors from the data source APIs. * **Response Formatting (NLG - Natural Language Generation):** * Use Claude to format the retrieved data into a human-readable response. Again, prompt engineering is crucial here. For example: ```python def format_response(company_name, stock_price, company_description): prompt = f"""You are a helpful assistant that formats company information and stock prices into a human-readable response. Company Name: {company_name} Stock Price: {stock_price} Company Description: {company_description} Response: """ response = client.completions.create( model="claude-v1.3", # Or the latest Claude model prompt=prompt, max_tokens_to_sample=300, ) return response.completion ``` 4. **Error Handling:** * Implement `try...except` blocks (Python) or similar error handling mechanisms in your code. * Log errors to a file or monitoring system for debugging. * Return informative error messages to the user. **Example Code Snippet (Conceptual - Python with Flask)** ```python from flask import Flask, request, jsonify import anthropic import requests # For making API calls to data sources app = Flask(__name__) # Replace with your actual API keys and data source URLs CLAUDE_API_KEY = "YOUR_CLAUDE_API_KEY" STOCK_API_URL = "https://api.example.com/stock/{ticker}" # Example COMPANY_API_URL = "https://api.example.com/company/{name}" # Example client = anthropic.Anthropic(api_key=CLAUDE_API_KEY) def get_intent_and_entities(query): # (Implementation as described above) # This is a placeholder. You'll need to parse the Claude response. if "stock" in query.lower(): intent = "get stock information" entity = query.split("stock of ")[-1].strip() # Very basic example elif "company" in query.lower(): intent = "get company information" entity = query.split("about ")[-1].strip() # Very basic example else: intent = "unknown" entity = None return intent, entity def get_stock_price(ticker): try: response = requests.get(STOCK_API_URL.format(ticker=ticker)) response.raise_for_status() # Raise HTTPError for bad responses (4xx or 5xx) data = response.json() return data["price"] except requests.exceptions.RequestException as e: print(f"Error fetching stock price: {e}") return None def get_company_description(company_name): try: response = requests.get(COMPANY_API_URL.format(name=company_name)) response.raise_for_status() data = response.json() return data["description"] except requests.exceptions.RequestException as e: print(f"Error fetching company description: {e}") return None def format_response(company_name, stock_price, company_description): # (Implementation as described above) prompt = f"""You are a helpful assistant that formats company information and stock prices into a human-readable response. Company Name: {company_name} Stock Price: {stock_price} Company Description: {company_description} Response: """ response = client.completions.create( model="claude-v1.3", # Or the latest Claude model prompt=prompt, max_tokens_to_sample=300, ) return response.completion @app.route("/query", methods=["POST"]) def handle_query(): query = request.json.get("query") if not query: return jsonify({"error": "Missing query parameter"}), 400 intent, entity = get_intent_and_entities(query) if intent == "get stock information": stock_price = get_stock_price(entity) if stock_price is None: return jsonify({"error": "Could not retrieve stock price"}), 500 company_description = get_company_description(entity) # Try to get company description too if company_description is None: company_description = "No description available." formatted_response = format_response(entity, stock_price, company_description) return jsonify({"response": formatted_response}) elif intent == "get company information": company_description = get_company_description(entity) if company_description is None: return jsonify({"error": "Could not retrieve company information"}), 500 formatted_response = format_response(entity, "N/A", company_description) # Stock price not applicable return jsonify({"response": formatted_response}) else: return jsonify({"error": "Unknown intent"}), 400 if __name__ == "__main__": app.run(debug=True) ``` **Key Improvements and Considerations:** * **Prompt Engineering:** The quality of Claude's responses depends heavily on the prompts you provide. Experiment with different prompts to optimize the results. Consider using few-shot learning (providing examples in the prompt) to guide Claude's behavior. * **Error Handling:** The example code includes basic error handling, but you should implement more robust error handling in a production environment. * **API Rate Limits:** Be mindful of the API rate limits of your data sources and the Claude API. Implement caching and rate limiting in your MCP system to avoid exceeding these limits. * **Security:** Protect your API keys and other sensitive information. Use environment variables to store API keys and avoid hardcoding them in your code. * **Scalability:** Consider the scalability of your MCP system. If you expect a large number of requests, you may need to use a load balancer and multiple servers. * **Testing:** Thoroughly test your MCP system to ensure it is working correctly. Write unit tests and integration tests to verify the functionality of your code. * **Monitoring:** Monitor your MCP system to identify and resolve issues quickly. Use a monitoring tool to track API response times, error rates, and other metrics. * **Data Validation:** Validate the data returned from the APIs to ensure it is accurate and consistent. * **Asynchronous Operations:** For long-running tasks (like calling external APIs), consider using asynchronous operations (e.g., with `asyncio` in Python) to improve the responsiveness of your MCP system. * **User Interface:** Consider how users will interact with your MCP system. You may want to create a web interface or a command-line interface. **Summary** This is a complex project that requires careful planning and execution. Start with a simple prototype and gradually add more features. Focus on the core functionality first (data retrieval and response formatting) and then add more advanced features like error handling, caching, and rate limiting. Remember to consult the documentation for the Claude API and your chosen data source APIs. Good luck!

uk-gazette

uk-gazette

Enables querying official UK public records from The Gazette, including insolvencies, winding-up petitions, and deceased estates.

rubberduck-mcp

rubberduck-mcp

Bridges AI assistants with Rubberduck VBA to enable code analysis, module management, and Git operations on VBA projects.

sap-bdc-mcp

sap-bdc-mcp

Enables AI agents to safely discover and validate SAP Business Data Cloud contracts (ORD, CSN, share plans) with enterprise guardrails like redaction and read-only defaults.

power_defect_analysis_mcp

power_defect_analysis_mcp

Enables querying and analysis of thermal power plant defects and work orders through fixed, parameterized SQL tools. Provides 8 core tools plus extensions for equipment search, defect/work order details, summaries, and failure analysis, with strict data boundaries and security.

MCP SQL Server

MCP SQL Server

An MCP server for Microsoft SQL Server integration that enables users to query, monitor, and analyze databases directly through Claude. It supports schema exploration, performance analysis, and optional write operations via natural language commands.

Agent Nudge

Agent Nudge

A local-first MCP server for AI coding agents that shares structured execution state, routes context deltas, and provides preflight nudges to prevent conflicts and stale decisions.

Mnemo Cortex

Mnemo Cortex

Persistent semantic memory for AI agents — hybrid SQLite + FTS5 with DAG-based summaries, context compaction, and 7 MCP tools. Open source, self-hosted, zero API cost.

legacy-mongodb-mcp

legacy-mongodb-mcp

Provides read-only access to legacy MongoDB instances (<4.0) via the Model Context Protocol, enabling AI models to query databases, collections, and run aggregations safely.

GSC MCP Worker

GSC MCP Worker

MCP server for Google Search Console, providing tools for site properties, search analytics, URL inspection, sitemaps, and audit reports.

MCP Store Greeting Server

MCP Store Greeting Server

Provides personalized store greetings combined with real-time weather information based on store location. Includes an admin web interface for managing stores with address autocomplete and map-based location selection.

jimeng-web-mcp

jimeng-web-mcp

Provides direct access to Jimeng AI's web interface for generating images and videos, supporting features like multi-image generation, video creation with frame control, and batch operations using free daily credits.

gh-board-mcp

gh-board-mcp

Manages GitHub Projects v2 as a personal kanban board, allowing you to create, move, and prioritize draft items without linking to real issues.

SEFAZ ES DEC: Caixa Postal

SEFAZ ES DEC: Caixa Postal

Enables querying the SEFAZ ES DEC postal mailbox from official sources via a single MCP tool.

ActionsPulse

ActionsPulse

Real-time GitHub Actions observability through VS Code with GitHub Copilot, providing DevOps metrics and interactive dashboards.

mod-dev-mcp

mod-dev-mcp

A development tooling MCP server for tModLoader mod projects, enabling building, formatting, and log tailing operations directly from an MCP client.