Nalogoo MCP

An MCP server that puts the Nalogoo logo catalog inside your AI client: Claude Desktop, Claude Code, Cursor, and anything else that speaks MCP. Ask for "the Unitel logo in PNG" and the official file lands on your disk, without opening a browser.

Made and officially distributed by Nalogoo.

Requires Node 20 or newer.

Install

You don't need a key to start. Copy one of the lines below and you're done. If you want to know whether you should add a key anyway, read Do I need a key? further down.

Claude Code — Mac and Linux

claude mcp add nalogoo -- npx -y nalogoo-mcp

Claude Code — Windows

claude mcp add nalogoo -- cmd /c npx -y nalogoo-mcp

Claude Desktop (claude_desktop_config.json), Cursor (mcp.json), or any other client configured with JSON:

{
  "mcpServers": {
    "nalogoo": {
      "command": "npx",
      "args": ["-y", "nalogoo-mcp"]
    }
  }
}

On Windows, swap command/args for this instead:

{
  "mcpServers": {
    "nalogoo": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "nalogoo-mcp"]
    }
  }
}

There's no separate install step. npx downloads and runs the server on the spot, always the latest published version, every time your client starts it.

Why Windows is different: on Mac and Linux, npx is a regular executable script, and any process can launch it directly. On Windows, npx is a .cmd file, and the way MCP clients usually launch processes — without going through a shell — can't find that kind of file. The symptom is always the same: the server never responds, and the client eventually gives up with a timeout error that doesn't explain why. We confirmed this live, with a real MCP client, before shipping the fix. Routing through cmd /c works because it's the Windows shell itself that knows how to open .cmd files.

Do I need a key?

Today, no. Nalogoo is running a free-access period: the server signs itself in automatically, gets an anonymous session, and every tool works. That is why the configuration above has no key in it, and it's the configuration we recommend for one person on one computer.

You'd want a key in three situations:

• The free-access period has ended. When that happens, the first tool you call answers with a message telling you so and where to get a key. Nothing breaks silently and nothing is lost — you add the key and carry on.
• You're setting this up for a team, or for a script or server that runs on its own. That's an API key.
• You already bought a Nalogoo license and want this server counted as part of it. That's a license key.

Adding a key doesn't unlock more logos. The catalog is the same either way. What changes is who the requests are attributed to, and what the limits are.

The two kinds of key

Both are pasted into the same place (see Adding a key); what differs is what they represent.

A license key is you. It's the key you get when you buy Nalogoo, it's tied to your name, and it occupies one of the seats your license paid for.

An API key is a machine. It isn't tied to a person, occupies no seat, and is meant to be pasted into a shared setup or a script — a team's shared config, a server that generates documents on a schedule, a build pipeline.

| | No key (default) | License key | API key | |---|---|---|---| | Environment variable | — | NALOGOO_LICENSE_KEY | NALOGOO_API_KEY | | Looks like | — | NLG-XXXXX-XXXXX-XXXXX-XXXXX | nlg_ak_ followed by a long string | | Who it's for | one person trying it out | one person, with a license | a team, a script, a server | | Uses up a seat? | no | yes, one | no | | Stops working when | the free-access period ends | your license expires, is suspended, or is revoked | it's revoked | | Requests allowed | 600 per 5 hours, 10 000 per 30 days | 600 per 5 hours, 10 000 per 30 days | 3 000 per 5 hours, 50 000 per 30 days | | Safe to share? | nothing to share | no — it's your identity | yes, that's the point — but see below | | If both are set | — | ignored | wins |

About seats

A Nalogoo license is counted per person, not per device. Our design plugins can tell when the same person is using several of them — Photoshop, Illustrator and Figma on the same Adobe or Figma account — and share one seat between all of them.

This server can't do that. Nothing here tells it which Adobe or Figma account you are, so when it signs in with a license key it counts as its own separate seat. If you have a three-seat license, putting your license key into this server on your own machine leaves you two seats for everything else.

That is the single most common surprise with this server, and it's the reason to prefer an API key for a team: one API key serves everyone and costs zero seats.

About the request limits

Every call to a tool is one request. Searching the catalog and listing categories usually cost nothing extra, because the catalog is cached in memory for five minutes after the first fetch.

The numbers in the table are for normal work, and normal work doesn't come close to them. Downloading two hundred logos in an afternoon is roughly two hundred requests. If you do run out, the server says so in plain words — how much was spent and when the window resets — rather than pretending the connection failed. estado_ligacao shows the current count at any time.

Separately from the quota, Nalogoo bans an IP address for 24 hours if it pulls more than 120 files in 5 minutes, which is how automated scraping looks. You don't have to think about this: the server spaces its own downloads three seconds apart so a large batch stays well under the line. A batch of fifty files takes about two and a half minutes.

If an API key leaks

An API key isn't tied to a person, which is what makes it convenient and also what makes it worth protecting: whoever holds it can use it, from anywhere, until it's revoked. Keep it out of screenshots and out of anything committed to a public repository, and if it does get out, ask support to revoke it — you'll be issued a new one and the old one stops working immediately.

The keys we hand out for this are always external keys. Internal keys exist for our own management tools and are refused on every administrative route, precisely so that a key which leaves the building carries no extra power with it.

Adding a key

Same configuration as before, with an env block. Use one of the two variables — if you set both, the API key is the one that gets used.

Claude Code

claude mcp add nalogoo -e NALOGOO_LICENSE_KEY=NLG-XXXXX-XXXXX-XXXXX-XXXXX -- npx -y nalogoo-mcp

(On Windows, -- cmd /c npx -y nalogoo-mcp, as above.)

JSON clients

{
  "mcpServers": {
    "nalogoo": {
      "command": "npx",
      "args": ["-y", "nalogoo-mcp"],
      "env": {
        "NALOGOO_LICENSE_KEY": "NLG-XXXXX-XXXXX-XXXXX-XXXXX"
      }
    }
  }
}

Restart your AI client afterwards — it reads this file when it starts.

There's no separate "activate" step: the first time the server talks to us with your key, this installation is registered automatically.

Where a key comes from: there's no automated checkout today. The key is handed to you directly, over WhatsApp or email, once payment is arranged. Questions about your key or your payment go to nalogoo.com/suporte.

All the settings

| Variable | What it's for | |---|---| | NALOGOO_LICENSE_KEY | Your license key. Optional. Uses one seat. | | NALOGOO_API_KEY | An API key. Optional. No seat, higher limits, takes priority over the license key. | | NALOGOO_DOWNLOAD_DIR | Where downloaded files are saved. Defaults to ~/nalogoo-logos. | | NALOGOO_MCP_HOME | Where this installation's identifier is stored. Defaults to ~/.nalogoo-mcp. | | NALOGOO_CDN_URL | A different server address, for a development tunnel or staging. Defaults to https://cdn.nalogoo.com. |

Tools

| Tool | What it does | |---|---| | procurar_logos | Search by name, category, or format. Ignores accents and casing. | | listar_categorias | The categories that exist, and how many logos each has. | | detalhe_logo | Formats, variants, color, description, social links. | | ver_logo | Returns the image, so the model can confirm it's the right brand. | | descarregar_logo | Saves the official file to disk and returns the path. | | estado_ligacao | Which server you're connected to, how you're signed in, your usage, and the state of your license. |

Logos are identified by slug or by name. A name that matches several results ("bank" returns fifteen) gives you back the list of candidates instead of picking one on its own: guessing wrong would mean the wrong brand ends up in your document.

Files are the official ones, stamped per request with the license that asked for them.

When something doesn't work

An MCP server that fails to start usually just shows up as missing in the client: no error, no tools, no clue. Two things to check, in this order:

1. The right command for your operating system. There's a real difference between Windows and everything else — see Install.
2. Ask the server itself. If the tools are listed but something fails, run estado_ligacao. It says which server it reached, how it's signed in, how much of the quota is used, and the state of the license. Almost every real problem is visible in those four lines.

Still stuck: nalogoo.com/suporte.

Known limits

• stdio only. Runs on the machine that's using it. A hosted version (over HTTP) would need its own authentication work, which is separate effort.
• No SVG preview. Some previews are served as SVG, and the protocol only transports images the model can actually view (PNG, JPEG, GIF, WEBP). In those cases ver_logo says a preview isn't available instead of sending bytes the client would ignore anyway. descarregar_logo still gets you the file.
• Downloads aren't counted. Same decision as our other clients: grabbing a file is a local action and shouldn't generate extra server traffic.