AwesomeRepos
Sign in

AwesomeRepos MCP server

This page is about the AwesomeRepos MCP server. It tells you who can use the server, what an AI app can read through it, and how to connect an app.

What the MCP server is

MCP (the Model Context Protocol) is a protocol that lets an AI app get data from a different service.

The AwesomeRepos MCP server lets an AI app read the Repository Index for you. The Repository Index is the catalog of repositories and their facts on AwesomeRepos.

You can connect Claude, ChatGPT, Cursor, VS Code, and other apps that support MCP.

The server is read-only. An app cannot change data on AwesomeRepos.

The MCP server is a test. The test ends on 27 December 2026. When the test ends, AwesomeRepos decides if the server stays.

Who can use it

You need an AwesomeRepos account. The account is free.

Each account can use the MCP server. The only exception is an account that a person who runs AwesomeRepos paused or blocked.

If you do not have an account, sign up first. If you have an account, sign in.

What the app can read

The server has 7 tools. A tool is one type of request that the app can send to the server. The app can use these tools:

  • search: Find repositories by their name on GitHub (owner/name), and find Tags (the groups of repositories by what they are) by their name.
  • get_repository_facts: Get the facts of one repository. The facts from GitHub are its stars, forks, last push, license, and topics. The other facts are its Tags, its daily star changes, and how fast its stars grow. The answer also has its maintenance and release facts, its dependencies in the index, and its newest releases.
  • get_trending: Get the Trending list, the same list as the Trending page, with the filters that the app gives.
  • get_tag_changes: Get what changed for 1 to 5 Tags in the last 7, 30, or 90 days. The answer has the repositories that got the most stars. It also has the repositories that got stars faster than in the period before, and the new repositories. If the app gives no Tags, the server uses the Tags in your Saved Views.
  • list_saved_views: List your Saved Views (the sets of filters that you saved). This tool needs the permission account:read.
  • get_saved_view: Get the repositories of one of your Saved Views. This tool needs the permission account:read.
  • list_bookmarks: List your Bookmarks (the repositories that you bookmarked), with the stars that each repository got in the last 7 days. This tool needs the permission account:read.

The app reads only the visible repositories. These are the repositories that AwesomeRepos shows on its pages.

When you connect an app, AwesomeRepos shows a consent page. On this page, you allow or deny the app. The page shows the permissions that the app asks for.

The tools for your Bookmarks and your Saved Views need the permission account:read. The consent page shows this permission as "Read your Bookmarks and your Saved Views."

The app can use these tools only if it asks for this permission and you select Allow.

The tool get_tag_changes also needs this permission when the app gives no Tags.

Connect an app

Server address

https://awesomerepos.com/mcp

When you add the server, the app opens AwesomeRepos. Sign in and allow access. The apps can only read data. To stop an app, remove it on the page Connected apps.

Claude (claude.ai and Claude Desktop)
  1. In Claude, go to Customize > Connectors.
  2. Select "+ Add", then "Add custom connector".
  3. Type the name AwesomeRepos.
  4. Paste the server address.
  5. Select "Continue".
  6. Keep the sign-in settings that Claude finds. Then select "Continue".
  7. For the OAuth client, keep "Use Claude's published identity".
  8. Select "Add".
  9. When Claude opens AwesomeRepos, sign in and allow access.

On a Team or Enterprise plan, an administrator adds the connector:

  1. Go to Organization settings > Connectors.
  2. Select "Add", then "Custom", then "Web".
  3. Do steps 3 to 8 above.

On a Team plan, an Owner or a Primary Owner can do this. On an Enterprise plan, a custom role with "Manage access to Libraries" can also do this. Then each person selects "Connect" in Customize > Connectors. On the Free plan, you can add only one custom connector.

Claude Code
  1. In a terminal, run this command: 
    claude mcp add --transport http awesomerepos --scope user https://awesomerepos.com/mcp
  2. In Claude Code, type /mcp and select awesomerepos. You can also run claude mcp login awesomerepos in a terminal.
  3. When Claude Code opens AwesomeRepos in your browser, sign in and allow access.

--scope user adds the server to all your projects. A run with claude -p cannot sign in, so sign in one time with /mcp first.

ChatGPT
  1. In ChatGPT on the web, go to Plugins (chatgpt.com/plugins).
  2. Select the plus button, then "Add custom MCP server".
  3. Type the name AwesomeRepos. Under "Connection", paste the server address as the "Server URL".
  4. For the authentication, select OAuth.
  5. Read the risk warning and select "I understand and want to continue". Then select "Create as a plugin".
  6. Install the plugin. When ChatGPT opens AwesomeRepos, sign in and allow access.

You can add the server only in ChatGPT on the web. Your account or workspace must permit custom MCP servers. The OpenAI setup pages do not list the plans that permit them.

Cursor
  1. Open the file ~/.cursor/mcp.json (for all projects) or .cursor/mcp.json (for one project).
  2. Add this server: 
    {
  "mcpServers": {
    "awesomerepos": {
      "url": "https://awesomerepos.com/mcp"
    }
  }
}
  3. In Cursor, go to Customize and make sure that the server is on.
  4. When Cursor opens AwesomeRepos, sign in and allow access.

If the file already has servers, add only the "awesomerepos" entry inside "mcpServers".

VS Code (GitHub Copilot)
  1. Open the Command Palette and run "MCP: Add Server".
  2. Select "HTTP (HTTP or Server-Sent Events)".
  3. Paste the server address.
  4. Type the server ID awesomerepos.
  5. Select where VS Code keeps the server.
  6. When VS Code opens AwesomeRepos, sign in and allow access.

Your organization can use a policy to block MCP servers in VS Code.

Limits

Each account has limits. The limits stop an app that reads too much of the Repository Index.

Each repository in an answer counts. The limits for each account are:

  • 1,500 repositories in each day (UTC)
  • 5,000 repositories in each week (Monday to Sunday, UTC)
  • 500 requests to the tools in each day (UTC)
  • 30 requests to the tools in each minute

There are also limits for all accounts together.

When an account is at a limit, the server refuses the request and tells the app about the limit.

Privacy

AwesomeRepos counts the requests of each account. It uses the counts to apply the limits, and to learn if people use the MCP server in more than one week. It does not keep the text that you or the app send, or the answers.

For the full list of what AwesomeRepos keeps, see the privacy page, section Apps that you connect.