Setup

Max PrilutskiyCEO & Co-Founder3 min read

Connect your assistant to https://mcp.lingo.dev/mcp and sign in through your browser. The server runs a standard OAuth flow: your client opens Lingo.dev in your browser, you sign in if you aren't already and approve the connection, and the client stores the token and renews it on its own.

Run in your terminal - registers the server globally for all projects (also picked up by the Claude Code VS Code extension, which shares the same config):

bash
claude mcp add lingo --transport http https://mcp.lingo.dev/mcp --scope user

Verify with claude mcp list. Or, to manage it yourself, add to ~/.claude/settings.json or project-level .mcp.json:

json
{
  "lingo": {
    "type": "http",
    "url": "https://mcp.lingo.dev/mcp"
  }
}

The first time your assistant calls a Lingo tool, a browser window opens for sign-in. After you approve, the client stores the token and reuses it on every subsequent call. The connection stays until you remove it from your client.

Organizations

The connection acts as you, with your permissions, in every organization you belong to - no organization is picked at sign-in. If you belong to one organization, your assistant uses it. If you belong to several, it asks once which one to work in and keeps using it; to switch, tell it which organization you mean.

New to Lingo.dev?

If you don't have an account yet, you create one and approve the connection. Your assistant finishes connecting in a new tab, while this tab continues with setup in the web app: name your organization, choose your integrations, invite teammates, and create your first engine, which lingo.dev fills from your website. You can skip integrations and teammates. Until you finish, your assistant's Lingo tools reply with a link to setup on lingo.dev, which opens the step you're on. After that, your assistant works normally and can create more engines.