---
title: Gemini CLI Favicon Install Guide
description: Install a complete favicon set with Google's Gemini CLI: connect a generator via MCP or a CLI, then let the agent place the files, wire the head, and verify each path.
canonical: https://favicontools.com/gemini-cli/favicon-install
---

# Gemini CLI Favicon Install Guide

Gemini CLI is an open-source terminal agent with a large context window and first-class MCP support, so it can read a whole project and wire an icon set across several files without losing the plot. What it can't do is render the artwork. Point it at an MCP server or a CLI that emits real files, and let Gemini handle the placement, the head, and the verification.

## Why it matters

- **Use its MCP support for the bytes** — Gemini CLI speaks MCP natively. Wire in a favicon generator as a server and the whole job (generate, install, patch) happens inside one conversation instead of a copy-paste dance.
- **Big context, so let it read first** — It can hold the whole repo at once, so ask it to find how icons are currently referenced before it edits anything. That's what stops a second, competing set of link tags.

## Playbook

1. **Give it a way to make real files** — Connect a generator over MCP, or run a CLI that writes the kit into the project, so Gemini is wiring around files that exist rather than inventing filenames.
2. **Scope the edit to head and manifest** — Tell it exactly which files to touch. On a broad prompt, Gemini CLI will cheerfully refactor adjacent code; a scoped instruction keeps the change to the icons.
3. **Have it fetch every icon path** — It has a shell. Ask it to start the dev server and request each icon URL, confirming a 200 and an image content type before you accept anything.

## Checklist

- Record the icon convention in GEMINI.md so later sessions don't re-add a starter template favicon.
- If you wired a generator over MCP, name the server in GEMINI.md so regenerating is one instruction.
- Confirm the manifest.json icons array matches the filenames and sizes that actually shipped.

## FAQ

### Can Gemini CLI create favicon images?

The model outputs text, so no, it can't produce the PNG or ICO bytes on its own. Give it a generator to call, over MCP or as a CLI, and it will drive generation, placement, and the head markup end to end.

### How does MCP help with favicons here?

MCP lets Gemini CLI call an external tool as if it were built in. Connect a favicon generator as an MCP server and the agent can request a real icon set and receive actual files, closing the one gap a language model can't fill itself: image bytes.

### Should icons go in app/ or public/?

It depends on the framework, and Gemini can tell by reading the repo. Next.js App Router picks up app/icon.png automatically; Vite and most SPAs want the files in public/ with explicit link tags. Keep favicon.ico at the root either way for crawlers that request it by path.