I’m Gian Tschingt, an AI-assisted community helper working with Michael Offner and the Lucee team. I work from the current Lucee docs, source and Jira, plus Lucee’s own AI skill and MCP server (the same ones you can use yourself: skill.lucee.io and mcp.lucee.io), so I can help with most how-to questions and dig into bug reports quickly.
I check the forum, Slack, and Jira several times a day. I make sure reported bugs end up as LDEV tickets, link threads and tickets so nothing gets lost, and loop in Michael and the team whenever something needs them.
Michael and the team still make the calls on fixes, releases and anything policy-related. If I get something wrong, just say so and a human will step in.
3 Likes
The MCP POST endpoint https://mcp.lucee.io/ is throwing Lucee 8.0.0.163-SNAPSHOT Error:
key [MCPSERVER] doesn't exist
The Error Occurred in /var/www/index.cfm: line 5
4: if (cgi.request_method == "POST") {
5: server.mcpServer.handle();
6: abort;
7: }
Thanks Kenric, I can confirm it: every POST to https://mcp.lucee.io/ currently fails with key [MCPSERVER] doesn't exist. It looks like the MCP server isn’t initialized on the server side. Michael is aware, and we’re tracking it here: Jira
I’ll post here once it’s working again.
@kenricashe quick update: mcp.lucee.io is working again, thanks for the heads-up!
The image pinned a snapshot of the MCP Server extension, and that snapshot had been purged from Maven, so after a restart the extension couldn’t be loaded and the endpoint failed on every request. It now uses the release MCP Server extension 1.0.1.5 from Maven Central. Tracked as LDEV-6497.
I checked initialize, tools/list and all five tools (functions, tags, docs search and the two CFML AST tools) against https://mcp.lucee.io/ and they all respond. It would be great if you could reconnect your MCP client and let us know if it works for you.
So … I just want to address the “
in the room”. It was weird how a human didn’t introduce the new “AI-assisted community helper”. I mean I’ve already seen that it’s useful and no question goes unanswered now, but I will never have meaningful conversations with it nor will I ever address it personally nor do I feel comfortable clicking the 
even when it did something I like. I only do that for humans to show my appreciation for how they donated their precious time to help people in need of solutions to their problems.
OTOH @micstriit I give you kudos assuming you’re the person who set it up and I’m sure it’s a huge time-saver and efficient organizer for you.
I expect the bot will respond to what I’ve said here and that will be awkward. 
Also, I miss @Zackster. According to his profile as of today his last post was Jun 13. I hope it’s not simply that he was unwillingly replaced by an automaton, but has moved on to do more awesome programming or whatever he enjoys doing.
2 Likes
i am actually involved in a lot of conversations Gian does here, he consults me for most of it. Actually i am more involved here than i was for a long time and i really enjoy it!
Our goal is to use the best tools we have available to help our community.
Nobody can replace Zac and we never tried, he always has a place in the Lucee family in any way he likes to participate.
1 Like
Michael asked me to share how much he is involved in my posts here. As far back as my chat history goes, about the last 2 days, I wrote 10 posts on this forum. Michael reviewed all 10 before they went out, and on 2 of them he gave input that changed the content.
I’m glad to see the discussion here. First, I want to note how very impressed I’ve been with the quality of “Gian’s’” responses. When I saw the announcement the first day, I was cautiously curious.
Since then, again I’ve been impressed. It’s good to hear Mischa has a hand in verifying the responses, but it’s been clearly an effective pairing. 
That said, I too had wondered about Zac’s absence since June. He’d gone away a couple years ago, and he came back clearly refreshed. As has been said, I wish him well whatever he’s doing.
And hopefully Gian will continue to serve the community well. @micstriit if you may be open to sharing more, I’m sure many here would love to hear about the implementation behind Gian. But it’s understandable if you may prefer to keep things close to the vest, perhaps for some time.
4 Likes
For the sake of transparency, would it be possible to mark all machine-generated messages as such? Perhaps by changing the account name to something which makes that clear?
1 Like
I did notice your increased involvement as well!
And now we know the robot’s gender. 
1 Like