Clavis

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

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "clavis": {
      "command": "npx",
      "args": [
        "-y",
        "@clavisagent/mcp-server"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Capabilities & Tool Schemas (4)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by Clavis.

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

Documentation Overview

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

Terminal

npx @clavisagent/mcp-server

Or install globally:

Terminal

npm install -g @clavisagent/mcp-server

Usage with Claude Desktop

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

config.json

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

Usage with Claude Code

Terminal

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

Read the full README →View source on GitHub →

Related MCP Servers

View all in Monitoring View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit

1mo ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Clavis

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "clavis": { "command": "npx", "args": ["-y","@clavisagent/mcp-server"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/clavis?style=directory)](https://allmcps.com/mcp/clavis)

HTML Embed

<a href="https://allmcps.com/mcp/clavis"><img src="https://allmcps.com/api/badge/clavis?style=directory" alt="Clavis on AllMCPs" /></a>

Technical Specs & Signals

CategoryMonitoring

5/10 checks healthy over the last 46d

48Quality signal: Fair · 48/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools24/30

Adoption & activity2/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · @clavisagent/mcp-server (npm)

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 📊 Monitoring →Best MCP servers for Monitoring & Observability →Alternatives to Clavis →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients

Documentation Overview

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

Terminal

npx @clavisagent/mcp-server

Or install globally:

Terminal

npm install -g @clavisagent/mcp-server

Usage with Claude Desktop

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

config.json

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

Usage with Claude Code

Terminal

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

License

MIT