MCP Context Template

Created By
currenjina year ago
🪱 MCP Context Template is a repository designed to centrally manage AI tools (MCP) to reduce context sharing costs and improve development productivity.
Overview

What is MCP Context Template?

MCP Context Template is a repository designed to centrally manage AI tools (MCP - Model Centralized Prompting) to reduce context sharing costs and improve development productivity.

How to use MCP Context Template?

To use MCP Context Template, set ai-context/ as a context path in your project's .cloderc or Cursor settings and reference guides in Claude Code prompts.

Key features of MCP Context Template?

  • Central context repository for AI tools
  • Reference document structure for collaboration
  • Examples and guides for different teams
  • Consistent AI usage experience across projects
  • Reduces duplicate context management burden

Use cases of MCP Context Template?

  1. New developer onboarding to understand code styles
  2. Automating repetitive coding tasks like test code generation
  3. Code review automation for generating consistent comments
  4. Supporting documentation tasks in codebases

FAQ from MCP Context Template?

  • Can I contribute to the MCP Context Template?

Yes! Contributions can be made via Pull Requests.

  • Is there a specific format for documentation?

Yes, all convention documents should be written in Markdown.

  • How can I integrate it into my project?

Set the context path in your project settings and reference the guides as needed.

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