mcp-vault-reader
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_PORT | No | Set a port (e.g. 3000) to run over HTTP/SSE instead of standard stdio. | |
| MCP_HTTP_HARDEN | No | If true, enables DNS rebinding protection and strict rate limits. | false |
| VAULT_CONFIG_DIR | No | Where vault configs and remote clones are stored. | ~/.mcp-vault-reader |
| MCP_HTTP_AUTH_TOKEN | No | Bearer token required for security when running HTTP server. | |
| VAULT_SYNC_ON_START | No | If set to true, the MCP server syncs all vaults on startup. | false |
| MCP_HTTP_ALLOWED_ORIGINS | No | CORS allowed origins. | 127.0.0.1 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LucasRocha179/mcp-vault-reader'
If you have feedback or need assistance with the MCP directory API, please join our Discord server