Skip to main content
Glama
kelleyblackmore

Vault MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VAULT_ADDRNoThe Vault server addresshttp://127.0.0.1:8200
VAULT_TOKENYesThe Vault authentication token

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
vault_readC

Read a secret from Vault at the specified path

vault_writeC

Write a secret to Vault at the specified path

vault_listB

List secrets at the specified path in Vault

vault_deleteC

Delete a secret from Vault at the specified path

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose targeting a specific CRUD operation: delete, list, read, and write. There is no overlap or ambiguity between these actions, making it easy for an agent to select the correct tool for any secret management task.

Naming Consistency5/5

All tool names follow a perfect and consistent pattern: 'vault_' prefix followed by a verb (delete, list, read, write). This uniformity makes the tool set predictable and easy to understand at a glance.

Tool Count5/5

With 4 tools, this server is well-scoped for its purpose of Vault secret management. Each tool earns its place by covering essential CRUD operations without bloat, making the set concise and effective for the domain.

Completeness5/5

The tool set provides complete CRUD/lifecycle coverage for secret management: write (create), read (retrieve), list (browse), and delete (remove). There are no obvious gaps, ensuring agents can handle all core workflows without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues