mcp_starter_cli

Created By
Sumedh1599a year ago
CLI tool to scaffold, run, and test MCP servers locally with Node.js or Python, integrated with Claude and OpenAI key injection and auto-link to Claude Desktop.
Overview

What is mcp_starter_cli?

mcp_starter_cli is a Command Line Interface (CLI) tool designed to scaffold, run, and test MCP servers locally using Node.js or Python, with integration for Claude and OpenAI API keys.

How to use mcp_starter_cli?

To use mcp_starter_cli, install it globally via npm or Yarn, then scaffold a new project or run an existing server using the provided commands.

Key features of mcp_starter_cli?

  • CLI Interface for easy server management.
  • Dynamic API Key Injection for OpenAI and Claude.
  • Real-time Server Logging and Error Display.
  • Integration with Claude Desktop for local testing.
  • Support for Auto-linting and TypeScript Transpilation.

Use cases of mcp_starter_cli?

  1. Quickly scaffold new MCP server projects in Node.js or Python.
  2. Test and debug local servers with live error monitoring.
  3. Manage API keys for AI integrations seamlessly.

FAQ from mcp_starter_cli?

  • What programming languages does it support?
    mcp_starter_cli supports both Node.js and Python for server development.

  • Is it necessary to have Node.js installed?
    Yes, Node.js is required to run the CLI tool.

  • Can I contribute to the project?
    Absolutely! Contributions are welcome via 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