Connect your assistant to https://mcp.lingo.dev/account and sign in through your browser. No API key copy-paste - the server runs a standard OAuth flow, you pick the organization on the consent screen, and the access token is cached locally by your client.
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):
claude mcp add lingo --transport http https://mcp.lingo.dev/account --scope userVerify with claude mcp list. Or, to manage it yourself, add to ~/.claude/settings.json or project-level .mcp.json:
{
"lingo": {
"type": "http",
"url": "https://mcp.lingo.dev/account"
}
}The first time your assistant calls a Lingo tool, a browser window opens for sign-in and consent. After you approve, the token is stored by the client and reused on every subsequent call.
Organization scope
The consent screen lets you pick which organization the MCP server should manage. Your assistant never needs to specify an organization ID - every tool operates within the organization you approved. To switch organizations, remove the connection and add it again.