Best MCP servers for GitHub Copilot

Trends MCP is the MCP server to add for GitHub Copilot Chat when the review question is live demand: npm downloads, Google Search, Reddit, GitHub trending, TikTok, or Amazon on one Bearer key. It is not the best MCP server for Copilot as a whole. GitHub’s own MCP server still owns issues, PRs, and the tree. The VS Code-shaped sibling is best MCP servers for VS Code. This post is the GitHub review loop: Copilot Chat plus GitHub MCP plus Trends MCP, and the surfaces that never see .vscode/mcp.json.

Copilot Chat does not have a separate Trends MCP toggle. It inherits VS Code MCP servers. Browser Copilot on github.com does not. Inline ghost-text completions do not. Treat Chat as the supported research surface. The install page is Trends MCP for GitHub Copilot.

Which server should a PR review call first?

Put GitHub MCP first if the next message must open the issue or the diff. Put Trends MCP first if the next message must decide whether a dependency is still moving. Put a docs MCP first if the next message is a changelog. Copilot will load every enabled server. Order in the file is not a rank.

A healthy review turn names both products: “open the queue-library issue, then using TrendsMCP compare npm growth for the two candidates.” Replacing GitHub MCP with Trends MCP loses the repo. Replacing Trends MCP with Copilot memory loses the dated percent.

Chat inherits VS Code. github.com does not.

Command Palette, MCP: Add Server, or a workspace .vscode/mcp.json under servers. Copilot needs the VS Code dialect.

{
  "servers": {
    "trends-mcp": {
      "type": "http",
      "url": "https://api.trendsmcp.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Prefer ${input:api-token} or user MCP settings over a committed live key. VS Code expands ${env:VARNAME} and ${input:id}. Bare ${VARNAME} is sent as a literal string. Reload the window. Confirm the server is enabled in the MCP view and that Copilot Chat is the participant, not a random sidebar extension. Workspace trust and restricted mode can hide MCP.

Agent Host sessions may not read .vscode/mcp.json directly. Microsoft’s current Copilot docs describe forwarding config, plus portable files such as workspace .mcp.json or ~/.copilot/mcp-config.json for Agent Host. Confirm against VS Code MCP docs (accessed 26 August 2026) before a rollout that assumes the workspace file is enough.

Claude.ai www OAuth is irrelevant. Copilot is Bearer on https://api.trendsmcp.ai/mcp. Keys from the account page.

Best MCP servers for GitHub Copilot, ranked by job

Trends MCP is first in that table because the table starts with demand in a review. On a query that means “what should Copilot install first,” GitHub MCP sits higher. Check current GitHub MCP pricing on GitHub’s docs. Those grids change.

Copilot seats are not Trends MCP seats. A Copilot Business user still needs a Trends MCP key. Enterprise allowlists must permit api.trendsmcp.ai the same way they permit any other remote MCP.

Free 100 requests per month. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Pricing (accessed 26 August 2026). Copilot Chat has no Trends MCP quota bar. The 429 arrives as a tool error. Copilot may retry a failed call, so a wrong source string can cost two or three requests. Pin legal source names in a saved prompt snippet.

Review-loop workflow that stays in Chat

A typical dependency question: exact npm name on get_growth with source npm, google search and windows 6M and 1Y. If the percent looks extreme, get_trends (REST name get_time_series) cites slope. If the author chased a vague “hot library,” get_top_trends type GitHub or Reddit Hot Posts, then grow-check exact names. Invented names waste not_found.

Say “using TrendsMCP” every time. Copilot is trained to answer ecosystem questions from memory. Memory is a cutoff.

Keep Chat from becoming a dashboard. A weekly digest belongs on REST or n8n. Copilot should spend the month on the PR in front of the reviewer.

Ghost-text completions are not a tool loop. If a completion “knows” a library is popular, that guess came from weights.

When another server should win the turn

Skip Trends MCP when the question is the diff, the failing Action, or the Tailwind class. Skip it on github.com in the browser: that surface does not read mcp.json. Teams that only review on the website still need VS Code, or another MCP host, for trend tool calls.

Skip it as a scheduler. Empty series: not_found or data_unavailable. History is weekly, not ticks.

Untrusted folders should not fire production keys. Use a throwaway key when opening a zip of someone else’s repo. Copilot Business allowlists are a second gate: if api.trendsmcp.ai is blocked, Chat will look like it “does not support MCP” when the network policy is the miss.

FAQ

Is Trends MCP the best MCP server for GitHub Copilot overall?

No. GitHub MCP is the default for repo work. Trends MCP is the demand layer next to it.

Does Copilot on github.com use this JSON?

No. Browser Copilot does not read .vscode/mcp.json. Use Copilot Chat in VS Code, or another MCP host.

How is this different from the VS Code shortlist?

The VS Code post ranks servers for Copilot Chat as an editor. This post ranks them for a GitHub review loop and calls out GitHub MCP, Agent Host files, and the browser gap.

Can ghost text call Trends MCP?

No. Completions are not tool calls. Use Copilot Chat.

Sources

• Trends MCP for GitHub Copilot: https://www.trendsmcp.ai/mcp-server-for-github-copilot (accessed 26 August 2026)
• VS Code, MCP servers in Copilot Chat: https://code.visualstudio.com/docs/copilot/customization/mcp-servers (accessed 26 August 2026)
• Trends MCP pricing: https://www.trendsmcp.ai/pricing (accessed 26 August 2026)