Skip to main content

​
The connector will not connect

“Missing connection token” or 401. The URL was pasted without its ?token=… part, or the connection was revoked. Create a new one; the URL is shown once. Local site. claude.ai, the Claude desktop connector and ChatGPT fetch from their cloud and cannot reach .local, localhost or a private IP. Use Claude Code or an IDE client, or put the site on a public https address. The screen says when it detects a local site. A caching plugin in front of the REST API. The endpoint is a POST; make sure your cache does not serve stale responses for wp-json/bevel-mcp/.

​
The header shows the wrong menu

Make sure Bevel Kit is up to date. The Kit registers the primary_menu location on every theme and the MCP assigns the header’s menu to it; an older Kit left the location unregistered on some themes and the widget fell back to the first menu it found. The connection that minted it was revoked, or the Media (or Design System, for fonts) capability was switched off. Ask the assistant for a new link from a live connection.

​
A page was saved as draft though I asked to publish

Some image slots still showed the grey placeholder, so the page was held back as a draft. The assistant lists which ones. Add real photos, or ask it to find some, and publish again.

​
Changes do not show on the site

Every content change purges the caches automatically. If a change still does not show, the Elementor CSS may be cached by a plugin the purge does not know; asking the assistant to clear the cache, or the Clear Cache button in the admin bar, clears everything.

​
A font family I named was ignored

The design system takes Google Fonts and the fonts installed under Bevel → Custom Fonts. Anything else is left out and the assistant says so, because the browser would silently fall back to another font. Drop the font files into Brand assets or Custom Fonts first.

​
Where to look

Bevel → MCP Connectors → Activity lists the last calls with their result, and the Session timeline shows where the minutes and bytes of a build went: the assistant’s thinking time, the server’s time, what it typed and what it read. Copy a session as JSON and paste it into a chat to analyse a slow build.