Context Awesome

MCP server for accessing curated awesome list documentation

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
95%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~539Tokens (tool definitions)
~1.8 KBTypical response size
Minimal attention impact (0.42% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "context-awesome": {
      "command": "npx",
      "args": [
        "context-awesome"
      ]
    }
  }
}

Runnable packages

npmcontext-awesome0.1.1stdio

Remote endpoints

https://www.context-awesome.com/api/mcpstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢find_awesome_section(query, confidence, limit)

Discovers sections/categories across awesome lists matching a search query and returns matching sections from awesome lists. You MUST call this function before 'get_awesome_items' to discover available sections UNLESS the user explicitly provides a githubRepo or listId. Selection Process: 1. Analyze the query to understand what type of resources the user is looking for 2. Return the most relevant matches based on: - Name similarity to the query and the awesome lists section - Category/section relevance of the awesome lists - Number of items in the section - Confidence score Response Format: - Returns matching sections of the awesome lists with metadata - Includes repository information, item counts, and confidence score - Use the githubRepo or listId with relevant sections from results for get_awesome_items For ambiguous queries, multiple relevant sections will be returned for the user to choose from.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Search terms for finding sections across awesome lists"
    },
    "confidence": {
      "type": "number",
      "minimum": 0,
      "maximum": 1,
      "default": 0.3,
      "description": "Minimum confidence score (0-1)"
    },
    "limit": {
      "type": "number",
      "minimum": 1,
      "maximum": 50,
      "default": 10,
      "description": "Maximum sections to return"
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_awesome_items(listId, githubRepo, section, subcategory, tokens, ...)

Retrieves items from a specific awesome list or section with token limiting. You must call 'find_awesome_section' first to discover available sections, UNLESS the user explicitly provides a githubRepo or listId.

Input Schema

{
  "type": "object",
  "properties": {
    "listId": {
      "type": "string",
      "description": "UUID of the list (from find_awesome_section results)"
    },
    "githubRepo": {
      "type": "string",
      "description": "GitHub repo path (e.g., 'sindresorhus/awesome') from find_awesome_section results"
    },
    "section": {
      "type": "string",
      "description": "Category/section name to filter"
    },
    "subcategory": {
      "type": "string",
      "description": "Subcategory to filter"
    },
    "tokens": {
      "type": "number",
      "description": "Maximum number of tokens to return (default: 10000). Higher values provide more items but consume more tokens."
    },
    "offset": {
      "type": "number",
      "minimum": 0,
      "default": 0,
      "description": "Pagination offset for retrieving more items"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools