clavis-mcp-server
Clavis MCP Server
Secure credential management for Claude Desktop and MCP servers.
Features
🔐 Encrypted credential storage (AES-128-CBC + HMAC-SHA256, via Fernet)
🛡️ Server-side credential injection — the raw key never enters the conversation
🔄 Automatic OAuth token refresh
📡 Thin forwarding layer — rate limiting, audit logging, and usage tracking are all handled by the Clavis server
Related MCP server: GhostKey
Installation
npx @clavisagent/mcp-serverOr install globally:
npm install -g @clavisagent/mcp-serverUsage with Claude Desktop
Add the following to your Claude Desktop configuration file (claude_desktop_config.json):
{
"mcpServers": {
"clavis": {
"command": "npx",
"args": ["-y", "@clavisagent/mcp-server"],
"env": {
"CLAVIS_API_KEY": "eyJ..."
}
}
}
}Usage with Claude Code
claude mcp add clavis -- npx -y @clavisagent/mcp-serverConfiguration
Variable | Required | Default | Description |
| yes | — | Your Clavis JWT, from |
| no |
| Base URL of your Clavis instance. Set this for self-hosted deployments. |
Available Tools
Tool | Description |
| Recommended. Make an API call with server-side credential injection — the credential is injected into the upstream request server-side, so the raw key never enters the conversation. |
| Legacy. Returns the raw access token or API key for a named service. Prefer |
| List all services with stored credentials |
| Check the status and expiry of credentials for a service |
Security note
Prefer call_service over get_credentials. call_service keeps the secret
server-side, so a prompt injection has no credential in context to exfiltrate.
get_credentials places the raw key in the conversation and exists only for
callers that must hold the token themselves.
License
MIT
Maintenance
Related MCP Servers
- Alicense-qualityDmaintenanceEncrypted credential vault with a 21-tool MCP server. Store and manage LLM API keys, service API keys, and OAuth credentials — then let your AI agent list, reveal, rotate, rename, pause, and proxy calls through them.MIT
- Alicense-qualityBmaintenanceMCP-native credential vault that enables AI agents to authenticate with external services without exposing secrets, supporting bearer, basic, OAuth2, and other auth patterns via MCP tools.7MIT
- Flicense-qualityCmaintenanceEnables AI agents and MCP clients to securely store, retrieve, and manage encrypted credentials without hardcoding API keys.
- Alicense-qualityBmaintenanceCredential vault for LLM agents that stores credentials encrypted and exposes MCP tools for authenticated HTTP requests, web scraping, and credential management, preventing AI assistants from seeing secrets.Apache 2.0
Related MCP Connectors
Encrypted secret store and rotation for autonomous agent credentials
MCP-native Trust Infrastructure for AI Agents. Persistent encrypted memory with Trust Quotient.
Free public MCP for AI agents — 193 tools, 44 workflows. No API key.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/KN0WBOT/clavis-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server