Ebenova Fieldops

io.github.dgtalquantumleap-aiPublished by GitHub account dgtalquantumleap-aiv1.0.2Updated Oct 24, 2026

WhatsApp booking, staff coordination, and invoice recovery for services.

VerifiedSTDIODesktop onlyDatabasesCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

A local MCP server for WhatsApp booking, staff coordination, and invoice recovery in service businesses.

What you can do
Ebenova Fieldops is a local MCP server that connects an assistant to a PostgreSQL database backing field-service operations. According to its registry description, it covers WhatsApp booking, staff coordination, and invoice recovery for services. No tool list is published, so the exact operations exposed are not documented in the available material.
When to use it
Consider it when a service business already runs its booking, scheduling, and invoicing data in PostgreSQL and wants an assistant to work with that data alongside WhatsApp-based customer conversations. It is a poor fit if you need a documented tool surface or a hosted endpoint, since none is described.
Requirements
Runs as a local process over stdio, installed from the npm package @ebenova/fieldops-mcp, so Node.js and npm are needed. It requires the environment variable DATABASE_URL, a PostgreSQL connection string, and network access to that database. Desktop only; no web executable. No authentication is declared.
Before you install
The server needs DATABASE_URL, a PostgreSQL connection string that typically embeds a username and password; treat it as a secret and avoid exposing it in logs or shared configuration. Because the description mentions booking, coordination, and invoice recovery, the assistant may read or change operational and customer records, so review what it can write before use. No tool list is published, so verify the actual capabilities yourself.

Installation

In SourceWeft

  1. Open Ebenova Fieldops 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

This repository has no README.

Tools

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

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

25% 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

    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.