Your skills badge, asked for in plain language.

The server has two tools, both read-only. They change nothing and call no outside service, because the data for all 756 icons is built into the Worker.

Server address: https://skill-icons.alanreisanjo.workers.dev/mcp

Install

Pick your client. No key or account needed.

Claude Code

Run it in the terminal, inside the project (or with --scope user for every project):

claude mcp add --transport http skill-icons https://skill-icons.alanreisanjo.workers.dev/mcp

Cursor

Add it to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "skill-icons": {
      "url": "https://skill-icons.alanreisanjo.workers.dev/mcp"
    }
  }
}

VS Code

Add it to .vscode/mcp.json:

{
  "servers": {
    "skill-icons": {
      "type": "http",
      "url": "https://skill-icons.alanreisanjo.workers.dev/mcp"
    }
  }
}

Other client

Any client that supports remote MCP servers over HTTP (Streamable HTTP). Paste the address as a custom server or connector; there is no authentication.

https://skill-icons.alanreisanjo.workers.dev/mcp

skill_icons_search

Searches the 756 available icons and returns the id to use in the badge. With neither query nor category, it lists them all.

skill_icons_badge

Builds the badge from a list of names written the way people write them, and returns the URL, the Markdown and the HTML, ready to paste.

Why use the MCP instead of building the URL by hand

The image API drops invalid ids without a word, and the badge just comes out with icons missing. skill_icons_badge resolves each name the way it was written, says what doesn’t exist and suggests the right spelling.

Prefer clicking? Open the builder →

MCP server · skill-icons 26.11.1

Your skills badge, asked for in plain language.

The server has two tools, both read-only. They change nothing and call no outside service, because the data for all 756 icons is built into the Worker.

  • Streamable HTTP
  • stateless
  • no sign-in
  • 2 tools · read-only
Server address
https://skill-icons.alanreisanjo.workers.dev/mcp

Install

Pick your client. No key or account needed.

Run it in the terminal, inside the project (or with --scope user for every project):

claude mcp add --transport http skill-icons https://skill-icons.alanreisanjo.workers.dev/mcp

skill_icons_badge

read-only

Builds the badge from a list of names written the way people write them, and returns the URL, the Markdown and the HTML, ready to paste.

Parameters

iconsrequiredstring[], at least 1 · default —
Icons in the order they should appear.
themeoptional"dark" | "light" · default "dark"
Background for icons that have a light and a dark version.
perLineoptionalinteger, 1 to 50 · default 15
Icons per line.

How each name is resolved, in this order

  1. 1typescript — exact id
  2. 2ts → typescript · postgres → postgresql · k8s → kubernetes — alias
  3. 3C++ → cpp · Google Cloud → gcp — brand name, case-insensitive
  4. 4node.js → nodejs — normalized form
  5. 5node → nodejs — normalized form with js at the end

Repeated icons are removed and the first one wins. The URL uses each icon’s shortest name and leaves out parameters set to their default.

Example · input

{
  "icons": [
    "typescript",
    "Node.js",
    "C++",
    "postgres",
    "ts"
  ],
  "theme": "light",
  "perLine": 4
}

Example · response

{
  "url": "https://skill-icons.alanreisanjo.workers.dev/icons?i=ts,nodejs,cpp,postgres&theme=light&perline=4",
  "markdown": "[![My Skills](https://skill-icons.alanreisanjo.workers.dev/icons?i=ts,nodejs,cpp,postgres&theme=light&perline=4)](https://skill-icons.alanreisanjo.workers.dev)",
  "html": "<p align=\"center\">\n  <a href=\"https://skill-icons.alanreisanjo.workers.dev\">\n    <img src=\"https://skill-icons.alanreisanjo.workers.dev/icons?i=ts,nodejs,cpp,postgres&theme=light&perline=4\" />\n  </a>\n</p>",
  "icons": [
    "typescript",
    "nodejs",
    "cpp",
    "postgresql"
  ]
}

The repeated ts left the list because typescript was already in it.

Unknown names

The icons that exist stay in the badge. The ones that don’t show up in unknown, each with up to 5 suggestions:

{
  "url": "https://skill-icons.alanreisanjo.workers.dev/icons?i=react",
  "markdown": "[![My Skills](https://skill-icons.alanreisanjo.workers.dev/icons?i=react)](https://skill-icons.alanreisanjo.workers.dev)",
  "html": "<p align=\"center\">\n  <a href=\"https://skill-icons.alanreisanjo.workers.dev\">\n    <img src=\"https://skill-icons.alanreisanjo.workers.dev/icons?i=react\" />\n  </a>\n</p>",
  "icons": [
    "react"
  ],
  "unknown": [
    {
      "input": "reactt",
      "suggestions": [
        "react",
        "preact",
        "reactos"
      ]
    },
    {
      "input": "zzzzzz",
      "suggestions": []
    }
  ]
}

If no name exists

The response is flagged as an error (isError: true):

{
  "error": "None of the icons exist.",
  "unknown": [
    {
      "input": "zzzzzz",
      "suggestions": []
    }
  ]
}

Why use the MCP instead of building the URL by hand

The image API drops invalid ids without a word, and the badge just comes out with icons missing. skill_icons_badge resolves each name the way it was written, says what doesn’t exist and suggests the right spelling.

Prefer clicking? Open the builder →