MCP & Distribution

The MCP server

It Just Vibes exposes a remote Model Context Protocol (MCP) server with a deposit_widget tool. Once it's connected, you can be in a fresh AI chat, build a widget, and simply say “save this to itjustvibes.com” — your AI tool deposits it for you and hands back the permanent link.

Connecting your AI tool

Generate an API key from your account settings, then add the server to your tool. Claude web custom integrations and Claude Desktop use the remote MCP URL https://itjustvibes.com/api/mcp with your key; Cursor uses an equivalent JSON config. The one-click “Copy for Claude” setup surface gives you a ready-to-paste config for each target, populated with your real key.

Treat your API key like a password — it authorizes deposits on your behalf. You can revoke and regenerate it anytime from settings.

Controlling each deposit

deposit_widget accepts optional parameters so an MCP deposit lands exactly where you want: visibility (public, private to you, or private to a group), the three SDK capability toggles, an optional group_id for group-scoped widgets, and source_url for attribution. When you omit them, deposits default to public and immediately discoverable.

Source tracking

When a widget is imported from a live source — a Claude artifact, a CodePen pen, a GitHub gist — we remember the original URL and show a source-aware link (“View on Claude”, “View source”) on the widget's detail page alongside its attribution.

A daily background poller re-fetches tracked sources through a dedicated allowlisted fetcher and hashes the extracted widget code. If the original source changes, the author gets a notification and a dismissible “the original source changed — regenerate?” banner. Re-importing updates the stored hash and clears the flag.