Larvabot

com.larvabotPublished by larvabot.comOfficial publisherv1.2.0Updated Oct 24, 2026

Ask Claude or any MCP client about your Larvabot leads and buyer-intent conversations, read-only.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Read-only MCP access to Larvabot leads and buyer-intent conversations, so an assistant can answer questions about them.

What you can do
  • Ask an assistant about your Larvabot leads and buyer-intent conversations.
  • Retrieve lead and conversation information in a read-only way, so answers are based on your Larvabot data rather than guesses.
  • No individual tools are listed in the manifest, so the exact queries available are not documented here.
When to use it
Useful when your team tracks leads and buyer-intent conversations in Larvabot and you want an assistant to look things up in that data while you work, without switching to the Larvabot app.
Requirements
A remote MCP endpoint at app.larvabot.com over streamable HTTP. Authentication is required: either OAuth sign-in or a Larvabot API key (lb_...) from Settings > Integrations, sent in the X-API-Key header. No local runtime or environment variables are needed.
Before you install
The API key is a secret; keep it out of shared configs and logs. Access is described as read-only, but the assistant can still read your lead and conversation data, so review what is exposed before connecting. Data is served by a third-party service, Larvabot.

Installation

In SourceWeft

  1. Open Larvabot 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/com.larvabot%2Flarvabot/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": {
    "larvabot": {
      "type": "http",
      "url": "https://app.larvabot.com/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

2
  1. v1.2.0LatestOct 12, 2026
  2. v1.1.0Oct 11, 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.