Keepline

app.keeplinePublished by keepline.appOfficial publisherv1.0.0Updated Oct 29, 2026

Team WhatsApp inbox: read chats and contacts; every send needs a person's confirmation.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Keepline is a remote MCP server for a team WhatsApp inbox, letting an assistant read chats and contacts while every send requires a person's confirmation.

What you can do
  • Read team WhatsApp chats and conversations
  • Look up contacts in the shared inbox
  • Draft or prepare outgoing messages, with each send gated on a person's confirmation
When to use it
Useful when a team handles WhatsApp conversations through a shared inbox and wants an assistant to look up chats and contacts or prepare replies, while keeping a human in the loop before anything is sent.
Requirements
A remote endpoint at keepline.app over streamable HTTP; OAuth authentication is required, so a Keepline account with access to the team inbox is needed. No environment variables or headers are declared.
Before you install
The assistant can read team WhatsApp conversations and contact data, which is sensitive customer information. Sending is described as requiring a person's confirmation, but verify how that approval works before relying on it; chat content is handled by a third-party service.

Installation

In SourceWeft

  1. Open Keepline in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.keepline%2Fkeepline/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "keepline": {
      "type": "http",
      "url": "https://keepline.app/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.