About Clavis Mcp Server
Clavis MCP Server provides credential management for Claude Desktop and MCP servers, with encrypted storage and server-side credential injection. It also handles OAuth token refresh, rate limiting, audit logging, and usage tracking.
Key features
- 01Encrypted credential storage
- 02Server-side secret injection
- 03Automatic OAuth token refresh
- 04Rate limiting and audit logging
- 05Credential status and expiry checks
- 06Service API calls through tools
Use cases
- 01Call third-party APIs without exposing keys in conversation
- 02Refresh OAuth credentials automatically
- 03Review stored service credentials and expiry
MCP support
Exposes tools to call services using stored credentials, list services, inspect credential status, and retrieve credentials. Its recommended call_service tool injects secrets server-side so raw keys stay out of the conversation.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEClavis 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
Installation
npx @clavisagent/mcp-server
Or install globally:
npm install -g @clavisagent/mcp-server
Usage 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-server
Configuration
| Variable | Required | Default | Description |
|---|---|---|---|
CLAVIS_API_KEY | yes | — | Your Clavis JWT, from POST /v1/auth/login. Not the cla_… key shown at sign-up. |
CLAVIS_API_URL | no | https://clavisagent.com | Base URL of your Clavis instance. Set this for self-hosted deployments. |
Available Tools
| Tool | Description |
|---|---|
call_service | 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. |
get_credentials | Legacy. Returns the raw access token or API key for a named service. Prefer call_service. |
list_services | List all services with stored credentials |
check_credential_status | 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.