modwire
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@modwireinspect the scaffolding collection"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Enclosure
Enclosure gives coding agents the context and guardrails they need to work confidently across projects. It combines reusable project guidance, architecture checks, diagrams, and scaffolding behind REST, Siren, and MCP.
Highlights
Agent-ready workspace guidance and project-health checks
Architecture contracts backed by Modwire and Mermaiden
Reusable records and project scaffolding
A Siren browser for exploring resources and actions
One machine-wide MCP server for every local project
Related MCP server: MCP Inspector as MCP Server
Quick start
uv sync
uv run python manage.py migrate
make mcpThe local stack runs on 127.0.0.1:8000:
Interface | URL |
Siren browser |
|
REST API |
|
Siren API |
|
MCP |
|
Use make dev when only the standard Django development server is needed.
Development
Run the complete verification suite before handoff:
make ciAfter changing the TypeScript browser, rebuild its checked-in static assets:
make browser-buildHard-refresh the browser after rebuilding to discard a cached bundle.
Machine-wide MCP server
The Compose runtime exposes MCP at http://127.0.0.1:8666/mcp and keeps the
server running as enclosure-mcp. Configure .env as needed:
ENCLOSURE_IMAGErequires an exact immutable SemVer release tag. Do not use the movinglatesttag for the machine-wide runtime.ENCLOSURE_PROJECTS_DIRselects the host projects directory mounted into the container at the same absolute path.MODWIRE_CACHE_MAX_BYTEScaps the persistent Modwire scan and analysis cache stored in the dedicatedmodwire-cachevolume.PROJECT_HEALTH_MAX_CONCURRENCYbounds architecture-health processes across all web workers. Excess requests fail immediately instead of queueing.PROJECT_HEALTH_TIMEOUT_SECONDSbounds each architecture-health process; the default is 60 seconds. Client disconnects cancel it sooner.PROJECT_HEALTH_WORKER_READY_TIMEOUT_SECONDSbounds worker bootstrap before a request is accepted; the default is 15 seconds.PROJECT_HEALTH_CACHE_MAX_BYTEScaps validated project-health stage results in the dedicatedhealth-cachevolume. Failed, canceled, and timed-out runs are never stored.
Start or update the runtime:
make runtime-config
make runtime-up
curl --fail http://127.0.0.1:8666/health//health/ remains the container liveness probe. Project-health capacity is
reported by the existing project-health operation, which returns 503 rather
than queueing when every execution slot is occupied.
runtime-up migrates with the selected image before starting MCP and retains
the previous image locally as :previous. Back up PostgreSQL before deploying
potentially irreversible migrations. Use make runtime-rollback to restore
the retained image, and make runtime-down to remove only the MCP container.
Releases
GitHub Release tags are canonical. Stable releases publish SemVer, minor,
latest, and commit-traceability image tags; prereleases never move latest.
Docker Hub publication requires DOCKERHUB_USERNAME and DOCKERHUB_TOKEN in
the repository configuration.
API attribution
The API is auth-free. Mutating record requests use X-Actor-Id and
X-Actor-Type; supported actor types are user and agent.
License
Copyright (c) 2026 Tomasz Szpak. All rights reserved. Enclosure is proprietary software; see the LICENSE file for the complete terms.
This server cannot be deployed
Maintenance
Related MCP Connectors
Programmatic control of the Hiro security platform: scans, tasks, plans, and approvals.
Tools to explore SumUp accounts, payments, customers, and payouts.
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
327 dev tools via REST API and MCP. Generate Dockerfiles, schemas, K8s, APIs, and more.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables interaction with ACOMO API through MCP tools and resources. Provides comprehensive API exploration, operation calling, and schema inspection capabilities for ACOMO backend services.82MIT
- AlicenseAqualityBmaintenanceEnables LLMs to inspect and test other MCP servers by listing and calling their tools, reading resources, and getting prompts. Supports stdio, SSE, and HTTP transports for both local and remote MCP server inspection.74 npm1MIT
- AlicenseAqualityBmaintenanceDiscovers, inspects, and executes requests against OpenAPI or Swagger APIs directly from documentation URLs or specification files. It enables users to trace parameter usage across an API and perform authenticated HTTP requests through a structured toolset.816 npm5MIT
- FlicenseNot gradedqualityDmaintenanceEnables users to expose arbitrary HTTP APIs as configurable MCP tools by defining tool specifications in a JSON configuration file.2,572 npm3-