mcp_input_analyzer

Created By
Sumedh1599a year ago
Analyzes user-described build features (e.g. database, API integration, tools) and extracts core server requirements like resources, tools, prompts, external systems, and transports needed for MCP.
Overview

What is mcp_input_analyzer?

mcp_input_analyzer is an open-source library designed to analyze user-described build features such as databases, API integrations, and tools. It extracts core server requirements including resources, tools, prompts, external systems, and transports needed for the Microservices Configuration Platform (MCP).

How to use mcp_input_analyzer?

To use mcp_input_analyzer, install it via pip with Python 3.6+ or clone the repository and install from source. You can then initialize the analyzer with a description of your build features and call its methods to extract requirements or generate structures.

Key features of mcp_input_analyzer?

  • Natural language to structured build feature extraction
  • MCP-compliant input structure generation
  • Validation of supported tools and protocols
  • Creation of Claude-readable JSON definitions
  • Fallback logic for unsupported features

Use cases of mcp_input_analyzer?

  1. Analyzing project requirements for microservices.
  2. Generating structured input for MCP platforms.
  3. Validating tool compatibility for server configurations.

FAQ from mcp_input_analyzer?

  • Can mcp_input_analyzer handle all types of build features?

Yes! It is designed to analyze a wide range of build features including databases and APIs.

  • Is mcp_input_analyzer free to use?

Yes! It is an open-source library available for everyone.

  • How can I contribute to mcp_input_analyzer?

You can contribute by opening issues or submitting pull requests on the GitHub repository.

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

2 days ago