Custom Sitefinity MCP Integration for University Event Publishing

How We Built a Custom Sitefinity MCP to Streamline Event Publishing for a Leading University in Saudi Arabia

A leading science and technology university in Saudi Arabia needed a way to let dozens of staff stakeholders publish academic events - including thesis and dissertation defenses - without requiring Sitefinity training. Eveliko built a custom MCP integration that accepts Word and Excel documents, guides users through disambiguations, and publishes structured events directly into Sitefinity.

Sitefinity CMS MCP (Model Context Protocol) Claude Cursor AI Integrations GitHub Copilot

Occasional CMS Users Don't Need to Become CMS Experts

Training doesn't scale for occasional users.

A leading science and technology university in Saudi Arabia has dozens of internal stakeholders - faculty, department managers, and research staff - who each need to publish academic events. Some publish regularly; others delegate to someone in their department who may touch the CMS even less frequently. Getting every one of them through meaningful Sitefinity training makes no operational sense when they use the system once every few months. There is simply no reason they should have to.

The existing workflow was a document.

Staff filled in a Word file or Excel spreadsheet - and that worked fine for the humans involved. The bottleneck was the manual step of re-entering that data into Sitefinity, with all the inconsistencies and delays that introduces. One of the most frequent and time-sensitive event types is the thesis and dissertation defense: a milestone that must be published promptly with precise structured data - supervisor names, research topics, defense location, participant roles.

A generic connector would not be enough.

Even an out-of-the-box AI connector for Sitefinity would not know how this university's instance is structured - its custom content types, taxonomies, speaker records, and editorial rules. The problem was not just automation; it was automation that understood this specific system.

A Custom MCP That Meets Staff Where They Already Work

Eveliko built a custom MCP (Model Context Protocol) server tailored to this university's Sitefinity instance and editorial workflow. The solution lets staff submit a Word or Excel document containing event details. The AI agent reads the document, extracts structured data, and begins the publishing process - without the staff member needing to log into Sitefinity at all.

Where the document is incomplete or ambiguous, the agent asks targeted follow-up questions rather than failing silently or guessing. For example, if a speaker named in the document already exists in the system, the agent surfaces the match and asks: should a new record be created, or should the existing one be linked? These disambiguation steps replicate the judgment a trained CMS editor would apply - but in a guided, conversational interface that requires no Sitefinity knowledge.

The MCP is fully custom to this client's environment. It understands the university's specific content model, event categories, and how structured data like supervisor roles and research topics map to Sitefinity fields. This is precisely the gap a generic connector cannot fill: every large Sitefinity installation has years of customisation layered into it, and a useful AI integration must reflect that reality.

The integration is part of the Eveliko platform approach: Sitefinity custom development combined with TCVelik, Eveliko's operational control platform. TCVelik provides SOP-gated workflows, onboarding structure, and a full audit trail for organisations that require traceability and compliance at scale. For a university managing many websites and dozens of content contributors, this layer is what turns a pilot tool into a sustainable operational process.

The pilot completed internal testing with no functional issues. The path forward includes expanding to additional event types, broader department rollout, and using TCVelik SOPs to onboard new stakeholders consistently as the university's content team evolves.