Read time: ~5 minutes · Series: Platform Admin (Data Engineering) advanced · Previous: External Agent Integration · Next: Backup and common issues
When you need MCP Sources
This is not Agent Integration. MCP Sources lets Lantide connect to an external data service; Agent Integration in the top-right lets an external Agent connect into Lantide. To set up Cursor, Codex, or Claude, read Safely connecting an external AI Agent to Lantide.
Connections are for standard databases and data sources (PostgreSQL / MySQL / SQLite, folders, and SQL Server). MCP Sources brings in other data or APIs over MCP and materializes them into queryable tables in the sidebar.
If the team only has Postgres + local CSV, you can skip MCP for now. Once analysis needs exceed direct traditional-DB connections, you and the analyst can evaluate it.
Your responsibilities (overview)
- Open management via the gear / + in the MCP Sources section
- Configure
stdio(launch command) orhttp(URL, Token, Headers) - Test → Add (newly added defaults to
disconnected) - Connect until
connected - Analysts explore materialized tables via Start in Chat → Scan Source or through conversation
Agent control (optional): The built-in Agent and external Agents use the same source registry. Execute can Test, Connect, Explore, and materialize; Admin can add, replace credentials, and Remove. Credentials are never shown again and risky actions require confirmation.
For the full UI and states, see USER_GUIDE §4.6.
How to read the status
| Status | Meaning |
|---|---|
connected |
Usable; materialized tables visible in the sidebar |
disconnected |
Configured but not connected |
error |
Recent test/reconnect failed; check the card message and Toast |
After restart or returning to the workspace, each previously connected source gets one automatic reconnect attempt. A source you explicitly disconnected is not retried. When disconnected / error, there's a yellow warning next to the name; you can right-click the source row to Connect.
Division of labor with analysts
- You: source setup, network and credentials, Test / Connect
- Analysts: scanning sources, deciding which tables to materialize, using them in the Plan
Exporting a Workspace can optionally include the MCP cache; after import you still need to Reconfigure MCP and reconnect.
One thing you can do right now
If you don't need MCP for now, note in the team wiki "currently using Connections only"; if you do, complete Test → Add → Connect on one test machine before rolling it out.