context-awesome

Context Awesome is an MCP server that provides access to curated 'awesome' lists and their items. It offers two primary tools: find_awesome_section and get_awesome_items. Use find_awesome_section to locate relevant sections or categories across multiple awesome lists by supplying a search query; you can fine-tune results with confidence and limit settings. Use get_awesome_items to retrieve items from a specific list or section, with options to filter by section, subcategory, and to control the amount of text tokens returned. This enables agents to quickly discover high-quality resources and pull targeted resources for a given topic, topic-agnostic research, or learning path.

Prerequisites:

• Node.js (LTS) and npm installed
• Git installed
• Basic familiarity with running MCP servers

1. Clone the repository

git clone https://github.com/bh-rat/context-awesome.git
cd context-awesome

2. Install dependencies

npm install

3. Build the server for production

npm run build

4. Run the server (development or production)

# Development (from source)
npm run dev -- [options]

# Production (compiled)
npm run start -- [options]

Options (examples):

• --transport <stdio|http|sse>
• --port <number>
• --api-host <url>
• --debug

5. If you want to configure MCP clients to connect locally, use the Node command configuration below and point to the built entry file.

# Example run using the built index (adjust path as needed)
node /path/to/context-awesome/build/index.js --transport http --port 3001 --api-host https://api.context-awesome.com

Notes:

• The server exposes endpoints via MCP and is designed to fetch and organize resources from widely-curated 'awesome' lists.
• Typical MCP client configurations involve pointing to the server with the appropriate transport (http, sse, or stdio).
• If you host locally, set CONTEXT_AWESOME_API_HOST to your backend API host to route requests properly.
• Ensure the built artifacts are accessible at the path provided in the MCP config (build/index.js in this example).
• For debugging, enable --debug to get more verbose logs during development.
• If you change the API host, re-build or ensure the environment variable is picked up by your runtime.