Example MCP Server built on Next.js

Created By
cs-flytbasea year ago
Overview

what is MCP Server?

MCP Server is an example server built on Next.js that allows developers to create and manage Model Context Protocol (MCP) applications.

how to use MCP Server?

To use MCP Server, update the app/mcp.ts file with your tools, prompts, and resources according to the MCP TypeScript SDK documentation.

key features of MCP Server?

  • Built on Next.js for modern web applications
  • Supports integration with Redis for data management
  • Fluid compute for efficient execution on Vercel
  • Sample client provided for testing invocations

use cases of MCP Server?

  1. Building scalable web applications using the Model Context Protocol.
  2. Integrating real-time data processing with Redis.
  3. Deploying applications on Vercel with optimized performance.

FAQ from MCP Server?

  • What is required to run MCP Server?

You need to attach a Redis instance and enable Fluid compute on Vercel for optimal performance.

  • Is there a sample client available?

Yes! A sample client is included in the repository to help you test invocations.

  • Can I deploy MCP Server on Vercel?

Yes! You can deploy the Next.js MCP template on Vercel easily.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cs-flytbase
Star
0
Language
TypeScript
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