Harness Hosted MCP (https://mcp.harness.io/mcp) currently requires interactive OAuth through Harness ID — a human completing a browser-based sign-in flow. This works well for IDE-based AI clients (Cursor, Claude Code, Windsurf, VS Code) where a person is present to authenticate.

However, it doesn't support backend or service integrations — automations, internal bots, or other non-interactive systems that need to call Harness MCP tools without a human in the loop to complete a browser redirect.

Request:

Add a non-interactive authentication method for Hosted MCP, such as:

• An OAuth 2.0 client-credentials grant (client ID + secret issued per service/integration), or

• A service-account-scoped token that can be exchanged for a Hosted MCP session without browser interaction, or

• Support for using an existing Harness Personal/Service Access Token (PAT/SAT) directly against the hosted endpoint, similar to how the self-hosted/open-source MCP server accepts API keys today

This would let backend services connect to the fully-managed Hosted MCP endpoint (with its associated RBAC and permission scoping) the same way interactive clients do, without needing to stand up and maintain a self-hosted MCP server just to get token-based auth.

Use case:

Monitoring/auditing recent feature flag (toggle) changes via Harness Feature Management & Experimentation (FME) through MCP — e.g., a backend service periodically checking what flags changed recently, on a scheduled or event-driven basis, with no human available to complete an interactive login for each connection.