logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

BC-MCP

Standardizes development rules and context for Business Central projects using JSON-based configurations. Ensures consistent coding practices and deployment processes across team members with dynamic or static rule management.

Author

BC-MCP logo

vanachterjacob

MIT License

Quick Info

GitHub GitHub Stars 2
NPM Weekly Downloads 0
Tools 1
Last Updated 2026-02-19

Tags

projectsvanachterjacobdevelopmentmanagement vanachterjacobproject managementcentral projects

Business Central MCP Server

A server that provides standardized development rules and context for Business Central projects, optimized for use with Cursor editor.

Features

  • Static Rules: JSON-based rules for Cursor editor
  • Render Deployment: Easy deployment to Render.com
  • Fallback Mode: Works without database connection
  • Team-Friendly: Rules automatically applied to all team members

Quick Start

For Team Members

To use the BC standards in your project:

  1. Clone this repository or copy the following files to your project:
  2. bc-rules.json
  3. .cursor-context

  4. Cursor will automatically pick up these rules when editing files in your project.

For Administrators

To update or manage the rules:

  1. Edit bc-rules.json directly to update static rules
  2. Or use the MongoDB database to store and manage rules dynamically
  3. Run node scripts/generateRules.js to update the static file from the database

Deployment

  1. Run ./scripts/deployRender.sh to prepare for deployment
  2. Push to GitHub
  3. Connect repository to Render.com
  4. Set environment variables in Render dashboard:
  5. NODE_ENV: production
  6. MCP_SERVER_PORT: 10000
  7. MONGODB_URI: Your MongoDB connection string (optional)

Endpoints

  • /cursorrules: Get the current rules (JSON format)
  • /health: Server health check

Rule Structure

Rules are structured as follows:

{
  "version": "1.0",
  "rules": [
    "Follow business naming conventions for all code",
    "Include proper error handling in all functions"
  ],
  "context": {
    "businessDomain": "Business Central",
    "preferredPatterns": ["Repository pattern", "SOLID principles"]
  }
}

See Also

`