MCP

Adding MCP servers to Lucid Train.

Registry search or a command and some environment variables. Anything that speaks stdio.

Download for macOS
v0.1.33 · .dmg · Apple Silicon & Intel
Signed & notarized by Apple · opens without a Gatekeeper warning
sha256 698955a0187bc039f4c74f5d05a9f10fbb27376a45788a0a241d1326b73873c7
Download for Windows instead
$curl -fsSL https://lucidtrain.com/install.sh | sh

Lucid Train's Connectors tab adds MCP servers two ways: searching the official MCP Registry, or entering a command, arguments and environment variables manually. Any stdio server works, including Atlassian's official one. Four provider connectors ship built in: GitHub, Vercel, Railway and Grafana, where Grafana also brings Loki and Prometheus querying through its own MCP server.

Two ways to add one

Discover queries the official MCP Registry and lists what it finds, with a fallback to web search. Manual takes a name, a command, its arguments and any environment variables as key-value rows, which is the path for anything not in the registry or anything internal. Configuration lands in your config file with restricted permissions.

What ships built in

GitHub, Vercel and Railway are auth-status connectors that wrap the vendor CLI, detecting whether it is installed and who is logged in, and delegating login. Grafana is the deep one: it downloads the Grafana MCP binary, stores credentials in the OS keychain, and registers it, which is how Loki log queries and Prometheus metric queries reach the agent.

Servers reach the other CLIs too

Whatever you configure is re-rendered into the native format each execution engine expects, so the same connectors are available whether a turn runs on Lucid Train's own agent, Claude Code, Codex or Cursor. You configure once rather than per CLI.

Transport

Connections are stdio: the server runs as a local child process with piped stdin and stdout. Remote HTTP and SSE servers appear in the Connectors tab's registry search but cannot be connected, and that is a real limit rather than a configuration step you are missing. A remote server needs a local stdio bridge in front of it.

Atlassian, stated precisely

There is no Jira or Confluence specific code in Lucid Train. What is true today is that the manual form accepts any command, so Atlassian's official MCP server can be added the same as any other stdio server, provided it runs locally. First-party Jira and Confluence integration, with the setup and auth handling that implies, is on the roadmap and is not shipping.

What is built in versus what you add

ConnectorHow it works
GitHubBuilt in, wraps the gh CLI for auth status and login
VercelBuilt in, wraps the vercel CLI
RailwayBuilt in, wraps the railway CLI
GrafanaBuilt in, downloads and registers the Grafana MCP server
Loki and PrometheusThrough the Grafana server's tools
Atlassian, Linear, Notion, othersAdd the vendor's stdio MCP server yourself
Internal or custom serversManual: command, args, environment
FAQ

Questions

Can I add any MCP server?

Any stdio MCP server, by registry search or by entering the command manually. Remote HTTP and SSE endpoints cannot be connected.

Does Lucid Train integrate with Jira or Confluence?

Not natively today. You can add Atlassian's own stdio MCP server from the Connectors tab. First-party integration is on the roadmap.

Do connectors work when a turn runs on Claude Code or Codex?

Yes. Configured servers are re-rendered into each CLI's native MCP configuration, so you set them up once.

Where are credentials stored?

In the OS keychain, not in the config file. The config file itself is written with restricted permissions.

Related