MCP example Netlify Express

Created By
srikaran7a year ago
Overview

what is MCP-SERVER?

MCP-SERVER is an example project demonstrating how to develop and run a serverless Model Context Protocol (MCP) using Netlify Functions.

how to use MCP-SERVER?

To use MCP-SERVER, you can deploy your own version by clicking the 'Deploy to Netlify' button, which will clone the example repository and set up an automated deployment pipeline. You can also run the examples locally by cloning the repository and using the Netlify CLI.

key features of MCP-SERVER?

  • Demonstrates serverless function deployment using Netlify.
  • Provides a customizable URL for accessing the serverless function.
  • Includes a simple setup for local development and testing.

use cases of MCP-SERVER?

  1. Learning how to implement serverless functions with Netlify.
  2. Developing applications that utilize the Model Context Protocol.
  3. Testing and iterating on serverless applications locally.

FAQ from MCP-SERVER?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol designed to facilitate the interaction between different models and agents in a serverless environment.

  • Is there a demo available for MCP-SERVER?

Yes! You can view the demo site at https://mcp-example-express.netlify.app/.

  • How can I run the examples locally?

You can clone the repository and follow the provided instructions to run the examples using the Netlify CLI.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
srikaran7
Star
0
Language
HTML
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)

20 hours ago
Gpt Scrambler

2 days ago