Luca Mcp

io.github.setlucaPublished by GitHub account setlucav0.7.1Updated Nov 7, 2026

SetLuca DM sales from any MCP client: 208 API tools and 15 task tools for leads, replies, calls.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Connects an AI assistant to a SetLuca DM sales workspace so it can review leads, draft replies, and help with calls and broadcasts.

What you can do
  • Review what needs attention, including the review queue and recommended approvals
  • Look up leads and pull together everything about a lead before a call
  • Draft replies for leads, which wait in the review queue for approval
  • Send messages, launch broadcasts and book calls, each requiring explicit confirmation
  • Check broadcast performance and other workspace activity
  • Access a large set of SetLuca API tools and task tools across the workspace
When to use it
Useful if you run DM sales in SetLuca for coaching, creator or expert work and want an assistant to triage the queue, prepare for calls, and draft replies without leaving the chat client.
Requirements
Either the remote endpoint with sign-in (no API key needed) or the npm package run locally with Node.js 20 or newer. The local path needs a SetLuca developer API key in LUCA_API_KEY (or LUCA_API_TOKEN), created under Settings, Developer API keys. Optional settings include LUCA_WORKSPACE_SLUG or LUCA_WORKSPACE_ID to pick a workspace, LUCA_API_BASE_URL, LUCA_AUTH_HEADER, LUCA_REQUEST_TIMEOUT_MS and LUCA_TOOLSET.
Before you install
The API key grants access according to its scopes and should be kept out of prompts, screenshots and committed files; revoke it in SetLuca settings if exposed. Tools that send a message, launch a broadcast or book a call act on real leads and are meant to require your confirmation, so check what you approve. Sign-in connections start with read and draft access, with anything more chosen at sign-in. Results are passed to your assistant's provider under its own privacy policy.

Installation

In SourceWeft

  1. Open Luca Mcp 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/io.github.setluca%2Fluca-mcp/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": {
    "luca": {
      "type": "http",
      "url": "https://mcp.setluca.com/mcp"
    }
  }
}

README

SetLuca MCP server

SetLuca runs DM sales for coaches, creators, and experts. This MCP server connects your SetLuca workspace to an AI assistant such as Claude, ChatGPT, or Cursor, so you can ask it what needs attention and get help with the work waiting there.

Once you're connected, try asking:

  • "What needs my attention this morning?"
  • "Show me the review queue and recommend what to approve."
  • "Pull up everything about this lead before my call."
  • "Draft a short, warm reply for this lead."
  • "How is my broadcast performing?"

Connect your assistant

There are two ways to connect. The connection guide helps you pick the one your assistant supports.

Sign in with SetLuca

If your assistant supports custom connectors, as Claude and ChatGPT do, add this URL:

text
https://mcp.setluca.com/mcp

Then sign in to SetLuca and choose what the assistant may do. You don't need an API key.

Use an API key

If your assistant runs MCP servers on your computer, you need Node.js 20 or newer.

  1. Create a key in SetLuca → Settings → Developer API keys.

  2. Add this to your assistant's MCP configuration:

    json
    {  "mcpServers": {    "luca": {      "command": "npx",      "args": ["-y", "@setluca/mcp"],      "env": { "LUCA_API_KEY": "luca_..." }    }  }}

Keep the key out of prompts, screenshots, and committed files. If it can reach more than one workspace, set LUCA_WORKSPACE_SLUG to choose one. Client setup has more on this path, including the Claude Code command.

What your assistant can do

  • Read and draft, unless you allow more. A sign-in connection starts with read and draft access, and you choose anything beyond that when you sign in. An API key can do what its scopes allow.
  • Reach a lead only with your approval. A tool that sends a message, launches a broadcast, or books a call refuses to run without a confirmation. Your assistant is told to confirm only after you approve that exact action.
  • Leave drafts for you to review. A reply your assistant drafts waits in your SetLuca review queue until you approve it.

Your data

Your assistant only sees what your access allows. This server keeps no copy of your workspace data: it passes each request to SetLuca and returns the result. It logs a tool's name, whether it succeeded, and how long it took, and leaves out API keys, message text, tool arguments, and drafted replies.

Your assistant's provider handles those results under its own privacy policy, so read that before connecting a live workspace. SetLuca's privacy policy covers how SetLuca handles your data.

Manage your connection

  • Disconnect an assistant in SetLuca → Settings → Connected agents.
  • Revoke an API key in SetLuca → Settings → Developer API keys.
  • If a connection stops working, check the connection guide and the error guide.
  • For anything else, email [email protected].

For developers

ToRead
Browse every tool, prompt, and resourceTools, Prompts and resources
See what each permission allowsScopes
Call SetLuca without MCPSetLuca API docs
Work on this serverDocumentation index, and AGENTS.md if you're a coding agent
See what changed in a versionChangelog, which also lists renamed tools that may affect saved prompts

To run every check from a clone:

bash
bun install --frozen-lockfilebun run verify

Licensed under the Apache License 2.0.

Source: README.md at commit 47b5854

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

8
  1. v0.7.1LatestNov 7, 2026
  2. v0.6.0Oct 24, 2026
  3. v0.5.2Oct 23, 2026
  4. v0.5.1Oct 22, 2026
  5. v0.4.0Oct 13, 2026
  6. v0.3.5Oct 6, 2026
  7. v0.3.0Oct 5, 2026
  8. v0.2.1Sep 16, 2026

Score

85% 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
  • License10 pts