Skip to main content
Glama
clavis-mcp-server

clavis-mcp-server

Clavis MCP Server

Sichere Anmeldedatenverwaltung für Claude Desktop und MCP-Server.

Funktionen

  • 🔐 Verschlüsselte Speicherung von Anmeldedaten (AES-256)

  • 🔄 Automatische Aktualisierung von OAuth-Tokens

  • ⚡ Verteilte Ratenbegrenzung

  • 📊 Vollständige Audit-Protokollierung

Related MCP server: GhostKey

Installation

npx @clavisagent/mcp-server

Oder global installieren:

npm install -g @clavisagent/mcp-server

Verwendung mit Claude Desktop

Fügen Sie Folgendes zu Ihrer Claude Desktop-Konfigurationsdatei (claude_desktop_config.json) hinzu:

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

Verwendung mit Claude Code

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

Verfügbare Tools

Tool

Beschreibung

get_credentials

Abrufen eines gültigen Zugriffstokens oder API-Schlüssels für einen benannten Dienst

list_services

Auflisten aller Dienste mit gespeicherten Anmeldedaten

check_credential_status

Überprüfen des Status und der Gültigkeitsdauer von Anmeldedaten für einen Dienst

Lizenz

MIT

Available Tools

4 tools
call_serviceA

RECOMMENDED: Make an API call with server-side credential injection. The credential is fetched from the Clavis vault and injected into the upstream request server-side — the raw API key never enters this conversation. Prefer this over get_credentials: it eliminates prompt-injection exfiltration as an attack vector, because there is no secret in context to exfiltrate.

Inputs: url (required), method (required), service_name (required), data, +3 more.

check_credential_statusA

Check the validity and rate-limit status of credentials for a service without making any external API call. Queries only the Clavis vault (database + Redis). Returns validity, expiry, rate-limit headroom, and last-used timestamp.

Inputs: service_name (required).

get_credentialsA

LEGACY — returns raw credential data into this conversation. Prefer call_service for security: call_service injects credentials server-side so the raw API key is never exposed to the model. Use this only when you must hold the token itself (e.g. handing it to a library that cannot be proxied). Clavis handles token refresh and rotation automatically.

Inputs: service_name (required).

list_servicesA

List all services configured in Clavis for the authenticated developer.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: call_service proxies requests with server-side credential injection, get_credentials returns raw tokens for non-proxy use, list_services enumerates configured services, and check_credential_status inspects vault state without external calls. The overlap between call_service and get_credentials is explicitly addressed with usage guidance, so an agent can select correctly.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in lower_snake_case: call_service, get_credentials, list_services, check_credential_status. The verbs are distinct and clearly map to each tool's function.

    Tool Count5/5

    With four tools, the set is tightly focused on core Clavis operations: using credentials, retrieving them, listing services, and checking status. This is the right granularity for a credential-management server—not bloated, not thin.

    Completeness5/5

    The tool surface covers the full lifecycle of interacting with Clavis-managed credentials: calling an upstream service, retrieving a raw credential when necessary, discovering available services, and checking status/rate limits. Missing features like credential creation or rotation are handled automatically by Clavis, so these are not gaps for the agent.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Encrypted 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP-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.
      2 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Credential 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