Developer · Remote MCP server
Luca MCP
Work your Luca workspace from any MCP client: 183 API tools + 15 task tools for leads and calls.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.setluca/luca-mcp- Version
- 0.2.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-22
- Updated
- 2026-08-22
- Publisher
- setluca (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/setluca) · how
- Website
- setluca.com/developers
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.setluca.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @setluca/mcp | 0.2.1 | stdio |
How to connect Luca MCP
Luca MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.setluca.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @setluca/mcp version 0.2.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @setluca/mcp@0.2.1. It reads these environment variables: LUCA_API_KEY (required, secret), LUCA_API_TOKEN (secret), LUCA_API_BASE_URL, LUCA_AUTH_HEADER, LUCA_WORKSPACE_ID, LUCA_WORKSPACE_SLUG, LUCA_REQUEST_TIMEOUT_MS and LUCA_TOOLSET; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"luca-mcp": {
"command": "npx",
"args": [
"-y",
"@setluca/mcp@0.2.1"
],
"env": {
"LUCA_API_KEY": "<secret>",
"LUCA_API_TOKEN": "<secret>",
"LUCA_API_BASE_URL": "<value>",
"LUCA_AUTH_HEADER": "<value>",
"LUCA_WORKSPACE_ID": "<value>",
"LUCA_WORKSPACE_SLUG": "<value>",
"LUCA_REQUEST_TIMEOUT_MS": "<value>",
"LUCA_TOOLSET": "<value>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| LovecPrompt-injection detector for untrusted text before it reaches an LLM (RU/EN). BYO lovec.tech key. | Local · stdio |
| LowlandData Developer ToolsDependency releases, TLS and domain expiry, and vendor status pages from one endpoint. | Remote · HTTPLive check: sign-in required |
| Ls SearchDisposable private vector search + semantic RAG for AI agents. x402 pay-per-call, no account. | Remote · HTTPLive check: ✗ no handshake |
| luLu.ma events MCP server with draft+confirm safety, audit logging, and prompt-injection scrubbing.… | Local · stdio |
| Lucairn MCP ServerPseudonymizes PII before your LLM and returns a cryptographically signed receipt per response. | Local · stdio |
| Lucius MCPMCP server for managing Allure TestOps tests, launches, plans, defects, and metadata. | Local · stdio |
| LuminRead-only access to a Lumin project's logs, metrics, uptime checks, alerts and infrastructure. | Remote · HTTPLive check: sign-in required |
| Lumino MCP ServerAI-powered SRE observability for Kubernetes/OpenShift with 40+ Tekton debugging tools. | Local · stdio |