my-model-context

Created By
matteovhaxta year ago
CLI to manage local MCP server configs
Overview

what is my-model-context?

my-model-context is a command-line interface (CLI) tool designed to manage local MCP (Model Context Provider) server configurations efficiently.

how to use my-model-context?

To use my-model-context, first install the necessary dependencies using the command bun install, and then run the application with bun run index.ts.

key features of my-model-context?

  • Easy management of local MCP server configurations.
  • Built with Bun, a fast all-in-one JavaScript runtime.
  • Simple installation and execution process.

use cases of my-model-context?

  1. Configuring local development environments for model context management.
  2. Streamlining the setup of server configurations for testing.
  3. Facilitating quick changes to server settings without complex setups.

FAQ from my-model-context?

  • What is Bun?

Bun is a fast all-in-one JavaScript runtime that allows for quick installation and execution of JavaScript applications.

  • Is my-model-context free to use?

Yes! my-model-context is open-source and free to use.

  • What programming language is used in my-model-context?

my-model-context is developed using TypeScript.

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