enbuild-mcp-server
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"enbuild-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server for the ENBUILD Platform. Provides tools for managing ENBUILD catalogs and integrates with Amazon Q, VS Code, and other MCP-compatible clients.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
MCP Server for kubernetes management commands
MCP server for Dynatrace Managed to access logs, events, and metrics.
MCP server for no-payment x402 surface triage, 402 Index health checks, and paid review handoff.
MCP Security Weekly
Get CVE alerts and security updates for Enbuild Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server for the ENBUILD Platform. Provides tools for managing ENBUILD catalogs and integrates with Amazon Q, VS Code, and other MCP-compatible clients.
mcp-server-enbuild binary from the releases page.# Stdio
q config add-mcp-server enbuild stdio
# SSE
q config add-mcp-server enbuild http://localhost:8080
Add to your User Settings (JSON):
{
"servers": {
"enbuild": {
"type": "stdio",
"command": "/usr/local/bin/mcp-server-enbuild",
"args": ["--base-url", "https://enbuild-dev.vivplatform.io"],
"env": {
"ENBUILD_BASE_URL": "https://enbuild-dev.vivplatform.io",
"ENBUILD_USERNAME": "username",
"ENBUILD_PASSWORD": "password"
}
}
}
}
{
"mcpServers": {
"enbuild": {
"type": "stdio",
"command": "/usr/local/bin/mcp-server-enbuild",
"args": ["--base-url", "https://enbuild-dev.vivplatform.io"],
"env": {
"ENBUILD_BASE_URL": "https://enbuild.vivplatform.io",
"ENBUILD_USERNAME": "username",
"ENBUILD_PASSWORD": "password"
}
}
}
}
The following tools are provided:
search_catalogs: List all catalogs for a specific VCSget_catalog_details: Get catalog details by ID# List all catalogs for a specific VCS
enbuild search_catalogs --vcs "GITHUB"
# Get catalog details
enbuild get_catalog_details --id "catalog-id"
# Search for catalogs by name, type, and VCS
enbuild search_catalogs --name "terraform" --type "terraform" --vcs "GITHUB"
All tools return a consistent JSON response:
{
"success": true,
"message": "Successfully retrieved catalogs",
"count": 5,
"data": [
{
"id": "catalog-id",
"name": "catalog-name",
"type": "terraform",
"vcs": "GITHUB",
"slug": "catalog-slug"
}
]
}
To add new tools, update the registerTools function in mcpenbuild.go and implement the corresponding handler.
To build the project from source, ensure you have Go installed and run the following commands:
git clone https://github.com/vivsoftorg/mcp-server-enbuild.git
cd mcp-server-enbuild
go build -o mcp-server-enbuild
./mcp-server-enbuild
#### SSE (HTTP)
```bash
./mcp-server-enbuild --transport sse --sse-address :8080
You can configure the server using command-line flags or environment variables:
| Flag | Env Var | Description | Default |
|---|---|---|---|
-base-url | ENBUILD_BASE_URL | Base URL for ENBUILD | https://enbuild.vivplatform.io |
-username | ENBUILD_USERNAME | Username for ENBUILD | |
-password | ENBUILD_PASSWORD | Password for ENBUILD | |
-transport | Transport type: stdio or sse | stdio |