What your agent can do
Once connected, your assistant has three tools:
- list_palettes — browse Fove's built-in palettes and every palette you've saved to your account.
- list_gradient_styles — get the available style ids (Nebula, Aurora, Velvet, Mesh Atlas, and so on) so the assistant picks a valid one.
- build_gradient — compose a gradient from a palette (or a set of custom hex colors) and get back the CSS, an editor link, a share link, an iframe embed URL, and a direct PNG URL — all in one response.
Example prompts
- "Build a calm teal mesh gradient for a slide deck cover."
- "Give me three warm, sunset-y two-color gradients I can use as hero backgrounds."
- "Turn my 'Client — Aurora' palette into a mesh gradient and paste the CSS."
Connect the tools
The endpoint is a Model Context Protocol server that any MCP-aware assistant can connect to. Sign-in uses your existing Fove account over OAuth — tools always run as you, so an agent only sees the palettes and collections you've saved.
Endpoint
https://fove.design/mcpClaude Desktop / Claude Code
Add Fove to your Claude MCP config (usually ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"fove": {
"url": "https://fove.design/mcp"
}
}
}Restart Claude and pick Fove from the tools menu. Claude will open a browser tab for you to sign in the first time.
Cursor
In Cursor, open Settings → MCP and add a new server:
{
"fove": {
"url": "https://fove.design/mcp"
}
}ChatGPT and other MCP clients
Any MCP-aware client accepts the same endpoint URL. When adding the server, point it at https://fove.design/mcp and complete the OAuth sign-in in the popup.
Auth and scope
Tools always execute as the signed-in user. That means:
- Your agent can see built-in palettes and your saved palettes — never someone else's.
- Nothing is written to your account by these tools; they compose and read only.
- Revoke access at any time by signing out of Fove.
Where to go next
Ready to make prettier gradients by hand? Read the design guide.