Claude Code
Add Lahuta to Claude Code with one command, sign in from the /mcp menu and choose which tools run without asking.
Claude Code is Anthropic's coding assistant for the terminal. With Lahuta connected, it can work with your Lahuta data while you build: pull an event's registrations into a script, create test contacts, or draft a blog post from your changelog.
Add the server
Run this in your terminal:
claude mcp add --transport http lahuta https://api.lahuta.org/mcpBy default, Claude Code adds the server to the current project only, and only for you. The --scope option changes that:
| Scope | Where Lahuta is available | Stored in |
|---|---|---|
local (default) | This project, only for you | ~/.claude.json |
project | This project, for everyone who clones it | .mcp.json in the project folder |
user | Every project on your computer, only for you | ~/.claude.json |
To use Lahuta in all your projects:
claude mcp add --transport http --scope user lahuta https://api.lahuta.org/mcpA project scope shares only the server address. Each teammate still signs in with their own Lahuta account and gets their own role.
Sign in
Start Claude Code and run /mcp.
Select lahuta. Until you sign in, it shows as needing authentication. Follow the prompt to authenticate.
Your browser opens at Lahuta's sign-in page. Sign in with your Lahuta account. If you belong to more than one organization, choose the one Claude Code should use by default.
Back in the terminal, /mcp shows Lahuta as connected. Claude Code keeps you signed in and renews the sign-in on its own.
You can also sign in from your shell with claude mcp login lahuta. On a machine without a browser, add --no-browser and it prints a link to open elsewhere.
Manage the server
claude mcp list # every server and whether it's connected
claude mcp get lahuta # details for Lahuta
claude mcp remove lahuta # remove itTo sign in as someone else, or to pick a different default organization, open /mcp, select lahuta, choose Clear authentication and sign in again.
Approvals
Claude Code asks before it runs a tool you haven't allowed. When it asks about a Lahuta tool, it's fine to allow the read-only ones for the session or permanently, such as contacts_list, events_registrations_list or products_orders_list. For tools that send email, publish or delete, approve each run so you see the arguments first. The Tools reference flags those.
Tip
Claude Code sees your code and your Lahuta data at the same time. That's handy, but say which one you mean. "Add a contact for jess@example.com in Lahuta" is clearer than "add Jess".