Servicebricks
Scaffold a ServiceBricks C# .NET microservice as a downloadable ZIP from your coding agent without hand-rolling solution layout.
Overview
io.github.holomodular/servicebricks is a MCP server for the Build phase that generates a ServiceBricks C# .NET microservice and delivers it as a ZIP file.
What is this MCP server?
- Generates a ServiceBricks C# .NET microservice packaged as a ZIP file
- Remote streamable-http MCP at https://servicebricks.com/api/mcp
- Published server schema version 0.1.0
- Source repository holomodular/ServiceBricks on GitHub
- No local stdio package required when using the hosted remote endpoint
- Server version 0.1.0
- Single remote endpoint https://servicebricks.com/api/mcp
- Transport type streamable-http
Community signal: 4 GitHub stars.
What problem does it solve?
.NET founders lose days recreating the same microservice folder structure, packages, and ServiceBricks conventions for every new API slice.
Who is it for?
Solo builders shipping C# .NET APIs who want agent-driven ServiceBricks boilerplate via a hosted MCP remote.
Skip if: Teams on Node, Go, or Rust-only stacks, or anyone who needs full infra provisioning rather than service ZIP codegen.
What do I get? / Deliverables
After registration, your agent can fetch a ready-to-unzip .NET microservice scaffold you extend toward production.
- ZIP archive containing a ServiceBricks-style C# .NET microservice
- Agent-callable codegen path for new backend services
Recommended MCP Servers
Journey fit
How it compares
Hosted remote MCP for .NET microservice ZIP codegen, not a general-purpose IaC or container deploy server.
Common Questions / FAQ
Who is servicebricks for?
Indie and small-team developers building C# .NET microservices who want MCP-driven scaffolding from ServiceBricks conventions.
When should I use servicebricks?
Use it in Build when starting a new backend service or bounded context and you want a ZIP starter instead of manual template copying.
How do I add servicebricks to my agent?
Add the remote MCP server URL https://servicebricks.com/api/mcp (streamable-http) in your agent's MCP configuration per your client's remote-server docs.