MCP server for accessing curated awesome list documentation
MCP server for accessing curated awesome list documentation. The context awesome mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
A Model Context Protocol (MCP) server that provides access to all the curated awesome lists and their items. It can provide the best resources for your agent from sections of the 8500+ awesome lists on github and more then 1mn+ (growing) awesome row items.
Everything the assistant can do here goes through one of these:
find_awesome_section — context-awesome sections <query...>search_awesome_items — context-awesome search <query...>get_awesome_items — context-awesome items Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 2 environment variables: CONTEXT_AWESOME_API_HOST, CONTEXT_AWESOME_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Context Awesome's toolset — find_awesome_section, search_awesome_items, get_awesome_items — is a fair guide to whether it matches your workflow. It is maintained by bh-rat; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| find_awesome_section | context-awesome sections <query...> |
| search_awesome_items | context-awesome search <query...> |
| get_awesome_items | context-awesome items <target> |
{
"mcpServers": {
"context-awesome": {
"url": "https://www.context-awesome.com/api/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CONTEXT_AWESOME_API_HOST | Endpoint or connection string the server talks to. | Optional |
| CONTEXT_AWESOME_API_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.