Cerver

io.github.eyal-gorPublished by GitHub account eyal-gorv0.1.1Updated Nov 5, 2026

AI backend for your app: a chat per customer, replies with their cost, spend caps per project.

VerifiedSTDIODesktop onlyDeveloper Tools AI & ML

Server details

Identifier: io.github.eyal-gor/cerver
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Nov 5, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account eyal-gor for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.eyal-gor%2Fcerver.svg)](https://sourceweft.com/mcp/io.github.eyal-gor%2Fcerver?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Cerver MCP lets an assistant open per-customer chat sessions, send messages, and see each reply's cost, backed by a Cerver project key.

What you can do: Open a chat session for one of your end-customers and get a session_id
Send a message in that session and receive the assistant's reply plus what the message cost
Check which Cerver project the configured key is bound to, including project slug and scope
When to use it: Useful when you are building an app on Cerver's AI backend and want an assistant to exercise or drive per-customer chat sessions while tracking spend. It is a developer-facing tool for testing and operating a Cerver project rather than a general chat client.
Requirements: Runs as a local stdio process from the npm package @cerver/mcp, so Node.js is needed. Requires a Cerver project key supplied in the CERVER_KEY environment variable, obtained from the Cerver dashboard. Network access to Cerver is implied.

Before you install

The CERVER_KEY project key is a secret that grants access to your Cerver project; keep it out of shared configs and logs. Sending messages consumes paid Cerver usage attributed to the end-customer, so conversations and costs are recorded on Cerver's side.

Installation

In SourceWeft

Open Cerver in the dashboard and add it to a workspace.
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.

Tools

open_chat

Open a Cerver chat session for one of your end-customers. Returns a session_id to pass to send_message. Cerver stores the conversation and attributes cost to this customer.

Parameterscustomer_idrequired

send_message

Send a message in a Cerver chat session and get the assistant's reply plus what the message cost.

Parametersmodelmessagerequiredsession_idrequired

whoami

Show which Cerver project this key is bound to (project slug + scope).

Takes no parameters.

Version history

v0.1.1LatestNov 5, 2026

Score

65% 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
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 listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.