home / mcp / buerokratt mcp server
Provides MCP endpoints and tooling to share Bürokratt module rules and prompts for AI coding assistants.
Configuration
View docs{
"mcpServers": {
"igorkrupenja-buerokratt-mcp": {
"url": "http://localhost:3627/mcp"
}
}
}The Bürokratt MCP Server lets you share and access module-specific AI rules across your development tools. It centralizes rules for different Bürokratt modules so you can load them into your IDEs and AI coding assistants, ensuring consistent guidance across environments.
You connect your MCP client to the Bürokratt MCP Server to load rules for a specific module. Once connected, you can fetch rules, list available modules, search for rules by keywords, and load development prompts tailored to a module. This enables AI assistants to follow module-specific guidelines during coding tasks, migrations, and frontend or backend work.
Prerequisites: Node.js and a container runtime if you plan to run the server locally via Docker Compose. You will also use a code editor that supports MCP settings, such as VS Code or JetBrains IDEs.
1. Start the MCP server locally using Docker Compose.
docker-compose up -d2. In your project, configure the MCP client to point to the local server. Use the example below to load rules for the Bürokratt MCP server.
{
"mcpServers": {
"buerokratt-mcp": {
"url": "http://localhost:3627/mcp",
"args": []
}
}
}3. Optionally add a module rule loader for your project so the client loads rules based on path, placing a rule file in your project at .cursor/rules/buerokratt-mcp.mdc.
4. If you are using an IDE that uses workspace settings, configure the MCP server there as well. See the examples for VS Code and JetBrains.
The server exposes rules per module and supports a few practical capabilities like loading rules on demand, listing modules, and providing a development prompt for a module. Rules are stored in Markdown with frontmatter in the rules/ directory. Each rule file must declare a modules array containing the exact Bürokratt module names you want to enable for that rule file.
Context size considerations apply when you merge multiple module rules. Keep individual file sizes small and avoid excessively large merged module rule sets to ensure fast loading.
The MCP server provides handy tools and endpoints you can invoke to work with rules and modules.
- get_rules: Retrieve rules for a specific module.
- list_modules: List all available modules.
- search_rules: Search rules by keyword.
- development-rules: Get development rules as a system prompt for a module.
- MCP Inspector: Use the inspector tool to test the MCP setup and prompt integration.
Editing rules is straightforward: modify the Markdown rule files under rules/, commit changes, and they load on the next request without needing to restart the server.
Project structure places global rules and module-specific rules under folders like rules/global/ and rules/Service-Module/, with additional modules as needed.
For local development, you can run the project workflow that installs dependencies and starts the server using the commands shown in the deployment guidance. Be mindful of the recommended size limits for rule files to avoid timing out or hitting token limits.
There are checks to ensure format, linting, type correctness, and rule validity. Run the local test suite as part of your development to keep rules consistent with their intended module mappings.
Fetch rules for a specific Bürokratt module, enabling targeted guidance and prompts.
List all available Bürokratt modules with loaded rules.
Search rule sets by keyword to quickly locate relevant guidance.
Provide development-focused system prompts for a chosen module to assist development tasks.
Inspect the MCP server setup using the built-in inspector tool for debugging and validation.