Windows + Claude Desktop with MCP

  • Resolved one3rdnerd

    (@one3rdnerd)


    1 week ago

    Hello,

    Firstly, congratulations on creating an awesome tool and being the most well developed AI implementation for WP so far.

    Secondly, I have a use case question.

    I’m running an SEO Audit in Claude Cowork in the desktop app on Windows, and want to be able to tie in my existing work to connect to the website using MCP.

    Is this possible at the moment? If so, how? If not, when? (cheeky, I know).

    I see a lot of marketers preferring the Cowork experience over Code, especially if they have an existing project.

    I also read in one of your docs that you haven’t tested it on Windows and it was written on Mac, so none of this may work. Is there a plan to work on that?

    I was also curious as to whether you would make it easier for users by trying to provide a Claude MCP connector via a Claude Plugin that can be easily installed directly inside the desktop app.

    I use a terminal as well but since the latest couple of updates to the desktop app, there are times where I prefer to work in there.

    I appreciate you, thanks in advance.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Jordy Meow

    (@tigroumeow)

    1 day, 8 hours ago

    Hi @one3rdnerd,

    First, thanks for the kind words, really appreciate it! And sorry for the late reply, I would’ve liked to answer a bit faster but honestly… I was working on your issue! AI Engine 3.4.9 just went out, and one of the headline changes is exactly this: the MCP server now speaks OAuth 2.1 with Dynamic Client Registration, which is the piece that makes Claude Desktop and Cowork talk to your WordPress site without any local setup! 🎉

    So the good news: it already works on Windows, and out of the box with Claude Cowork. Since everything goes through OAuth, there’s nothing to install or configure locally. You paste your site URL into Claude Desktop’s Custom Connectors, sign in, approve, and you’re connected. No Node, no scripts, no config files, no platform-specific gotchas, and no shared bearer token to babysit.

    The “not tested on Windows” note in the docs is actually about the local Node test scripts in labs/tests/, not the MCP server itself. The server is just a remote HTTP endpoint, so it’s OS-agnostic.

    Full walkthrough here: How To: Connect Claude to WordPress with MCP. Same flow works in Cowork.

    About a dedicated Claude plugin/connector: now that Claude Desktop has native OAuth Custom Connectors and AI Engine speaks that protocol directly, building a separate plugin would add friction rather than remove it. The current setup is already the “paste a URL, sign in, done” experience you’d want from a plugin anyway.

    Update to 3.4.9, give it a spin, and let me know if you hit any snag with the OAuth approval flow. Happy to look into it.

    Cheers!

    Thread Starter one3rdnerd

    (@one3rdnerd)

    1 day, 8 hours ago

    Hey @tigroumeow

    Thank you for your update, and no worries on the delay. I appreciate you getting back to me when you were able to.

    Wow, that’s awesome, I guess you really are one step ahead! 🙂

    Okay, I’ll give this a try and see how I get on.

    I guess my only thought about the plugin is, what if I manage 10 websites and want to use AI Engine in Claude for all of them. The best approach is just to add each individually and name them appropriately so it’s easy to reference which site I want to use?

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.