team-evolve-http-mcpserver

Created By
qianping-saraa year ago
Overview

what is team-evolve-http-mcpserver?

team-evolve-http-mcpserver is a Model Context Protocol (MCP) server built with the mcp-framework, designed to facilitate the development and integration of various tools within a server environment.

how to use team-evolve-http-mcpserver?

To use the server, install the dependencies using npm install, build the project with npm run build, and configure it with your Claude Desktop client for local development or after publishing.

key features of team-evolve-http-mcpserver?

  • Easy tool integration through a CLI interface.
  • Example tool provided for quick start.
  • Supports local development and publishing to npm.
  • Automatic loading of tools on server startup.

use cases of team-evolve-http-mcpserver?

  1. Developing custom tools for data processing.
  2. Creating API clients for various services.
  3. Handling file operations through custom handlers.

FAQ from team-evolve-http-mcpserver?

  • How do I add a new tool?

Use the command mcp add tool my-tool to create a new tool.

  • Can I publish my tools?

Yes! After building your tool, you can publish it to npm for others to use.

  • What is the project structure like?

The project includes a src directory with tools and an entry point for the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
qianping-sara
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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