Expose profile source in MCP users

Add a ProfileSource schema to the MCP specification and include source\nin the Profile response schema so MCP clients can distinguish\nmanual and SCIM-managed users.\n\nWire the source field in the Profile mapper so list, get, and\ncreate user responses return the persisted profile source.

Signed-off-by: Cursor Agent <cursoragent@cursor.com>

pkg/server/api/mcp/v1/specification.yaml

@@ -187,6 +187,14 @@ components:
         - INACTIVE
       go.probo.inc/mcpgen/type: go.probo.inc/probo/pkg/coredata.ProfileState
 
+    ProfileSource:
+      type: string
+      enum:
+        - MANUAL
+        - SCIM
+        - SAML
+      go.probo.inc/mcpgen/type: go.probo.inc/probo/pkg/coredata.ProfileSource
+
     Regulation:
       type: string
       enum:
@@ -470,6 +478,7 @@ components:
         - email_address
         - additional_email_addresses
         - kind
+        - source
         - state
         - created_at
         - updated_at
@@ -496,6 +505,9 @@ components:
             - string
             - "null"
           description: Profile kind
+        source:
+          $ref: "#/components/schemas/ProfileSource"
+          description: Profile source (MANUAL, SCIM, or SAML)
         state:
           $ref: "#/components/schemas/ProfileState"
           description: Profile state (ACTIVE or INACTIVE)

pkg/server/api/mcp/v1/types/profile.go

@@ -24,6 +24,7 @@ func NewProfile(p *coredata.MembershipProfile) *Profile {
 		EmailAddress:             p.EmailAddress,
 		AdditionalEmailAddresses: p.AdditionalEmailAddresses,
 		Kind:                     p.Kind,
+		Source:                   p.Source,
 		State:                    p.State,
 		Position:                 p.Position,
 		ContractStartDate:        p.ContractStartDate,