Meta MCP Server

Created By
infinitimelessa year ago
A meta server for orchestrating and leveraging multiple MCP servers and tools based on user requests
Overview

what is Meta MCP Server?

Meta MCP Server is a meta server designed to orchestrate and leverage multiple Model Control Protocol (MCP) servers and tools based on user requests.

how to use Meta MCP Server?

To use Meta MCP Server, clone the repository, install the dependencies, configure the environment variables, and start the server. It exposes a REST API for user requests.

key features of Meta MCP Server?

  • Request Analysis: Parses and understands user requests to determine intent.
  • Tool Discovery: Maintains a registry of available MCP tools and their capabilities.
  • Orchestration: Creates execution plans that may involve multiple MCP servers.
  • Tool Recommendation: Suggests creation of new tools when gaps are identified.

use cases of Meta MCP Server?

  1. Automating data extraction and visualization tasks.
  2. Coordinating multiple tools for complex workflows.
  3. Enhancing user interaction with various MCP tools through a unified interface.

FAQ from Meta MCP Server?

  • What are the prerequisites for using Meta MCP Server?

You need Node.js v18 or higher and access to one or more MCP servers/tools.

  • How do I start the server?

After installation, run npm start to start the server.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can submit a Pull Request.

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