Claude integration?

[kristhayer11]

Before proceeding, check to make sure there isn’t an existing issue for this idea or a similar one.

• I have searched the existing issues and determined this is a new proposal.

Proposed change

I've been using the desktop version of Claude for all kinds of things in my daily work. I noticed that it has a plug-in called "desktop commander."​ This allows the user to access terminal using conversational prompts. I know that the use of terminal and the preview browser for quire is intimidating for some people. It certainly was for me!

Claude is also a terrific bridge for GitHub, which also is confusing for some new users. I personally enjoyed learning about GitHub, CSS, and some HTML. But, it took me quite a while, and I'm still not as comfortable as I would like to be.

I wonder if there are any developers interested in building​ an MCP (Model Context Protocol)​ for Quire+Claude...

Even if not, a quick Google search comes up with many possibilities for Claude assistance. An official integration would, of course be easier and more powerful, but even a manual integration would be helpful.

Potential Impact

I think users without prior experience with using terminal, CSS, HTML, and GitHub would find the conversational interface of Claude simple and efficient, with a quicker learning curve.

Supporting Information

No response

[andy-jdl]

Hey @kristhayer11, I think the impact is real and a prompt like Create a new Quire project called my-catalogue in my Documents folder would help with initial learning curves.

Effort for wrapping cli commands in an mcp server is well documented and achievable. In fact something similar to this article can be spun up in a couple to a few days.

Rather than trying to deliver everything at once I'm thinking a Phase 1 approach on CLI tooling is the place to start. If we open a Discussions thread and see if there's community interest or, I'm happy to put a server together and get the ball rolling.

cc: @Erin-Cecele

[kristhayer11]

@andy-jdl Thanks for your reply—I was hoping this would be the response from someone. I built 4 pubs in older versions of Quire, but since it's been a few years, I'm having a bit of anxiety about remembering/relearning everything for my next project. I think your proposed phased approach makes sense—it would get users over an initial hump.

I wonder if @Erin-Cecele and @geealbers have any info about a wider interest for this integration. If you're up for it, I would say to go ahead and open up a discussion thread and see where it leads.

[Erin-Cecele]

Hi @kristhayer11 and @andy-jdl, what a fantastic thread! We encourage you to open this topic for broader discussion within the Quire community. I will do my best to draw people's attention to it to maximize feedback. One thing to keep in mind: this is unlikely to be something the Getty would implement in core Quire, but should there be enough enthusiasm from other users (and no obvious code incompatibilities), we would welcome a community-driven, externally developed solution. Thank you both for your interest in exploring this!

[andy-jdl]

Thank you @Erin-Cecele, since this would be a separate system and outside of core quire, I went ahead and created a dedicated repository for this project (link). @kristhayer11 I would like to stay in touch to gather feedback once Phase 1 is complete. Phase 1 will focus on creating Claude tools from Quire commands.

[kristhayer11]

@andy-jdl Great news, thank you! In full disclosure, I do not have a development background and have only dabbled in customizing my Quire-created publications. I'm using Claude in my regular workflow, integrating asana, the Google suite, and other tools via connectors. I could see right away the potential of a Claude and Quire integration, but I will likely not be a very helpful contributor to the process.

[Erin-Cecele]

@andy-jdl Are you opening a discussion thread for this? Or would you like me to convert this issue into a discussion to capture the back-and-forth that has taken place here?

[andy-jdl]

@Erin-Cecele, I'll go ahead an open a discussion thread, apologize for jumping the gun. I'll keep it brief with an explanation of what an integration would accomplish.

@kristhayer11 No worries at all. What I'm mostly looking for is your feedback and experience with using the tool. Every bit of feedback is helpful.

[Erin-Cecele]

See Discussion #1209 for more information and to join the conversation.