Awesome Remote MCP Servers

Created By
sylviangtha year ago
A curated list of Hosted & Managed Model Context Protocol (MCP) Servers accessible via a simple URL endpoint.
Overview

What is Awesome Remote MCP Servers?

Awesome Remote MCP Servers is a curated list of hosted and managed Model Context Protocol (MCP) servers that can be accessed via a simple URL endpoint, enabling seamless integration of AI applications with external tools and data.

How to use Awesome Remote MCP Servers?

Users can access the list of MCP servers by visiting the GitHub repository and selecting a server that fits their needs. Each server provides a unique URL and instructions for integration.

Key features of Awesome Remote MCP Servers?

  • Curated list of reliable MCP servers for AI applications
  • Zero setup required; connect instantly with just a URL
  • Managed infrastructure for reliability and scalability
  • Easy integration with various tools and services
  • Accessibility for non-technical users

Use cases of Awesome Remote MCP Servers?

  1. Integrating AI applications with cloud platforms like Zapier and Make.
  2. Enhancing data processing and analytics capabilities.
  3. Facilitating communication and collaboration through tools like Asana and Intercom.

FAQ from Awesome Remote MCP Servers?

  • What is the Model Context Protocol (MCP)?

MCP allows AI applications to connect to external tools and data for real-world tasks.

  • Are these servers free to use?

The repository lists various servers, some of which may have associated costs depending on the provider.

  • How do I contribute to this repository?

Contributions are welcome! Please refer to the CONTRIBUTING.md file in the repository for guidelines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sylviangth
Star
11
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago