How to connect Moonlit to your AI assistant

Moonlit's MCP server works with any AI tool that supports remote MCP servers. You add one URL, sign in with your Moonlit account, and that's it. No API key needed. Here's what that actually looks like across the tools people use, and where to go for the exact steps for yours.

Picture the usual workflow: you're drafting in Claude, or working through a contract in Copilot in VS Code, and you need to check whether a ruling still holds up. So you switch tabs, open Moonlit, search, read, copy the answer, switch back and paste it in, hoping you copied the right paragraph. Do that for every citation in a long brief and the tab-switching becomes work on its own.

MCP closes that gap. It lets an AI tool talk directly to an outside data source, in this case the same nightly-refreshed, enriched legal database that powers search on Moonlit. Connect once, and the tool you're already using can pull from that database on its own. You never have to leave the window you're in.

The chat apps

In Claude, the setup lives in a settings menu, not a file you have to edit. Add a custom connector, paste the URL, sign in and approve it. Once you do, it syncs across Claude's web, desktop and mobile apps right away.

On Claude's own Team and Enterprise plans, a workspace Owner adds the connector once, and everyone else just signs in.

ChatGPT works in a similar way, with two differences. Connectors sit behind Developer mode, a setting you turn on under paid plans, and sign-in runs through OAuth. On ChatGPT Enterprise and Edu, connectors are off by default until a workspace admin turns them on.

In the editor

In the editor, most of that happens in GitHub Copilot inside VS Code. Setup here works differently than it does in Claude: instead of a settings menu, you point Copilot at the server through a short config file, and sign-in starts on its own the first time it's used in agent mode.

On Copilot Business and Enterprise plans, an admin has to turn on MCP support first, since it's off by default there.

Cursor and Codex work the same way too: a short config entry pointing at the same URL, followed by a quick sign-in approval in the browser, same as everywhere else.

Claude Code, Gemini CLI, Windsurf and Zed follow the same pattern, for anyone running those. One thing to note: every tool names that setting a little differently, so a config snippet copied from a colleague on a different editor won't always paste in cleanly. Worth checking the exact wording for your tool before you copy anything over.

On every other app

Langdock, Le Chat and Perplexity all support Moonlit as a custom connector too, each with its own version of the same add-connector-then-sign-in flow.

Perplexity offers custom connectors on its Pro, Max and Enterprise plans. In Le Chat, the connector name skips spaces, so it's lowercase moonlit with no gap. Langdock lets a workspace admin share the connection with the whole team, and each person still signs in with their own Moonlit account.

Microsoft 365 Copilot connects in its own way. There's no personal sign-in at all; it connects through an agent built in Microsoft Copilot Studio, using an organization MCP key instead of an individual login.

When it doesn't work

If something doesn't connect, work through the same short checklist: check the URL ends in /mcp, remove the server entry and add it again, then sign in once more. If the connection works but something still looks off, like plan limits or quota, ask your assistant to call get_account_status. You'll get the answer right there, no separate dashboard needed.

 Still stuck? Email support@moonlit.ai with the client you're using and what you're seeing.

None of this changes what Moonlit actually is. It just means the database doesn't live in one browser tab anymore. It lives wherever you're already working. The docs have the exact setup for your specific tool, screen by screen: How to connect.