octapi

app.octapiPublished by octapi.appv0.1.1Updated Oct 24, 2026

A business's WhatsApp front desk as tools: inbox, customers, catalogue, bookings, fees.

Overview

AI-generated overview

Connects an assistant to a business's WhatsApp front desk — inbox, customers, catalogue, bookings and fees — as MCP tools.

What you can do
  • Work the WhatsApp inbox and conversations for a business.
  • Look up and manage customer records.
  • Browse and maintain the product or service catalogue.
  • Handle bookings and the fees attached to them.
  • Consumer-side tools let the assistant find and book with listed businesses, even without an API key.
When to use it
Useful when a business runs its customer conversations, catalogue and bookings through this WhatsApp front desk and wants an assistant to read or act on that data. Also relevant for consumers who want an assistant to find and book with businesses listed on the platform.
Requirements
Runs locally over stdio, launched with npx from the npm package octapi-mcp, so Node.js is needed. Desktop only; no web executable. A brand API key from Account → API keys is supplied through the OCTAPI_API_KEY environment variable; it is optional for the consumer find-and-book tools.
Before you install
The brand API key is a secret passed in the OCTAPI_API_KEY environment variable and grants access to a business's inbox, customers, catalogue and bookings. Tools act on live customer conversations and booking data, so writes or messages may reach real customers. Consumer tools work without a key, but the brand tools should be treated as production access.

Installation

In SourceWeft

  1. Open octapi 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. v0.1.1LatestSep 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.