MCPRules - Programming Guidelines Management Server

Created By
bartwischa year ago
A powerful Model Context Protocol (MCP) server that manages and serves programming guidelines and rules. This server integrates with development tools to provide consistent coding standards across projects.
Overview

what is MCPRules?

MCPRules is a powerful Model Context Protocol (MCP) server designed to manage and serve programming guidelines and rules, promoting consistent coding standards across various projects.

how to use MCPRules?

To use MCPRules, clone the repository from GitHub, install the necessary dependencies, build the server, and configure the environment variables. You can then access the rules through various tools integrated with the server.

key features of MCPRules?

  • Rule Management: Access and filter rules by categories, supporting both local and GitHub-hosted rules.
  • Flexible Storage: Integration with local file systems and GitHub, allowing markdown-based rule definitions.
  • Category Organization: Supports various categories related to programming principles and specific languages.

use cases of MCPRules?

  1. Enforcing coding standards across teams in software development.
  2. Managing programming guidelines in collaborative projects.
  3. Tailoring coding standards by project needs or programming languages.

FAQ from MCPRules?

  • How do I install MCPRules?

Clone the repository, install dependencies, build the server, and configure your rules file path.

  • Can I host my own rules?

Yes! MCPRules supports local and GitHub-hosted markdown-based rules.

  • What is the licensing for MCPRules?

MCPRules is licensed under the MIT License, allowing for free use and modification.

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

2 days ago