# crowvault [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/rajeswaran140/crowvault-setup  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/crowvault

## Description
327 dev tools via REST API and MCP. Generate Dockerfiles, schemas, K8s, APIs, and more.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "crowvault": {
    "url": "https://api.crowvault.ai"
  }
}
```

## Documentation

## What crowvault does

The crowvault MCP server connects CI/CD workflows to the CrowVault platform through the CrowVault CLI. The repository provides a GitHub Action that installs and authenticates the CLI, allowing subsequent workflow steps to generate development and infrastructure artifacts.

Supported generation targets include database schemas, Dockerfiles, OpenAPI specifications, Kubernetes configurations, and Terraform modules. The CLI also supports named workflows for larger, ordered tasks such as scaffolding a microservice, preparing a deployment stack, or setting up a database.

CrowVault exposes nine MCP servers containing 327 tools. The CLI can list those servers, search their tools, and call a selected tool with key-value arguments. This makes the repository relevant when a pipeline needs either a focused generator command or access to the broader CrowVault tool catalog.

## How it works

A workflow first invokes `rajeswaran140/crowvault-setup@v1` with a CrowVault API key. The action installs the requested CLI version and uses the configured API endpoint. Later steps invoke commands such as `crowvault schema`, `crowvault dockerfile`, or `crowvault workflow run`.

Generated content can be written directly to files with `--output`. Commands can also be grouped in shell steps, which supports batch generation for multiple schemas or infrastructure outputs. The `batch` command accepts a JSON file and can execute up to 10 operations in parallel.

Predefined workflows combine related operations. For example, `microservice-scaffold` covers a service, schema, migration, Docker configuration, and Kubernetes configuration, while `deploy-stack` produces Dockerfile, Compose, Kubernetes, and Helm outputs. The available workflow definitions cover six named scenarios.

## Setup and configuration

Add the GitHub Action to a workflow and pass `secrets.CROWVAULT_API_KEY` through the required `api-key` input. The key is obtained from the CrowVault dashboard after account registration; the free plan lists 50 calls per month. Store the key as an encrypted GitHub secret rather than placing it directly in workflow source.

The optional `version` input selects the CLI version and defaults to `latest`. The optional `api-url` input defaults to `https://api.crowvault.ai`, allowing the endpoint to be changed when needed. The documented secret name for the API key is `CROWVAULT_API_KEY`.

## Tools and capabilities

The crowvault MCP server and CLI provide commands for:

- Listing available MCP servers with `crowvault servers`.
- Searching the tool catalog with `crowvault tools --search <query>`.
- Calling a selected server tool with `crowvault call <server> <tool>`.
- Generating schemas in formats such as Prisma.
- Generating runtime-specific Dockerfiles.
- Producing OpenAPI specifications and Terraform modules.
- Running named multi-step workflows.
- Executing up to 10 operations in parallel from a batch file.

## Limitations and notes

The repository documents a GitHub Action and CLI workflow rather than client-specific desktop or editor setup. It does not list compatibility with individual MCP clients. API access is required, and usage is subject to the account plan; the documented free plan allows 50 calls per month.

_Full upstream README: https://allmcps.com/mcp/crowvault/readme_