Awesome Core MCP Server

What the code does

We read the source, 5 d ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

        result = subprocess.run(

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        result = subprocess.run(

        <select name="lang">
            <option value="">dowolny język</option>
            {% for name, count in langs %}<option value="{{ name }}" {% if filters.lang == name %}selected{% endif %}>{{ name }} ({{ count }})</option>{% endfor %}

# Baza (data/awesome.db) i README list (offline-db/) są w .gitignore, więc
# trzeba je odtworzyć w trakcie builda: najpierw pobranie list z GitHuba,
# potem zbudowanie bazy. Token jest opcjonalny — bez niego GitHub limituje
# wyszukiwanie, ale build i tak się kończy.
ARG GITHUB_TOKEN=""

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add awesome-core -- uvx awesome-core

{
  "mcpServers": {
    "awesome-core": {
      "command": "uvx",
      "args": [
        "awesome-core"
      ]
    }
  }
}

[mcp_servers.awesome-core]
command = "uvx"
args = ["awesome-core"]

{
  "mcpServers": {
    "awesome-core": {
      "command": "uvx",
      "args": [
        "awesome-core"
      ]
    }
  }
}

{
  "servers": {
    "awesome-core": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "awesome-core"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: AWESOME_DATA_DIR (Katalog z gotową bazą awesome.db (zbudowaną przez ./awesome start)).