DemiCode

Created By
greenrush21a year ago
Ringkasan tentang awesome-mcp-servers - koleksi server Model Context Protocol (MCP)
Overview

What is DemiCode?

DemiCode is a curated collection of Model Context Protocol (MCP) servers, allowing AI models to interact securely with local and remote resources through standardized server implementations.

How to use DemiCode?

To use DemiCode, explore the repository on GitHub, where you can find various implementations of MCP servers in different programming languages and categories.

Key features of DemiCode?

  • Collection of various MCP server implementations
  • Supports multiple programming languages including Python, TypeScript, Go, Rust, C#, and Java
  • Categorized services for local and cloud applications

Use cases of DemiCode?

  1. Automating browser tasks using local services.
  2. Integrating with external APIs for cloud-based applications.
  3. Utilizing database connections for AI model interactions.

FAQ from DemiCode?

  • What is MCP?

MCP (Model Context Protocol) is an open protocol that enables AI models to interact securely with local and remote resources.

  • How can I contribute to DemiCode?

You can contribute by following the contribution guidelines that will be added later in the repository.

  • What programming languages are supported?

DemiCode supports various languages including Python, TypeScript, Go, Rust, C#, and Java.

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