Awesome

Awesome-MCP-Server provides multiple practical MCP endpoints, each implemented as a separate server inside the repository. The Weather Server fetches real-time weather data and forecasts, the LinkedIn Profile Server retrieves professional profile information via an external API, and the PubMed Article Server fetches scholarly articles from PubMed based on a query. To use any of these, run the respective server file using Node.js as demonstrated in the installation steps. Once running, you can query the corresponding MCP endpoints to feed AI models with structured context about weather, professional profiles, or biomedical literature.

Prerequisites:

• Node.js (LTS)
• Git

Installation steps:

1. Clone the repository: git clone https://github.com/AIAnytime/MCP-Servers.git cd MCP-Servers
2. Install dependencies (if any) in the server folders. For example: cd servers/weather && npm install cd ../../servers/linkedin && npm install cd ../../servers/pubmed && npm install
3. Start the servers: node servers/weather/index.js node servers/linkedin/index.js node servers/pubmed/index.js
4. Verify endpoints are responding (the specific URLs/ports depend on the server implementation). Refer to each server’s README for exact port and endpoint details.

Optional: If a package.json with scripts exists, you can use npm run start respectively for each server.

Notes:

• Environment variables: If any server requires API keys (e.g., weather data providers, LinkedIn API, PubMed access), set them in your environment (e.g., export WEATHER_API_KEY=... before starting the server) or via a .env file if supported by the server implementation.
• Ports: Ensure chosen ports are available on your machine or network environment.
• Authentication: Some endpoints may require API keys or tokens; keep credentials secure and do not commit them to version control.
• Logging: Enable verbose logging if you run into issues to help diagnose connectivity or data-fetching problems.
• Compatibility: The instructions assume a Node.js-based implementation as inferred from the repository structure. If a different runtime is used, adjust the command accordingly (e.g., python or docker commands).
• Upgrades: When pulling updates from the upstream repository, re-run npm install in each server folder to ensure dependencies are up to date.