Use AnimatedWebs in Cursor

Set up AnimatedWebs in Cursor

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

1. 1

   Use the install link or edit mcp.json

   The button opens Cursor and fills in the server. To do it by hand, put the entry in ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project.

   Add to Cursor →

   or ~/.cursor/mcp.jsonCopy

   {
     "mcpServers": {
       "animatedwebs": {
         "url": "https://mcp.animatedwebs.com"
       }
     }
   }

2. 2

   Approve the install

   Cursor shows the server name and URL before it saves anything. Confirm that the URL is the AnimatedWebs MCP address above.

3. 3

   Sign in

   Cursor starts the OAuth flow in your browser. Sign in with your AnimatedWebs account and approve access.

4. 4

   Ask the agent

   Open the agent chat and ask for a template. Cursor asks before it runs a tool unless you allowed it.

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

Check that it works

• Open Customize in the Cursor sidebar and look for animatedwebs in the list of servers. It can be switched on and off there without removing it.
• 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 Cursor. Each one makes it call real AnimatedWebs tools.

Use animatedwebs to find a dark, cinematic template for a boutique fitness studio, then rebuild its hero section in this project.

Search animatedwebs components for a magnetic button and add the source to src/components.

Pull the style reference for a Linear-like site from animatedwebs and generate a Tailwind theme from it.

If something goes wrong in Cursor

The tools never show up

Open the Output panel (Cmd+Shift+U on Mac), choose MCP Logs from the dropdown, and read the error. A JSON typo in mcp.json is the common cause.

You edited mcp.json by hand and nothing changed

Restart Cursor. Its docs tell you to update a custom server's local files and then restart Cursor.

The sign-in window does not appear

Toggle the server off and on in Customize to retry the OAuth flow, or use the headers form with your API key.

A tool call fails but other servers keep working

Cursor marks that call as failed and keeps going. Read the error in the chat; a 401 means the sign-in expired.

Questions about Cursor and AnimatedWebs