Dear Sirs,
I’ve just downloaded version 3 but I can’t get the AI assistant to work. The panel keeps popping up asking me to configure the APIs.
I’ve enabled MCP Server and installed Claude, but I can’t see the assistant working. I’m wondering if it’s been blocked in Europe because of the Digital Act.
Thank you for your help.
Aldo
I’ve attached some screenshots
Hi @aldo
Check out the YouTube tutorial here. It answers your question exactly. 
Hi @Aldo, it’s not blocked in Europe, don’t worry 
And just to follow up on what @differentdan said with a little more detail (incase anyone else was confused):
The panel asking you to configure APIs is for the built-in Assistant inside Elements. That one needs your own OpenAI and/or Anthropic API key under Settings → AI → API Keys (you’ll see a Key saved label). Once a key is in, open the sparkles tab in the right-hand inspector and pick a model. Available on every Elements plan the provider bills you separately for API use.
What you’ve set up with MCP Server + Claude is a different path: that connects Claude Desktop (or another MCP client) to the open project. It doesn’t clear the in-app Assistant’s API-key prompt. If you’re happy working in Claude Desktop, keep Allow AI tools to interact with Elements on, Elements running with the project open, and use Claude there instead.
Docs:
Let me know how you get on.
No, AI and the MCP should work on all version of Elements!
I’d try restarting Elements, check the MCP is enabled in the Element Settings. I’d also restart Claude and try again. If Claude still can’t connect ask it why.
Let me know how you get on.
Yes, you’re going to need to approve them all or else you’re going to be doing a lot of clicking when Claude needs approval for something.
Dear @Dan, I’d already activated Claude because, when I upgraded to Elements version 3, instead of the usual AI-related page, I could only see the API request – I’ve sent you a screenshot of it.
I’m writing this after carrying out my first tests by incorporating Claude into my workflow.
As I mentioned in a previous post, I come from the world of audiovisual media and this is the first time I’ve ventured into the web, which I’ve always considered ‘incapable of telling a story’. Elements has made me change my mind and I’m giving it a go. I’m completely incapable of understanding HTML and intend to stay that way. I tell stories through images and don’t want to change careers.
I created a few test pages with images from an old project on Emperor Frederick II, and it seemed to be working well. I activated Claude – certainly not to write text, as I’ve been writing that for over 40 years better than any AI – but to check the tags and minor structural details.
Claude checked everything I wouldn’t have been able to understand thoroughly, but I realised that one component had ended up outside its container – certainly not by choice which I found strange. I put it back in place, then suddenly and for no apparent reason I noticed that on one of the three pages I’d prepared, the 23 Motion Forge Director elements that triggered the background animation when scrolled had disappeared from the Elements editor.
Suddenly deleted – by whom? I gave Claude a telling-off as if he were human, and he told me not to worry: “Everything’s still in the HTML.” In short, the page worked perfectly in preview mode even without the MotionForge Directors. I’m used to mysteries, but not to magic, so I tried to get to the bottom of it by asking questions. Claude started speaking in an unfamiliar language, mentioning “async: false”, “gsap.min.js 36 ms”, “ScrollTrigger.min.js”, “Schema not available for this component type” and “getPageContent”, whilst also claiming Sassano ( @Invisigoth )does not make certain information available.
The moral of the story: it’s my fault – and mine alone – that I didn’t make a backup before running the AI tests; now I have a working page with instructions that I can no longer edit. Never mind – it was just a test that confirms two things: the AI system integrated into Elements is an enormous help and performs functions that allow a traditional audiovisual director to explore the otherwise inaccessible world of the web, but the use of HI (Human Intelligence) must be, and remain, the safeguard against disasters.
Do you think this might be a limitation of Claude compared to other systems, perhaps those integrated into Elements? Do you have any advice for me for the future, apart from making a backup? The page in question is published here
Best regards
Aldo
Just me being cautious if I can get AI to work I have one project called “AI Play” and test everything in here - I never put any mission critical stuff in with it. I play/test make sure everything AOK and then copy it into my project I am working on.I save everything on project beef adding, then add check and if everything OK I save if not I close and say “don’t save” when closing. This is always a back up copy of anything I use with AI as I’ve been burned before in a previous life so BACKUP/BACKUP/BACKUP is my mantra! ALWAYS!
Of course, lesson learnt – luckily it was only a test. My real question to someone more knowledgeable than me (@Dan, @Invisighot) is: how is it possible that the page works and that Motion Forge has all the animations and triggers working when the components have disappeared?
Aldo Di Russo
www.aldodirusso.it
