Service-account authentication for the MCP server

Today the MCP server authenticates with a Personal Access Token, which is tied to an individual user's account. This request is for a way to connect the MCP server using a non-personal, service-level identity instead.

The use case is connecting an AI agent (e.g. an autonomous coding agent) to the Trigger.dev MCP to explore tasks and runs, without that access being tied to a specific team member's login. A dedicated service identity would allow access to be:

• Provisioned and revoked independently of any one person

• Kept intact when a team member leaves or rotates their token

• Cleanly separated between human and automated use

Ideally this pairs with scoped/read-only permissions, so a service identity can be granted read-only access for agents that only need to inspect data.