サーバーを起動する

Created By
irep-jumpei-usuia year ago
Overview

what is mcp-server-test?

The mcp-server-test project is a Docker-based server setup that allows users to easily build and run a server environment.

how to use mcp-server-test?

To use mcp-server-test, you need to build the Docker image using the provided command and then run the server with the specified port mapping.

key features of mcp-server-test?

  • Simple Docker setup for server management
  • Easy to use commands for building and running the server
  • Lightweight and efficient server environment

use cases of mcp-server-test?

  1. Quickly setting up a development server for testing applications.
  2. Running isolated server environments for different projects.
  3. Simplifying the deployment process for server applications.

FAQ from mcp-server-test?

  • What is required to run mcp-server-test?

You need to have Docker installed on your machine to build and run the server.

  • Can I customize the server configuration?

Yes! You can modify the Dockerfile and other configurations as needed.

  • Is mcp-server-test suitable for production use?

This project is primarily designed for development and testing purposes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
irep-jumpei-usui
Star
0
Language
Python
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