Skip to main content
Glama
Ceveto MCP Server

Ceveto MCP Server

Official
by Ceveto

Ceveto MCP Server

MCP (Model Context Protocol) server for AI agent access to the Ceveto business management API.

Quick Start

uvx --from git+https://github.com/Ceveto/mcp-server ceveto-mcp

Related MCP server: @agentlair/mcp

Claude Code Setup

Add to your .mcp.json:

{
  "mcpServers": {
    "ceveto": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/Ceveto/mcp-server", "ceveto-mcp"],
      "env": {
        "CEVETO_MCP_BASE_URL": "https://api.ceveto.com",
        "CEVETO_MCP_USERNAME": "<your-api-username>",
        "CEVETO_MCP_PRIVATE_KEY": "<your-api-private-key>"
      }
    }
  }
}

Or install the Ceveto Claude Plugin for automated setup.

Getting Credentials

  1. Log in to your Ceveto dashboard

  2. Go to Settings → API Keys

  3. Click Create API Key

  4. Save the username and private key (shown once)

Environment Variables

Variable

Required

Default

Description

CEVETO_MCP_USERNAME

Yes

—

API user username

CEVETO_MCP_PRIVATE_KEY

Yes

—

Ed25519 private key (hex)

CEVETO_MCP_BASE_URL

No

https://api.ceveto.com

API base URL

CEVETO_MCP_DEFAULT_ACCOUNT

No

—

Default account slug/UUID

CEVETO_MCP_MODULES

No

—

Comma-separated OpenAPI tags to filter

CEVETO_MCP_TRANSPORT

No

stdio

Transport: stdio or sse

CEVETO_MCP_PORT

No

8500

Port for SSE mode

How It Works

  1. On startup, fetches the OpenAPI schema from the Ceveto API

  2. Checks your permissions via /company-api/me/

  3. Generates MCP tools for each permitted API endpoint

  4. Tools include parameter schemas, descriptions, and permission limits

Docker (SSE mode)

docker build -t ceveto-mcp .
docker run -p 8500:8500 \
  -e CEVETO_MCP_USERNAME=... \
  -e CEVETO_MCP_PRIVATE_KEY=... \
  -e CEVETO_MCP_BASE_URL=https://api.ceveto.com \
  ceveto-mcp

Hosted Instances

Environment

MCP Server

Backend API

Production

https://mcp.ceveto.com

https://api.ceveto.com

Staging

https://mcp.ceveto.dev

https://api.ceveto.dev

Hosted mode (multi-tenant, no credentials needed on server):

ceveto-mcp --hosted --transport sse --port 8500

Security

  • Ed25519 signatures — every API request is cryptographically signed

  • OAuth 2.1 — browser-based authorization with PKCE

  • Permission-filtered tools — only endpoints you have access to become tools

  • Method-level filtering — read-only keys don't see write operations

  • No secrets stored — credentials only in environment variables

Available Tools

3 tools
list_accountsA

List all accounts this API key has access to.

Each entry includes the account id, name, slug, and whether the API user is an owner.

Inputs: no named parameters. Returns: result

switch_default_accountA

Switch the active account for all subsequent tool calls.

Args: account: Account slug (e.g. "acme-corp") or UUID.

Inputs: account (required). Returns: result

whoamiA

Show the current API user's identity, active account, and permissions.

Use this first to understand which account you're operating on and what permissions are available.

Inputs: no named parameters. Returns: result

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: whoami reports the current user, list_accounts enumerates accessible accounts, and switch_default_account changes the active account. No overlap or ambiguity.

    Naming Consistency4/5

    Two tools follow the verb_noun pattern (list_accounts, switch_default_account), while whoami is a standard Unix command rather than verb_noun. This is a minor deviation from an otherwise consistent, readable convention.

    Tool Count5/5

    Three tools is perfectly scoped for account identity and switching functionality. Each tool is necessary and there is no redundancy or bloat.

    Completeness5/5

    The tool surface covers the complete lifecycle of account context: discovering identity, listing available accounts, and switching the active account. No obvious gaps for the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to register, send/receive email, store encrypted credentials, emit audit events, and query behavioral trust scores via MCP tools.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to securely discover, invoke, and manage tools through a hardened MCP endpoint with protections like injection detection, circuit breakers, retry backoff, response caching, context-window limiting, and state snapshots.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to discover and create agents, durably submit messages with verifiable replies, and search source-linked local memory. Exposes eight authenticated tools with owner-approved OAuth, transcript-backed verification, and explicit control over history import and embedding.
      MIT