Be Token Efficient
Claude Desktop is a good example of a tool
But it is very token-hungry, in part because of the protocol traffic occurring
Know Your ID's
If you have a lot of sites in your workspace, MCP has to list them and locate the correct site in order to get the SiteID. If you are doing regular work with a specific site, you can short circuit this process by making these available.
An easy way to get your site ID is to go to your published site and view source, you will see wf-site-id in the attributes of the topmost <html> element.
Claude Desktop
Use Projects
Claude's Projects allows for instructions, where you can specify the Webflow site_id and collection_id's that you work with most commonly.
This can reduce calls to the List Sites and List Collections and API endpoints, which will both reduce token use and speed up basic tasks you want to perform in Claude.
Know Your Tools
The MCP defines "tools" that your LLM can use to achieve the tasks you set, like creating CMS items.
Revoke Webflow MCP Access
When needed, you may need to de-authorize the Webflow MCP token so that you can issue a new one.
To do this you can request your LLM to "revoke Webflow mcp access" which should run the revoke_webflow_mcp_access tool and deauthorize MCP access.
After that, refresh the tools in your IDE. If you're using Claude Desktop, restart the app.
Alternatively, you can run this command: rm -rf ~/.mcp-auth Once that’s done, it should trigger the auth window to open in your browser, and you can create a new auth token.
