Leadcloser Mcp

io.github.dylanc1317-createPublished by GitHub account dylanc1317-createv1.0.1Updated Oct 24, 2026

Manage leads and insights for NZ trade businesses via LeadCloser AI.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

A local MCP server that lets an assistant manage leads and insights for New Zealand trade businesses through LeadCloser AI.

What you can do
Manage leads and related insights for NZ trade businesses through LeadCloser AI, as described in the registry entry. No individual tools are listed in the manifest, so the exact operations available are not documented here. It runs as a local process on the user's machine and connects over stdio.
When to use it
Consider it if you run a New Zealand trade business on LeadCloser and want an AI assistant to work with your leads and insights from within a desktop client. It is not useful without a LeadCloser tenant.
Requirements
Runs locally as an npm package over stdio, so Node.js and a desktop MCP client are needed. Requires the environment variable LEADCLOSER_TENANT_ID, described as your LeadCloser tenant ID from the provider's settings page. No authentication method is declared in the manifest.
Before you install
The server needs your LeadCloser tenant identifier (LEADCLOSER_TENANT_ID), which ties the assistant to your account's data. The manifest lists no tools, so what it can read or change in your lead data is not documented; check before letting it write or delete anything. It is desktop-only and not available as a web executable.

Installation

In SourceWeft

  1. Open Leadcloser Mcp 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.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.