Clavis

io.github.KN0WBOTPublished by GitHub account KN0WBOTv0.1.3Updated Oct 24, 2026

Encrypted credential vault for AI agents — auto OAuth refresh, rate limiting, audit logging.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Clavis is a local MCP server that gives an assistant access to an encrypted credential vault, letting it call services with stored keys injected server-side.

What you can do
List stored services and check credential status and expiry for each one. Make upstream API calls through the vault so the raw key is injected server-side and never enters the conversation. Retrieve a raw access token or API key for a named service through a legacy tool. Rely on the Clavis server for OAuth token refresh, rate limiting, audit logging and usage tracking.
When to use it
Use it when an assistant needs to call third-party APIs with stored credentials and you want to keep the secrets out of the chat context. It suits setups that also want centralized OAuth refresh, rate limiting and audit logging for those calls.
Requirements
Runs locally over stdio via the npm package, typically started with npx or installed globally, so Node.js is needed. Requires a Clavis account and the CLAVIS_API_KEY environment variable holding a Clavis JWT obtained from the login endpoint, not the sign-up key. Optionally set CLAVIS_API_URL for a self-hosted instance; network access to the Clavis server is required.
Before you install
The configuration asks for a Clavis JWT in CLAVIS_API_KEY, which grants access to the stored credentials. The legacy get_credentials tool returns raw keys into the conversation, where prompt injection could exfiltrate them; prefer call_service. Calls made through the vault reach third-party services and are logged and rate limited by the Clavis server, so review what data is sent upstream.

Installation

In SourceWeft

  1. Open Clavis in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

Installation

bash
npx @clavisagent/mcp-server

Or install globally:

bash
npm install -g @clavisagent/mcp-server

Usage with Claude Desktop

Add the following to your Claude Desktop configuration file (claude_desktop_config.json):

json
{  "mcpServers": {    "clavis": {      "command": "npx",      "args": ["-y", "@clavisagent/mcp-server"],      "env": {        "CLAVIS_API_KEY": "eyJ..."      }    }  }}

Usage with Claude Code

bash
claude mcp add clavis -- npx -y @clavisagent/mcp-server

Configuration

VariableRequiredDefaultDescription
CLAVIS_API_KEYyes—Your Clavis JWT, from POST /v1/auth/login. Not the cla_… key shown at sign-up.
CLAVIS_API_URLnohttps://clavisagent.comBase URL of your Clavis instance. Set this for self-hosted deployments.

Available Tools

ToolDescription
call_serviceRecommended. 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_credentialsLegacy. Returns the raw access token or API key for a named service. Prefer call_service.
list_servicesList all services with stored credentials
check_credential_statusCheck 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

Source: README.md at commit 92ecdc1

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts