@lucairn/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | OpenAI API key (sk-...). Used for gpt-* / openai-* / o1-* / o3-* / o4-* models. BYOK — Lucairn does not store it. | |
| LUCAIRN_API_KEY | No | Lucairn API key starting with lcr_live_. Get one free at https://lucairn.eu/account/signup | |
| ANTHROPIC_API_KEY | No | Anthropic API key (sk-ant-...). Used for claude-* / anthropic-* models. BYOK — Lucairn does not store it. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chat_via_lucairnA | Send a chat request through the Lucairn privacy gateway with cross-provider BYOK (Anthropic + OpenAI). PII is detected and replaced with placeholders before reaching the upstream LLM. The gateway picks the upstream provider based on the |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguous selection. The single tool clearly defines its action and scope, so agents cannot confuse it with anything else.
The sole tool name, `chat_via_lucairn`, follows a clean snake_case verb-phrase convention. There are no other names present, so there are no conflicting naming styles to navigate.
One tool is slightly below the typical 3–15 tool range, but it is a substantial operation rather than a trivial placeholder. For a narrow privacy-gateway chat use case, the single-tool scope is reasonable.
The tool fully covers the server's apparent purpose: sending chat requests through the Lucairn gateway with provider routing and PII handling. There are no dead ends in the core workflow, and configuration concerns are handled through parameters and environment keys.