Looba MCP Server

An MCP server that gives AI assistants read-only access to Looba a community platform for UI snippets and design inspiration.

No API key required. No database credentials. The server calls the public Looba API over HTTPS.

More info

For additional MCP docs, usage examples, and updates, visit looba.dev/mcp.

Install

npx (no install needed)

npx looba-mcp

npm

npm install -g looba-mcp

pip

pip install looba-mcp

git

git clone https://github.com/looba-snippet/looba-mcp.git
cd looba-mcp
npm install

All methods require Node.js 18+ installed on your machine.

Tools

detect_frontend_context

When Looba MCP is active, the AI automatically calls detect_frontend_context at the start of a session. It looks for frontend signals:

• Dependencies — React, Vue, Svelte, Next.js, Angular, Astro, Remix, SolidJS, Gatsby, Lit, Preact…
• Config files — vite.config.ts, tailwind.config.js, next.config.js, angular.json, astro.config.mjs…
• File extensions — .jsx, .tsx, .vue, .svelte, .astro in src/, app/, pages/, components/

If a frontend project is detected, the AI uses Looba by default for any UI component request — instead of writing code from scratch.

#### Local vs remote servers

The tool takes two optional inputs:

This matters because Looba MCP is also hosted remotely at mcp.looba.dev. A remote server has no access to your filesystem, so directory alone tells it nothing.

When the tool cannot inspect the project it reports ? UNKNOWN and asks the caller to retry with packageJson — it never reports a confident "not a frontend project", because a false negative would silently switch Looba off.

propose_snippets

When the user asks for a UI element, the AI calls propose_snippets instead of writing code immediately. It searches Looba and returns 3 options with their looba.dev links. The user picks one (1, 2, or 3) and the AI integrates it via integrate_post.

Example flow:

User: "Add an animated loading spinner to my React app" → AI calls propose_snippets with query="loading spinner" and snippet_type="react" → Shows 3 options with looba.dev links → User picks option 2 → AI calls integrate_post with the chosen slug and project context

integrate_post

The integrate_post tool is designed for when you want to add a Looba snippet directly into your codebase. It fetches the full code and returns it with a detailed adaptation checklist so the AI assistant can:

• Rename CSS classes to match your naming convention (BEM, camelCase, CSS modules...)
• Replace hardcoded colors/spacing with your CSS variables or design tokens
• Convert between frameworks (vanilla HTML to React JSX, CSS to Tailwind utilities...)
• Scope styles to avoid conflicts with your global CSS
• Add proper imports and follow your component patterns

Example prompt:

"Use integrate_post to add the animated-circle-loaders-html-css-10 snippet to my Next.js project that uses Tailwind and CSS variables"

The AI will fetch the snippet, read your project context, and produce adapted code ready to paste.

Supported snippet types

Setup

Remote MCP URL

If your client supports URL-based MCP servers, use:

• URL: https://mcp.looba.dev
• Bearer token: not required
• Custom headers: not required

Use the root endpoint (https://mcp.looba.dev) unless your proxy explicitly maps another path.

Claude Code

Add to your project .mcp.json or ~/.claude/settings.json:

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

Cursor

Go to Settings > MCP Servers > Add Server:

• Name: looba
• Command: npx -y looba-mcp

Windsurf

Add to ~/.windsurf/mcp.json:

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

Using pip or git install

If you installed via pip or git clone, use looba-mcp or node directly:

{
  "mcpServers": {
    "looba": {
      "command": "looba-mcp"
    }
  }
}

Or with git clone:

{
  "mcpServers": {
    "looba": {
      "command": "node",
      "args": ["/path/to/looba-mcp/index.js"]
    }
  }
}

Examples

Once connected, ask your AI assistant things like:

• "Add a glassmorphism card to my Next.js project" (AI proposes 3 Looba options)
• "I need a navbar with animations for my Tailwind site" (AI proposes 3 Looba options)
• "Show me the most popular CSS snippets on Looba"
• "Find Looba posts tagged with animation"
• "Get the code for the post animated-circle-loaders-html-css-10"
• "List all posts by @Frontend-snippet-Bot"
• "Integrate the focus-trapped-navigation-controller snippet into my React project using CSS modules"

Every response includes source URL, author, and license so AI assistants always cite properly.

Deploying to Cloudflare Workers

mcp.looba.dev runs as a Cloudflare Worker. It serves the same seven tools over Streamable HTTP, statelessly, with no Durable Object — the tools are network-bound, so this fits the Workers Free plan. It previously ran as a systemd service behind nginx on a VPS; that stack has been removed.

Two files drive it: worker.js (the fetch entrypoint) and wrangler.jsonc. index.js is shared by both transports and needs no fork.

1. Set the secret — do this first

npx wrangler secret put LOOBA_MCP_TOKEN_SECRET

This is not optional. propose_snippets mints an HMAC-signed token that integrate_post verifies. Without an explicit secret, index.js falls back to randomBytes(32) per process — and on a stateless Worker each isolate gets a different one, so the two calls fail to agree whenever they land on different isolates. The failure is intermittent and reports a bogus "token signature is invalid".

Any long random string works, e.g. openssl rand -hex 32.

2a. Deploy from Git (Workers Builds)

Connect this repository in the Cloudflare dashboard, then set:

Every push to main then redeploys.

2b. Or deploy from your machine

npm install
npm run deploy

3. Attach the domain

Add mcp.looba.dev as a Custom Domain on the Worker. looba.dev is already on Cloudflare nameservers, so no DNS change is needed.

The Worker answers at the root path (route: "/" in worker.js), matching the existing endpoint. createMcpHandler defaults to /mcp, so that setting must not be removed or every existing client breaks.

4. Verify before switching traffic

npm run dev:worker   # local, needs .dev.vars — see .dev.vars.example

Beyond initialize and tools/list, test the pair that depends on the shared secret — mint a token with propose_snippets, restart the Worker, then spend it with integrate_post. If the token still verifies after a restart, the secret is being read from configuration rather than regenerated per process.

License

MIT