MCP Server Development for Business Tools | SJ Innovation

MCP server development for business tools in practice: how our HR team shipped about 100 pull requests with Cursor and handles feedback from the editor.

MCP Server Development for Business Tools | SJ Innovation

A leave policy change sounds like one task. In practice it is a screen, a permission rule, a database migration and a release note, all waiting on each other. Multiply that by attendance, hiring and feedback requests, and a small HR team can spend weeks on changes that each look simple on a ticket.

That is the daily reality behind the SJ HR portal. Mushfiqur Rahman, a developer on the Avengers team at SJ Innovation, ran into it constantly. Tickets rarely stayed on one screen, and feedback made things worse because people had to leave their editor, open the portal and work through the hub by hand.

Why One HR Change Touches So Many Layers

HR software carries rules that other products can skip. Who approves leave, who sees attendance and who reads a hiring note are business decisions, not styling choices. Each rule shows up in the interface, the data layer and the documentation, and missing one leaves the feature half finished.

Before AI entered the workflow, Mushfiqur wrote the Frontend and Backend codes, hooks, SQL and edge functions himself, then tested and opened the pull request. A change that touched the UI, the database and the docs usually took a full day. The process was not broken. It was simply built to handle one layer at a time.

Letting Cursor Draft While a Human Decides

Mushfiqur now describes the problem in Cursor and points it at the existing code. Cursor drafts the screens, the data layer, the migrations and the release notes. He then corrects the business rule, reviews the diff, runs the flow and merges. The AI writes the first pass, and the judgment stays with him.

That split matters more than the speed. A fast draft that nobody checks just moves bugs into production sooner. Reviewing every diff and testing every flow before merge is what lets the team trust the pace. Between 1 August and 7 October 2026, the results looked like this:

Bringing the Feedback Hub Into the Chat

The bigger shift came from the Feedback Hub. The team built the SJ HR Feedback MCP, a connector that lets Cursor work with the hub directly. MCP, short for Model Context Protocol, is an open standard that lets AI tools use outside systems through a defined set of actions.

This is where MCP server development for business tools gets practical. The Feedback MCP exposes eight tools covering lists, ticket details, stats, comments and status updates. HR, managers and engineers can pull up open bugs, read a ticket with its comments, reply and change its status without opening the portal.

It also runs on the same permissions as the portal, which is the part most teams skip past. MCP server development for business tools only works if the AI connection respects your existing access rules. A shortcut that bypasses permissions is a risk, and reusing the portal’s own rules meant nobody gained access they did not already have.

What Other Teams Can Take From This

You do not need an HR portal to use the pattern. Any team with a ticket queue, an internal dashboard or a feedback inbox can ask the same question: which tasks force people to leave the tool where they already work? Start with those, and connect only what people touch every day.

Internal systems also hold teams back more often than they admit. Custom HR portal development pays off when the rules are written down and the people using the system can report problems quickly. Mushfiqur’s team had both, and the pace showed it.

Where This Leaves the Team

Feedback triage no longer means switching into the portal for every ticket. More HR requests ship in the same week, and each one carries its permissions and release notes. The gain is not one headline number. It has fewer context switches, fewer hand-offs and a team that spends its time on decisions instead of busywork.

If your team is buried in tickets that touch five layers each, or your feedback process lives in a tool nobody wants to open, SJ Innovation can help. Our engineers build AI assisted workflows and connect them safely to the systems you already use. Share what slows your team down, and we will suggest a first step in plain English.