Use AnimatedWebs in Copilot cloud agent

GitHub's Copilot cloud agent can use the AnimatedWebs MCP server through the repository's MCP configuration, authenticated with an API key stored as an Agents secret. It does not support OAuth servers, so this is the header route, and it only uses the tools you allow.

Connects with: type http, url, tools allowlist
Sign-in: API key header only (no OAuth)
Where: Repository Settings, Copilot, MCP servers

Browse templates See pricing All setup options

Set up AnimatedWebs in Copilot cloud agent

Server address: https://mcp.animatedwebs.com

1
Copy your API key
Open the developer page in your AnimatedWebs dashboard and copy the aw_ key. Free accounts have one.
2
Store it as a secret
In the repository or organization settings, add an Agents secret whose name starts with COPILOT_MCP_. Only names with that prefix reach the MCP configuration.

Paste the MCP configuration

In the repository settings, under Copilot, open MCP servers and paste this JSON into MCP configuration, then save. GitHub checks the syntax when you save.

Agents secret (name and value)

COPILOT_MCP_ANIMATEDWEBS_KEY = aw_your_key

Repository settings, Copilot, MCP servers, MCP configuration

{
  "mcpServers": {
    "animatedwebs": {
      "type": "http",
      "url": "https://mcp.animatedwebs.com",
      "tools": [
        "search_templates",
        "get_template",
        "get_template_prompt",
        "search_styles",
        "get_style_reference",
        "search_components",
        "get_component",
        "search_backgrounds"
      ],
      "headers": {
        "Authorization": "Bearer $COPILOT_MCP_ANIMATEDWEBS_KEY"
      }
    }
  }
}

4
Assign an issue to Copilot
Create an issue, assign it to Copilot, and say which AnimatedWebs template or component to use. Copilot opens a pull request when it is done.

Your API key is on the developer page of your dashboard. Every account has one, free accounts included.

Check that it works

When the pull request appears, open the Copilot started work event, click View session, open the ... menu and choose Copilot, then expand the Start MCP Servers step. The started servers and their tools are listed at the bottom.
In the issue, ask Copilot to confirm that it called search_templates from animatedwebs before it wrote any code.

Three requests to try

Paste one into Copilot cloud agent. Each one makes it call real AnimatedWebs tools.

example prompt 1

Add a hero section to the landing page. Use the animatedwebs server to find a template for a landscaping company and follow its prompt.

example prompt 2

Replace the plain footer with a component from animatedwebs, search_components first, and keep our color tokens.

example prompt 3

Pick a cinematic background from animatedwebs for the home hero and wire it in with a poster image fallback.

If something goes wrong in Copilot cloud agent

The config is rejected on save: GitHub validates the JSON syntax when you save. Check for trailing commas and that tools is present; it is required.
The tools are not listed in the session: Open the Start MCP Servers step in the session log and read the error there. A missing or misspelled COPILOT_MCP_ secret is a common cause.
The server asks for OAuth: Copilot cloud agent does not support remote servers that use OAuth. Keep the Authorization header with the API key as shown.
Copilot calls tools you did not expect: Once configured, the agent uses allowed tools without asking. Trim the tools list. Remove get_template_prompt if you do not want Pro prompts to use a Prompt Pack credit.

Questions about Copilot cloud agent and AnimatedWebs

Why is there a tools list?+

GitHub requires tools in the configuration, and recommends allowlisting specific read-only tools instead of *. The list here is the search and fetch tools that matter for building a site.

Does it work for prompts and resources?+

No. GitHub's docs say Copilot cloud agent and code review support only MCP tools, not resources or prompts.

Is the key exposed in the repository?+

No. The JSON holds only a reference to the secret, written as $COPILOT_MCP_ANIMATEDWEBS_KEY. The key itself lives in the Agents secret.

Does this also affect Copilot code review?+

GitHub says the same repository configuration is used by code review, which only keeps tools that declare themselves read-only. There is a toggle under Copilot, Code review to turn MCP tools off for reviews.

Facts checked on October 28, 2026

What this page says about Copilot cloud agent comes from its official documentation, linked below, and Copilot cloud agent can change, so check its docs for the latest. What it says about AnimatedWebs comes from how our own MCP server works.

Copilot cloud agent accepts local, stdio, http and sse servers; remote ones use url and optional headers. GitHub Docs: extend Copilot cloud agent with MCP ↗
Remote MCP servers that use OAuth are not supported; the tools key is required and GitHub recommends allowlisting read-only tools. GitHub Docs: extend Copilot cloud agent with MCP ↗
Secrets and variables must start with COPILOT_MCP_ and can be referenced as $VAR, ${VAR} or ${VAR:-default} in string fields. GitHub Docs: extend Copilot cloud agent with MCP ↗
The Start MCP Servers step of the session log lists started servers and tools; only MCP tools are supported, not resources or prompts. GitHub Docs: extend Copilot cloud agent with MCP ↗

Copilot cloud agent and the other tool names on this page are trademarks of their owners. AnimatedWebs is independent and not affiliated with them.

Pick a look, then let Copilot cloud agent build it

Free accounts open every free prompt, and Pro unlocks the whole vault. Building an agent of your own? Read the agent guide.

Browse templates See pricing MCP overview