Luca Mcp

io.github.leonardomsoPublished by GitHub account leonardomsov0.1.1Updated Oct 24, 2026

Work your Luca workspace from any MCP client: 67 tools for leads, conversations, and campaigns.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Lets an assistant work inside a Luca workspace, with 67 tools covering leads, conversations, and campaigns.

What you can do
Luca MCP exposes a Luca workspace to any MCP client through 67 tools, grouped around leads, conversations, and campaigns. It runs locally over stdio and talks to the Luca API, so an assistant can read and act on workspace data rather than only discuss it. The manifest does not list individual tool names, so exact operations are not documented here.
When to use it
Worth adding when you already use Luca and want an assistant to handle workspace tasks such as working with leads, conversations, or campaigns without switching apps. It is less useful if you do not have a Luca account or developer API key.
Requirements
Runs as a local process on the user's machine via the npm package @setluca/mcp over stdio, so Node.js is needed. Requires a Luca developer API key supplied as the LUCA_API_KEY environment variable. The optional LUCA_API_BASE_URL variable sets the API origin and defaults to the Luca API host; LUCA_WORKSPACE_SLUG optionally sets a default workspace. Network access to the Luca API is required. Desktop only.
Before you install
The server needs a Luca developer API key, passed as LUCA_API_KEY, which grants access to your workspace; treat it as a secret and avoid exposing it in logs or shared configuration. With 67 tools spanning leads, conversations, and campaigns, some operations likely create, update, or send data in your Luca workspace, so review what the assistant is allowed to do before enabling it broadly. The optional LUCA_API_BASE_URL can point the server at a non-default origin, which would send your API key…

Installation

In SourceWeft

  1. Open Luca 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. 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.