📬 mcp-index

Created By
mcprepositorya year ago
CLI tool to index MCP Servers to mcprepository.com
Overview

what is mcp-index?

mcp-index is a CLI tool designed to submit your GitHub repository as an MCP Server to mcprepository.com, the official MCP Server Repository. It allows developers to list their automation tools, AI servers, or protocol interfaces publicly for discovery.

how to use mcp-index?

To use mcp-index, you can either run it instantly via npx with the command npx mcp-index <github-repo-url> or install it globally using npm install -g mcp-index. After installation, you can submit your repository by running mcp-index https://github.com/yourname/your-mcp-server.

key features of mcp-index?

  • Simple command-line interface for easy submission of MCP Servers.
  • Automatic checks for duplicates and MCP compatibility.
  • Queues submissions for processing and validation.
  • Notifications when the repository is available on the MCP Repository.

use cases of mcp-index?

  1. Submitting automation tools to the MCP repository for public access.
  2. Listing AI servers for easier discovery by other developers.
  3. Validating and indexing protocol interfaces for community use.

FAQ from mcp-index?

  • What is an MCP Server?

An MCP Server is a server that follows the Model Context Protocol, allowing for standardized interactions.

  • Do I need to provide a valid GitHub repository URL?

Yes, a valid GitHub repository URL is required for submission.

  • How will I know if my submission is successful?

You will receive a notification once your repository is validated and available on the MCP Repository.

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