Click on "Install 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., "@modwire inspect 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 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.
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: ACOMO MCP Server
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.
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.
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_IMAGE selects latest or an exact immutable release tag.
ENCLOSURE_PROJECTS_DIR selects the host projects directory mounted into
the container at the same absolute path.
Start or update the runtime:
make runtime-config
make runtime-up
curl --fail http://127.0.0.1:8666/health/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.
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.
The API is auth-free. Mutating record requests use X-Actor-Id and
X-Actor-Type; supported actor types are user and agent.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Programmatic control of the Hiro security platform: scans, tasks, plans, and approvals.
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.
Drive real Android & iOS devices and web browsers from natural language for mobile + web QA. 290+ tools across device control, app management, automation sessions, browser automation, and flow recording / replay. Bearer-auth — get a token at robotactions.com → Profile → API Tokens.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/szpak-dev/enclosure'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
