Use AnimatedWebs in goose

goose adds the AnimatedWebs MCP server as a Remote Extension (Streamable HTTP), either through goose configure or a config.yaml entry. goose obtains OAuth credentials on its own for servers that support dynamic client registration.

Connects with: type streamable_http
Sign-in: OAuth handled by goose, or a headers entry
Config file: ~/.config/goose/config.yaml

Browse templates See pricing All setup options

Set up AnimatedWebs in goose

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

1
Try it for one session
The --with-streamable-http-extension flag loads the server for a single session without saving anything, which is a quick way to test the URL.

Save it

Run goose configure, choose Add Extension and then Remote Extension (Streamable HTTP), and follow the prompts. Or add the same extension to config.yaml.

terminal

goose configure
# Add Extension > Remote Extension (Streamable HTTP)
# name it animatedwebs and enter the URL below

goose session --with-streamable-http-extension "https://mcp.animatedwebs.com"

or config.yaml

extensions:
  animatedwebs:
    name: AnimatedWebs
    type: streamable_http
    uri: https://mcp.animatedwebs.com
    enabled: true
    timeout: 300

3
Sign in
goose says remote extensions that need OAuth normally get a client ID automatically, through Client ID Metadata Documents or Dynamic Client Registration. Approve access in the browser window that opens.
4
Make sure it is on
In goose Desktop open Extensions in the sidebar and check the toggle, or confirm enabled: true in config.yaml. Then ask for a design.

Headless or CI? Use an API key from your dashboard instead of the browser sign-in.

Check that it works

In goose Desktop, Extensions in the sidebar lists the extension with its toggle. In config.yaml, check for enabled: true.
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.

Three requests to try

Paste one into goose. Each one makes it call real AnimatedWebs tools.

example prompt 1

Use the animatedwebs extension to find a template for a wine bar in Napa and write the page in this directory.

example prompt 2

Search animatedwebs for a cinematic background for a hero and summarize the three best options.

example prompt 3

List the animatedwebs template categories and tell me which fits a mobile detailing business.

If something goes wrong in goose

The OAuth callback is blocked: The callback runs on 127.0.0.1. If something needs a fixed port, set GOOSE_OAUTH_CALLBACK_PORT before starting goose.
The extension is blocked before it starts: goose checks external extensions for known malware before activation and shows an error if one is flagged. The goose known-issues page covers blocked extensions and offline setups.
The tools are missing: Confirm enabled: true and give the extension a longer timeout than the 300 seconds in the example if your tool calls run long.
Windows cannot find config.yaml: On Windows it is at %APPDATA%\Block\goose\config\config.yaml. On macOS and Linux it is ~/.config/goose/config.yaml.

Questions about goose and AnimatedWebs

Can I use an API key header in goose?+

Yes, in config.yaml. goose's config reference shows a headers map on a streamable_http extension, so add Authorization: Bearer with your aw_ key under it. The extensions guide describes the OAuth route, which is what the commands above use.

Is it Streamable HTTP or streaming HTTP?+

The goose docs label the type Remote Extension (Streamable HTTP), and config.yaml uses type: streamable_http.

Do I have to register an OAuth client?+

No. AnimatedWebs supports Dynamic Client Registration and Client ID Metadata Documents, the two methods goose uses to get a client ID by itself.

What timeout does the example use?+

300 seconds, copied from the goose docs' remote extension example. Lower it if you want failed calls to give up sooner.

Facts checked on October 28, 2026

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

goose supports Remote Extension (Streamable HTTP) in goose configure and --with-streamable-http-extension for one session. goose extensions guide ↗
A streamable_http extension in config.yaml uses name, type, uri, enabled and timeout. goose extensions guide ↗
Remote extensions that need OAuth normally get a client ID automatically via Client ID Metadata Documents or Dynamic Client Registration; the callback runs on 127.0.0.1. goose extensions guide ↗
config.yaml lives at ~/.config/goose/config.yaml on macOS and Linux and %APPDATA%\Block\goose\config\config.yaml on Windows, with extensions under the extensions key. goose config files ↗
The config reference shows a streamable_http extension with uri, headers, envs and timeout fields, and says SSE is not supported. goose config files ↗

goose 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 goose 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