Feature request: native MCP (Model Context Protocol) support in GoCD

Summary

Please consider adding native MCP (Model Context Protocol) support to GoCD itself.

There is already a community MCP server at https://github.com/rushi/gocd-mcp, which is useful as a proof of concept, but running a separate server is operationally inconvenient.

Problem

Today, using GoCD from MCP-compatible AI clients requires an extra sidecar service:

• additional deployment + lifecycle management
• duplicated auth/session handling
• separate compatibility/versioning concerns
• fragmented user experience vs core GoCD APIs

For teams already running GoCD, this extra moving part creates friction and reduces adoption.

Proposal

Add MCP capability directly in GoCD (or as an officially maintained first-party module/plugin distributed with GoCD), so users can connect MCP clients without a separate community server.

Potential scope:

• expose selected pipeline/build/environment operations as MCP tools
• map tool permissions to existing GoCD auth/RBAC
• provide configuration in GoCD admin settings
• document a stable MCP surface + versioning policy

Why this matters

• lower operational overhead for users
• better security posture through native auth integration
• clearer support story and long-term compatibility
• easier discovery/adoption of GoCD in AI-assisted workflows

Prior art

• Community server: https://github.com/rushi/gocd-mcp

Ask

Would the GoCD maintainers be open to native MCP support in core/official distribution?

If there is interest, I’m willing to help with implementation and/or an RFC/technical design proposal.