Use AnimatedWebs in Continue
Continue connects to the AnimatedWebs MCP server through a streamable-http entry in config.yaml, with your API key sent in requestOptions headers. MCP tools run only in Continue's agent mode.
- Connects with
- type streamable-http
- Sign-in
- Authorization header in requestOptions
- Config file
- config.yaml, mcpServers block
Set up AnimatedWebs in Continue
Server address: https://mcp.animatedwebs.com
- 1
Copy your API key
Open the developer page of your AnimatedWebs dashboard and copy the aw_ key. Free accounts have one.
- 2
Edit config.yaml
Add the entry to the mcpServers list of your Continue config. Keep the two-space indentation, because YAML is strict about it.
config.yamlmcpServers: - name: AnimatedWebs type: streamable-http url: https://mcp.animatedwebs.com requestOptions: headers: Authorization: Bearer aw_your_key - 3
Switch to agent mode
Continue's docs say MCP can only be used in agent mode, so pick agent in the chat mode selector.
- 4
Ask for a template
Describe the site you want. Continue calls the AnimatedWebs tools and shows each call.
Your API key is on the developer page of your dashboard. Every account has one, free accounts included.
Check that it works
- Check with a prompt. Ask it to run the get_account tool from the animatedwebs server. A reply with your plan and today's usage means the connection and your sign-in both work.
- If the tool call never happens, confirm you are in agent mode and that the YAML parses.
Three requests to try
Paste one into Continue. Each one makes it call real AnimatedWebs tools.
Use the AnimatedWebs MCP server to find a template for a community food bank and outline the page sections.Search AnimatedWebs backgrounds for a hero loop for a mountain lodge and give me the link and a video tag.Get the AnimatedWebs style reference for a Vercel-like site and write a tailwind.config theme from it.If something goes wrong in Continue
- Nothing happens when you ask for a template
- MCP works only in agent mode. Switch the mode selector from chat to agent.
- The server entry is ignored
- Check the YAML indentation and that type is streamable-http. Continue accepts sse, stdio and streamable-http.
- You get a 401
- Check the Authorization line under requestOptions, headers: it must read Bearer, a space, then the aw_ key.
- You prefer a separate file
- Continue also reads files in .continue/mcpServers/ that start with name, version and schema fields. Its docs show that layout for a local server; the mcpServers entry itself is the same shape.
Questions about Continue and AnimatedWebs
Does Continue support OAuth for MCP servers?+
Its MCP page does not mention OAuth, so this guide uses the API key header.
Is the headers option documented?+
Yes. The config reference says requestOptions on an MCP server uses the same format as model requestOptions, and that format includes headers as name and value pairs.
Can I use chat mode?+
No. Continue's docs say MCP is only available in agent mode.
Which transport should I pick?+
streamable-http. AnimatedWebs serves Streamable HTTP, and Continue also supports sse for older servers.
Facts checked on
What this page says about Continue comes from its official documentation, linked below, and Continue can change, so check its docs for the latest. What it says about AnimatedWebs comes from how our own MCP server works.
- Continue supports sse, stdio and streamable-http MCP servers, listed under mcpServers in config.yaml with name, type and url. Continue MCP docs ↗
- MCP can only be used in agent mode. Continue MCP docs ↗
- requestOptions on an MCP server applies to sse and streamable-http servers and follows the model requestOptions format, which includes headers. Continue config reference ↗
Continue 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 Continue build it
Free accounts open every free prompt, and Pro unlocks the whole vault. Building an agent of your own? Read the agent guide.