MCP Server Development Services

Description

We want our internal tools reachable from the AI assistants our engineers already use, through the Model Context Protocol, instead of each team wiring up its own bespoke integration. Scope is an MCP server exposing four internal systems: our deployment tool, our incident tracker, our metrics API and a read-only slice of our customer database. The read-only part is deliberate and not negotiable for this phase. Authorisation is the substance of this job. Each tool call must run as the requesting engineer with their own permissions, not as a shared service account, and every call must be logged with who asked and what came back. Assume this will be reviewed by our security team before it is enabled.

• Build an MCP server exposing the four agreed internal systems
• Implement per-user authorisation so a tool call carries the requesting engineer's own permissions
• Log every tool call with the caller, arguments and result summary, in a form our security team can audit
• Keep the customer database slice strictly read-only, enforced server-side rather than by convention
• Write tool descriptions clear enough that an assistant picks the right one without trial and error

• MCP server deployed in our environment, with the four integrations
• Authorisation design note for security review
• Audit log with retention and export
• Tool reference documentation for our engineers