When Workday detects a role change, syncs the updated job profile to Microsoft Identity Manager, updates ServiceNow group memberships, and notifies the employee in Microsoft Teams.

naftiko: '0.5'
info:
  label: Identity and Access Provisioning
  description: When Workday detects a role change, syncs the updated job profile to Microsoft Identity Manager, updates ServiceNow group memberships, and notifies the employee in Microsoft Teams.
  tags:
  - iam
  - identity
  - workday
  - microsoft-identity-manager
  - servicenow
  - microsoft-teams
  - security
capability:
  exposes:
  - type: mcp
    namespace: iam-provisioning
    port: 8080
    tools:
    - name: sync-role-change
      description: Given a Workday employee ID and new role, update Microsoft Identity Manager, adjust ServiceNow group access, and notify the employee in Teams.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The Workday employee ID.
      - name: new_role
        in: body
        type: string
        description: The new job role or title as defined in Workday.
      - name: effective_date
        in: body
        type: string
        description: Effective date of the role change in YYYY-MM-DD format.
      steps:
      - name: get-employee
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{employee_id}}'
      - name: update-mim
        type: call
        call: mim.update-person
        with:
          upn: '{{get-employee.work_email}}'
          job_title: '{{new_role}}'
          department: '{{get-employee.department}}'
          effective_date: '{{effective_date}}'
      - name: update-snow-group
        type: call
        call: servicenow.update-group-membership
        with:
          user_email: '{{get-employee.work_email}}'
          role: '{{new_role}}'
      - name: notify-employee
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{get-employee.work_email}}'
          text: 'Your system access has been updated for your new role: {{new_role}} (effective {{effective_date}}). Contact IT if you need additional access.'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: mim
    baseUri: https://3m-mim.internal/identitymanagement/api/v1
    authentication:
      type: bearer
      token: $secrets.mim_token
    resources:
    - name: persons
      path: /persons/{{upn}}
      inputParameters:
      - name: upn
        in: path
      operations:
      - name: update-person
        method: PATCH
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: group-members
      path: /table/sys_user_grmember
      operations:
      - name: update-group-membership
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Reconciles inventory cycle count discrepancies by comparing SAP book quantities against physical counts, logging adjustments, and alerting the warehouse manager in Teams.

naftiko: '0.5'
info:
  label: Inventory Cycle Count Reconciliation
  description: Reconciles inventory cycle count discrepancies by comparing SAP book quantities against physical counts, logging adjustments, and alerting the warehouse manager in Teams.
  tags:
  - inventory
  - warehouse
  - sap
  - sap-s4hana
  - microsoft-teams
  - manufacturing
capability:
  exposes:
  - type: mcp
    namespace: inventory-management
    port: 8080
    tools:
    - name: reconcile-cycle-count
      description: Given a plant, storage location, and count results, compare against SAP, post adjustments, and notify warehouse manager.
      inputParameters:
      - name: plant_code
        in: body
        type: string
        description: The 3M plant code.
      - name: storage_location
        in: body
        type: string
        description: SAP storage location.
      - name: material_number
        in: body
        type: string
        description: Material number counted.
      - name: physical_count
        in: body
        type: string
        description: Physical count quantity.
      steps:
      - name: get-book-quantity
        type: call
        call: sap.get-stock
        with:
          material: '{{material_number}}'
          plant: '{{plant_code}}'
          storage_location: '{{storage_location}}'
      - name: post-adjustment
        type: call
        call: sap.post-inventory-adjustment
        with:
          material: '{{material_number}}'
          plant: '{{plant_code}}'
          storage_location: '{{storage_location}}'
          book_qty: '{{get-book-quantity.available_qty}}'
          physical_qty: '{{physical_count}}'
      - name: notify-warehouse
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.warehouse_team_id
          channel_id: $secrets.warehouse_channel_id
          text: 'Cycle Count: {{material_number}} at {{plant_code}}/{{storage_location}} | Book: {{get-book-quantity.available_qty}} | Physical: {{physical_count}} | Adjustment: {{post-adjustment.document_number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/MM_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: stock
      path: /A_MaterialStock(Material='{{material}}',Plant='{{plant}}',StorageLocation='{{storage_location}}')
      inputParameters:
      - name: material
        in: path
      - name: plant
        in: path
      - name: storage_location
        in: path
      operations:
      - name: get-stock
        method: GET
    - name: adjustments
      path: /InventoryAdjustment
      operations:
      - name: post-inventory-adjustment
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Generates a vendor performance scorecard by pulling delivery and quality metrics from SAP, computing scores in Snowflake, and publishing results to a Power BI dashboard and the procurement Teams channel.

naftiko: '0.5'
info:
  label: Vendor Scorecard Generation
  description: Generates a vendor performance scorecard by pulling delivery and quality metrics from SAP, computing scores in Snowflake, and publishing results to a Power BI dashboard and the procurement Teams channel.
  tags:
  - procurement
  - vendor-management
  - sap
  - snowflake
  - power-bi
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: vendor-performance
    port: 8080
    tools:
    - name: generate-vendor-scorecard
      description: Given a vendor number and period, pull SAP metrics, compute scores, refresh Power BI, and notify procurement.
      inputParameters:
      - name: vendor_number
        in: body
        type: string
        description: The SAP vendor number.
      - name: period
        in: body
        type: string
        description: Evaluation period (e.g., 2026-Q1).
      steps:
      - name: get-vendor-metrics
        type: call
        call: sap.get-vendor-evaluation
        with:
          vendor: '{{vendor_number}}'
          period: '{{period}}'
      - name: compute-scorecard
        type: call
        call: snowflake.run-query
        with:
          statement: CALL PROCUREMENT.COMPUTE_VENDOR_SCORECARD('{{vendor_number}}', '{{period}}')
          warehouse: PROCUREMENT_WH
      - name: refresh-dashboard
        type: call
        call: powerbi.trigger-refresh
        with:
          group_id: $secrets.procurement_pbi_group
          dataset_id: $secrets.vendor_scorecard_dataset
      - name: notify-procurement
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.procurement_team_id
          channel_id: $secrets.procurement_channel_id
          text: Vendor scorecard for {{vendor_number}} ({{period}}) published. Dashboard refreshed.
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/MM_VENDOR_EVAL_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: vendor-evaluations
      path: /VendorEvaluation(Vendor='{{vendor}}',Period='{{period}}')
      inputParameters:
      - name: vendor
        in: path
      - name: period
        in: path
      operations:
      - name: get-vendor-evaluation
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://3m.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: run-query
        method: POST
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: dataset-refresh
      path: /groups/{{group_id}}/datasets/{{dataset_id}}/refreshes
      inputParameters:
      - name: group_id
        in: path
      - name: dataset_id
        in: path
      operations:
      - name: trigger-refresh
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Queries SAP S/4HANA for current raw material inventory levels by plant and storage location, returning available stock, reserved quantities, and reorder point status.

naftiko: '0.5'
info:
  label: Raw Material Inventory Lookup
  description: Queries SAP S/4HANA for current raw material inventory levels by plant and storage location, returning available stock, reserved quantities, and reorder point status.
  tags:
  - inventory
  - manufacturing
  - sap
  - sap-s4hana
  - supply-chain
  - materials
capability:
  exposes:
  - type: mcp
    namespace: inventory
    port: 8080
    tools:
    - name: get-raw-material-stock
      description: Look up raw material inventory in SAP S/4HANA by material number and plant. Returns available stock, reserved quantity, and reorder point.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number for the raw material.
      - name: plant_code
        in: body
        type: string
        description: The 3M plant code.
      call: sap.get-material-stock
      with:
        material_number: '{{material_number}}'
        plant: '{{plant_code}}'
      outputParameters:
      - name: available_qty
        type: string
        mapping: $.d.AvailableQuantity
      - name: reserved_qty
        type: string
        mapping: $.d.ReservedQuantity
      - name: reorder_point
        type: string
        mapping: $.d.ReorderPoint
      - name: unit_of_measure
        type: string
        mapping: $.d.BaseUnitOfMeasure
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/MM_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: material-stock
      path: /A_MaterialStock(Material='{{material_number}}',Plant='{{plant}}')
      inputParameters:
      - name: material_number
        in: path
      - name: plant
        in: path
      operations:
      - name: get-material-stock
        method: GET
        outputRawFormat: json

When a manufacturing line goes down, creates a SAP Plant Maintenance work order, opens a ServiceNow incident, and alerts the plant operations team in Microsoft Teams with downtime details.

naftiko: '0.5'
info:
  label: Manufacturing Line Downtime Alert
  description: When a manufacturing line goes down, creates a SAP Plant Maintenance work order, opens a ServiceNow incident, and alerts the plant operations team in Microsoft Teams with downtime details.
  tags:
  - manufacturing
  - downtime
  - sap
  - servicenow
  - microsoft-teams
  - maintenance
capability:
  exposes:
  - type: mcp
    namespace: plant-operations
    port: 8080
    tools:
    - name: report-line-downtime
      description: Given a production line ID and downtime reason, create a SAP PM work order, open a ServiceNow incident, and notify the plant operations team in Teams.
      inputParameters:
      - name: line_id
        in: body
        type: string
        description: The manufacturing line identifier.
      - name: plant_code
        in: body
        type: string
        description: The 3M plant code.
      - name: downtime_reason
        in: body
        type: string
        description: Reason for the production line downtime.
      - name: estimated_duration_hours
        in: body
        type: string
        description: Estimated downtime duration in hours.
      steps:
      - name: create-pm-order
        type: call
        call: sap.create-maintenance-order
        with:
          plant: '{{plant_code}}'
          equipment: '{{line_id}}'
          order_type: PM02
          short_text: 'Line Down: {{line_id}} — {{downtime_reason}}'
          priority: '1'
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Production Line Down: {{line_id}} at {{plant_code}}'
          description: '{{downtime_reason}} | Est. Duration: {{estimated_duration_hours}}h | SAP Order: {{create-pm-order.order_number}}'
          urgency: '1'
          category: manufacturing
      - name: notify-operations
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.plant_ops_team_id
          channel_id: $secrets.plant_ops_channel_id
          text: 'ALERT: Line {{line_id}} DOWN at {{plant_code}} | Reason: {{downtime_reason}} | Est: {{estimated_duration_hours}}h | SAP: {{create-pm-order.order_number}} | SNOW: {{create-incident.number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/PM_ORDER_CREATE_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: maintenance-orders
      path: /MaintenanceOrder
      operations:
      - name: create-maintenance-order
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Detects material cost variances in SAP cost accounting, logs an investigation task in Jira, and alerts the plant controller and finance team in Microsoft Teams.

naftiko: '0.5'
info:
  label: Material Cost Variance Alert
  description: Detects material cost variances in SAP cost accounting, logs an investigation task in Jira, and alerts the plant controller and finance team in Microsoft Teams.
  tags:
  - finance
  - cost-accounting
  - sap
  - jira
  - microsoft-teams
  - manufacturing
capability:
  exposes:
  - type: mcp
    namespace: cost-management
    port: 8080
    tools:
    - name: alert-cost-variance
      description: Given a material, plant, and variance details, retrieve SAP cost data, create Jira investigation, and alert finance.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number.
      - name: plant_code
        in: body
        type: string
        description: The 3M plant code.
      - name: variance_amount
        in: body
        type: string
        description: Cost variance amount in USD.
      - name: variance_type
        in: body
        type: string
        description: Type of variance (e.g., purchase_price, production_quantity, usage).
      steps:
      - name: get-cost-data
        type: call
        call: sap.get-material-cost
        with:
          material: '{{material_number}}'
          plant: '{{plant_code}}'
      - name: create-investigation
        type: call
        call: jira.create-issue
        with:
          project_key: FIN
          issuetype: Task
          summary: 'Cost Variance: {{material_number}} at {{plant_code}} (${{variance_amount}})'
          description: 'Variance type: {{variance_type}} | Amount: ${{variance_amount}} | Standard cost: {{get-cost-data.standard_cost}} | Actual cost: {{get-cost-data.actual_cost}}'
      - name: notify-finance
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.finance_team_id
          channel_id: $secrets.cost_alerts_channel_id
          text: 'Cost Variance Alert: {{material_number}} at {{plant_code}} | Type: {{variance_type}} | Amount: ${{variance_amount}} | Jira: {{create-investigation.key}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/CO_MATERIAL_COST_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: material-costs
      path: /MaterialCostEstimate(Material='{{material}}',Plant='{{plant}}')
      inputParameters:
      - name: material
        in: path
      - name: plant
        in: path
      operations:
      - name: get-material-cost
        method: GET
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Receives an invoice from SAP Ariba, validates vendor data against SAP S/4HANA master records, posts the accounting document, and notifies the AP team in Microsoft Teams.

naftiko: '0.5'
info:
  label: Invoice Processing and AP Automation
  description: Receives an invoice from SAP Ariba, validates vendor data against SAP S/4HANA master records, posts the accounting document, and notifies the AP team in Microsoft Teams.
  tags:
  - finance
  - accounts-payable
  - sap-ariba
  - sap
  - invoice-processing
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: accounts-payable
    port: 8080
    tools:
    - name: process-invoice
      description: Given an Ariba invoice ID, validate the vendor in SAP, post the AP document, and notify the AP team in Teams.
      inputParameters:
      - name: invoice_id
        in: body
        type: string
        description: The SAP Ariba invoice identifier.
      - name: vendor_id
        in: body
        type: string
        description: The SAP vendor master ID.
      steps:
      - name: get-invoice
        type: call
        call: ariba.get-invoice
        with:
          invoice_id: '{{invoice_id}}'
      - name: validate-vendor
        type: call
        call: sap.get-vendor
        with:
          vendor_id: '{{vendor_id}}'
      - name: post-ap-document
        type: call
        call: sap.post-invoice
        with:
          vendor_id: '{{vendor_id}}'
          amount: '{{get-invoice.total_amount}}'
          currency: '{{get-invoice.currency}}'
          invoice_date: '{{get-invoice.invoice_date}}'
          reference: '{{invoice_id}}'
      - name: notify-ap-team
        type: call
        call: msteams.send-message
        with:
          recipient_upn: ap-team@3m.com
          text: 'Invoice Posted: {{invoice_id}} | Vendor: {{validate-vendor.name}} | Amount: {{get-invoice.total_amount}} {{get-invoice.currency}} | SAP Doc: {{post-ap-document.document_number}}'
  consumes:
  - type: http
    namespace: ariba
    baseUri: https://openapi.ariba.com/api/invoice/v1
    authentication:
      type: bearer
      token: $secrets.ariba_token
    resources:
    - name: invoices
      path: /invoices/{{invoice_id}}
      inputParameters:
      - name: invoice_id
        in: path
      operations:
      - name: get-invoice
        method: GET
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/API_VENDOR_0001
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: vendors
      path: /A_Supplier('{{vendor_id}}')
      inputParameters:
      - name: vendor_id
        in: path
      operations:
      - name: get-vendor
        method: GET
    - name: invoice-documents
      path: /A_SupplierInvoice
      operations:
      - name: post-invoice
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves the current status, quantities, and scheduling details of a SAP production order for manufacturing floor visibility.

naftiko: '0.5'
info:
  label: Production Order Status Lookup
  description: Retrieves the current status, quantities, and scheduling details of a SAP production order for manufacturing floor visibility.
  tags:
  - manufacturing
  - production
  - sap
  - sap-s4hana
  - erp
  - scheduling
capability:
  exposes:
  - type: mcp
    namespace: production
    port: 8080
    tools:
    - name: get-production-order
      description: Look up a SAP production order by number. Returns status, planned and actual quantities, start and finish dates.
      inputParameters:
      - name: order_number
        in: body
        type: string
        description: The SAP production order number.
      call: sap.get-prod-order
      with:
        order_number: '{{order_number}}'
      outputParameters:
      - name: status
        type: string
        mapping: $.d.OrderStatus
      - name: planned_qty
        type: string
        mapping: $.d.TotalPlannedQty
      - name: actual_qty
        type: string
        mapping: $.d.ActualQuantityDelivered
      - name: start_date
        type: string
        mapping: $.d.BasicStartDate
      - name: finish_date
        type: string
        mapping: $.d.BasicEndDate
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/PP_PRODUCTION_ORDER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: production-orders
      path: /A_ProductionOrder('{{order_number}}')
      inputParameters:
      - name: order_number
        in: path
      operations:
      - name: get-prod-order
        method: GET
        outputRawFormat: json

When a qualifying LinkedIn signal occurs, enriches the Salesforce contact record with current profile data, syncs to HubSpot, and alerts the owning sales rep in Microsoft Teams.

naftiko: '0.5'
info:
  label: Sales Lead Enrichment
  description: When a qualifying LinkedIn signal occurs, enriches the Salesforce contact record with current profile data, syncs to HubSpot, and alerts the owning sales rep in Microsoft Teams.
  tags:
  - sales
  - crm
  - salesforce
  - hubspot
  - linkedin
  - microsoft-teams
  - lead-management
capability:
  exposes:
  - type: mcp
    namespace: sales-intelligence
    port: 8080
    tools:
    - name: enrich-lead-from-linkedin
      description: Given a LinkedIn member URN and Salesforce contact ID, enrich the Salesforce record, sync to HubSpot, and notify the owning rep in Microsoft Teams.
      inputParameters:
      - name: linkedin_member_urn
        in: body
        type: string
        description: The LinkedIn member URN for the contact.
      - name: salesforce_contact_id
        in: body
        type: string
        description: The Salesforce contact record ID to enrich.
      - name: signal_type
        in: body
        type: string
        description: The LinkedIn signal type (e.g., job_change, content_share, profile_view).
      - name: rep_upn
        in: body
        type: string
        description: The Microsoft UPN of the owning sales rep.
      steps:
      - name: get-linkedin-profile
        type: call
        call: linkedin.get-profile
        with:
          member_urn: '{{linkedin_member_urn}}'
      - name: update-salesforce
        type: call
        call: salesforce.update-contact
        with:
          contact_id: '{{salesforce_contact_id}}'
          title: '{{get-linkedin-profile.headline}}'
          company: '{{get-linkedin-profile.current_company}}'
          linkedin_url: '{{get-linkedin-profile.profile_url}}'
      - name: sync-hubspot
        type: call
        call: hubspot.update-contact
        with:
          email: '{{update-salesforce.email}}'
          jobtitle: '{{get-linkedin-profile.headline}}'
          company: '{{get-linkedin-profile.current_company}}'
          hs_lead_status: OPEN_DEAL
      - name: alert-rep
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{rep_upn}}'
          text: 'Warm Lead Signal: {{get-linkedin-profile.first_name}} {{get-linkedin-profile.last_name}} | Signal: {{signal_type}} | Title: {{get-linkedin-profile.headline}} | Company: {{get-linkedin-profile.current_company}} | Salesforce updated.'
  consumes:
  - type: http
    namespace: linkedin
    baseUri: https://api.linkedin.com/v2
    authentication:
      type: bearer
      token: $secrets.linkedin_token
    resources:
    - name: profiles
      path: /people/{{member_urn}}
      inputParameters:
      - name: member_urn
        in: path
      operations:
      - name: get-profile
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: contacts
      path: /sobjects/Contact/{{contact_id}}
      inputParameters:
      - name: contact_id
        in: path
      operations:
      - name: update-contact
        method: PATCH
  - type: http
    namespace: hubspot
    baseUri: https://api.hubapi.com/crm/v3
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: contacts
      path: /objects/contacts/{{email}}
      inputParameters:
      - name: email
        in: path
      operations:
      - name: update-contact
        method: PATCH
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Posts a goods receipt in SAP against a purchase order, triggers a three-way match check, and notifies accounts payable in Microsoft Teams if discrepancies are found.

naftiko: '0.5'
info:
  label: SAP Goods Receipt Processing
  description: Posts a goods receipt in SAP against a purchase order, triggers a three-way match check, and notifies accounts payable in Microsoft Teams if discrepancies are found.
  tags:
  - supply-chain
  - procurement
  - sap
  - sap-s4hana
  - microsoft-teams
  - accounts-payable
capability:
  exposes:
  - type: mcp
    namespace: goods-receipt
    port: 8080
    tools:
    - name: process-goods-receipt
      description: Given a PO number, material, and received quantity, post goods receipt in SAP and notify AP of any discrepancies.
      inputParameters:
      - name: po_number
        in: body
        type: string
        description: The SAP purchase order number.
      - name: material_number
        in: body
        type: string
        description: The material number received.
      - name: received_quantity
        in: body
        type: string
        description: Quantity actually received.
      - name: storage_location
        in: body
        type: string
        description: Storage location for the received goods.
      steps:
      - name: post-goods-receipt
        type: call
        call: sap.post-gr
        with:
          po_number: '{{po_number}}'
          material: '{{material_number}}'
          quantity: '{{received_quantity}}'
          storage_location: '{{storage_location}}'
      - name: check-three-way-match
        type: call
        call: sap.check-invoice-match
        with:
          po_number: '{{po_number}}'
          gr_document: '{{post-goods-receipt.document_number}}'
      - name: notify-ap
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.ap_team_id
          channel_id: $secrets.ap_channel_id
          text: 'Goods Receipt posted: PO {{po_number}} | Material: {{material_number}} | Qty: {{received_quantity}} | GR Doc: {{post-goods-receipt.document_number}} | Match Status: {{check-three-way-match.match_status}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/MM_GOODS_RECEIPT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: goods-receipts
      path: /GoodsReceipt
      operations:
      - name: post-gr
        method: POST
    - name: invoice-match
      path: /ThreeWayMatch(PO='{{po_number}}',GR='{{gr_document}}')
      inputParameters:
      - name: po_number
        in: path
      - name: gr_document
        in: path
      operations:
      - name: check-invoice-match
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Triggers SAP S/4HANA period-close tasks, pulls consolidated financials into Oracle Hyperion for intercompany elimination, and refreshes the Power BI executive financial dashboard.

naftiko: '0.5'
info:
  label: Financial Consolidation and Close
  description: Triggers SAP S/4HANA period-close tasks, pulls consolidated financials into Oracle Hyperion for intercompany elimination, and refreshes the Power BI executive financial dashboard.
  tags:
  - finance
  - financial-close
  - sap
  - oracle-hyperion
  - power-bi
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: finance-close
    port: 8080
    tools:
    - name: run-period-close
      description: Trigger SAP period-close postings for a company code and fiscal period, sync results to Oracle Hyperion, and refresh the Power BI financial dashboard.
      inputParameters:
      - name: company_code
        in: body
        type: string
        description: SAP company code (e.g., 1000 for 3M US).
      - name: fiscal_year
        in: body
        type: string
        description: Four-digit fiscal year (e.g., 2025).
      - name: fiscal_period
        in: body
        type: string
        description: Two-digit fiscal period (e.g., 03 for March).
      steps:
      - name: trigger-close
        type: call
        call: sap.run-period-close
        with:
          company_code: '{{company_code}}'
          fiscal_year: '{{fiscal_year}}'
          fiscal_period: '{{fiscal_period}}'
      - name: sync-hyperion
        type: call
        call: oracle-hyperion.load-data
        with:
          application: 3M_CONSOL
          period: '{{fiscal_year}}.{{fiscal_period}}'
          scenario: Actuals
      - name: refresh-dashboard
        type: call
        call: powerbi.refresh-dataset
        with:
          dataset_name: executive-financial-{{fiscal_year}}-{{fiscal_period}}
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/FAC_CLOSE_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: period-close
      path: /PeriodClose
      operations:
      - name: run-period-close
        method: POST
  - type: http
    namespace: oracle-hyperion
    baseUri: https://3m-hyperion.oracle.com/HyperionPlanning/rest/v3
    authentication:
      type: basic
      username: $secrets.hyperion_user
      password: $secrets.hyperion_password
    resources:
    - name: data-loads
      path: /applications/{{application}}/dataLoads
      inputParameters:
      - name: application
        in: path
      operations:
      - name: load-data
        method: POST
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets/{{dataset_name}}/refreshes
      inputParameters:
      - name: dataset_name
        in: path
      operations:
      - name: refresh-dataset
        method: POST

Reconciles travel expenses by pulling reports from SAP Concur, matching against SAP FI postings, and creating a ServiceNow ticket for any discrepancies found.

naftiko: '0.5'
info:
  label: Travel Expense Reconciliation
  description: Reconciles travel expenses by pulling reports from SAP Concur, matching against SAP FI postings, and creating a ServiceNow ticket for any discrepancies found.
  tags:
  - finance
  - travel
  - sap-concur
  - sap
  - servicenow
  - expense-management
capability:
  exposes:
  - type: mcp
    namespace: travel-finance
    port: 8080
    tools:
    - name: reconcile-travel-expenses
      description: Given an employee ID and period, pull Concur reports, match against SAP postings, and flag discrepancies.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The employee ID in Concur.
      - name: period
        in: body
        type: string
        description: The reconciliation period (e.g., 2026-03).
      steps:
      - name: get-concur-reports
        type: call
        call: concur.get-expense-reports
        with:
          employee_id: '{{employee_id}}'
          period: '{{period}}'
      - name: get-sap-postings
        type: call
        call: sap.get-travel-postings
        with:
          employee_id: '{{employee_id}}'
          period: '{{period}}'
      - name: create-discrepancy-ticket
        type: call
        call: servicenow.create-case
        with:
          short_description: 'Travel expense discrepancy: {{employee_id}} ({{period}})'
          description: 'Concur total: {{get-concur-reports.total_amount}} | SAP total: {{get-sap-postings.total_amount}} | Reports: {{get-concur-reports.report_count}}'
          category: finance
  consumes:
  - type: http
    namespace: concur
    baseUri: https://us.api.concursolutions.com/api/v3.0
    authentication:
      type: bearer
      token: $secrets.concur_token
    resources:
    - name: expense-reports
      path: /expense/reports
      inputParameters:
      - name: employee_id
        in: query
      - name: period
        in: query
      operations:
      - name: get-expense-reports
        method: GET
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/FI_TRAVEL_EXPENSE_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: travel-postings
      path: /TravelExpensePosting
      inputParameters:
      - name: employee_id
        in: query
      - name: period
        in: query
      operations:
      - name: get-travel-postings
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: cases
      path: /table/sn_customerservice_case
      operations:
      - name: create-case
        method: POST

When a new API is published to Kong Gateway, registers it in Confluence as documentation, creates a Datadog API monitor, and notifies the API governance team in Microsoft Teams.

naftiko: '0.5'
info:
  label: API Lifecycle Management
  description: When a new API is published to Kong Gateway, registers it in Confluence as documentation, creates a Datadog API monitor, and notifies the API governance team in Microsoft Teams.
  tags:
  - api-management
  - kong
  - confluence
  - datadog
  - microsoft-teams
  - governance
capability:
  exposes:
  - type: mcp
    namespace: api-governance
    port: 8080
    tools:
    - name: register-new-api
      description: Given a Kong service name and API metadata, create a Confluence doc page, add a Datadog availability monitor, and notify the API governance team in Teams.
      inputParameters:
      - name: kong_service_name
        in: body
        type: string
        description: The Kong Gateway service name.
      - name: api_title
        in: body
        type: string
        description: Human-readable API title.
      - name: api_owner_team
        in: body
        type: string
        description: Team email owning this API.
      - name: confluence_space_key
        in: body
        type: string
        description: Confluence space key to publish docs to.
      steps:
      - name: create-doc-page
        type: call
        call: confluence.create-page
        with:
          space_key: '{{confluence_space_key}}'
          title: 'API: {{api_title}}'
          body: 'Kong service: {{kong_service_name}} | Owner: {{api_owner_team}}'
      - name: create-monitor
        type: call
        call: datadog.create-monitor
        with:
          name: 'API Availability: {{api_title}}'
          type: api
          message: API {{api_title}} ({{kong_service_name}}) is unavailable. Notify {{api_owner_team}}
      - name: notify-governance
        type: call
        call: msteams.send-message
        with:
          recipient_upn: api-governance@3m.com
          text: 'New API Registered: {{api_title}} | Kong: {{kong_service_name}} | Owner: {{api_owner_team}} | Docs: {{create-doc-page.url}} | Monitor: {{create-monitor.id}}'
  consumes:
  - type: http
    namespace: confluence
    baseUri: https://3m.atlassian.net/wiki/rest/api
    authentication:
      type: basic
      username: $secrets.confluence_user
      password: $secrets.confluence_token
    resources:
    - name: pages
      path: /content
      operations:
      - name: create-page
        method: POST
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: monitors
      path: /monitor
      operations:
      - name: create-monitor
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Verifies nightly Commvault and Veritas NetBackup job results, logs failures to Datadog, and opens a ServiceNow incident for any backup that did not complete successfully.

naftiko: '0.5'
info:
  label: Backup and Recovery Verification
  description: Verifies nightly Commvault and Veritas NetBackup job results, logs failures to Datadog, and opens a ServiceNow incident for any backup that did not complete successfully.
  tags:
  - backup
  - recovery
  - commvault
  - servicenow
  - datadog
  - infrastructure
capability:
  exposes:
  - type: mcp
    namespace: backup-ops
    port: 8080
    tools:
    - name: verify-backup-job
      description: Given a Commvault job ID, check its completion status, log to Datadog, and open a ServiceNow incident if the backup failed.
      inputParameters:
      - name: job_id
        in: body
        type: string
        description: The Commvault backup job ID.
      - name: backup_set_name
        in: body
        type: string
        description: Name of the backup set or client.
      - name: environment
        in: body
        type: string
        description: Environment the backup covers (prod, dr, staging).
      steps:
      - name: get-job-status
        type: call
        call: commvault.get-job
        with:
          job_id: '{{job_id}}'
      - name: log-result
        type: call
        call: datadog.create-event
        with:
          title: 'Backup Job {{job_id}}: {{get-job-status.status}}'
          text: 'BackupSet: {{backup_set_name}} | Env: {{environment}} | Size: {{get-job-status.size_gb}}GB | Duration: {{get-job-status.duration_minutes}}min'
          alert_type: info
          tags: backup:{{backup_set_name}},env:{{environment}}
      - name: open-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Backup failure: {{backup_set_name}} ({{environment}})'
          description: 'Commvault job {{job_id}} failed for {{backup_set_name}} in {{environment}}. Status: {{get-job-status.status}}. Datadog: {{log-result.url}}'
          category: backup_failure
          urgency: '2'
  consumes:
  - type: http
    namespace: commvault
    baseUri: https://3m-commvault.internal/commandcenter/api
    authentication:
      type: bearer
      token: $secrets.commvault_token
    resources:
    - name: jobs
      path: /Job/{{job_id}}
      inputParameters:
      - name: job_id
        in: path
      operations:
      - name: get-job
        method: GET
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST

Provisions IT equipment for a new hire by creating a ServiceNow request, linking the Workday employee record, and notifying the hiring manager and IT support in Teams.

naftiko: '0.5'
info:
  label: New Hire Equipment Provisioning
  description: Provisions IT equipment for a new hire by creating a ServiceNow request, linking the Workday employee record, and notifying the hiring manager and IT support in Teams.
  tags:
  - hr
  - it-service
  - servicenow
  - workday
  - microsoft-teams
  - onboarding
capability:
  exposes:
  - type: mcp
    namespace: hr-it-provisioning
    port: 8080
    tools:
    - name: provision-new-hire-equipment
      description: Given an employee ID, role, and start date, create equipment request in ServiceNow, verify Workday record, and notify stakeholders.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The Workday employee ID.
      - name: role
        in: body
        type: string
        description: The new hire's role/job title.
      - name: start_date
        in: body
        type: string
        description: Employee start date.
      - name: manager_upn
        in: body
        type: string
        description: UPN of the hiring manager.
      steps:
      - name: get-employee
        type: call
        call: workday.get-worker
        with:
          employee_id: '{{employee_id}}'
      - name: create-equipment-request
        type: call
        call: servicenow.create-request
        with:
          short_description: 'Equipment provisioning: {{get-employee.full_name}} ({{role}})'
          description: 'New hire starting {{start_date}}. Role: {{role}}. Manager: {{manager_upn}}'
          category: hardware
          requested_for: '{{employee_id}}'
      - name: notify-manager
        type: call
        call: msteams.send-chat
        with:
          recipient_upn: '{{manager_upn}}'
          text: 'Equipment request created for {{get-employee.full_name}} ({{role}}), starting {{start_date}}. ServiceNow: {{create-equipment-request.number}}'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd5-impl-services1.workday.com/ccx/api/v1/3m
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /workers/{{employee_id}}
      inputParameters:
      - name: employee_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: requests
      path: /table/sc_request
      operations:
      - name: create-request
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: chats
      path: /users/{{recipient_upn}}/chats
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-chat
        method: POST

Triggers a demand forecast model run in Snowflake, pushes forecast data back to SAP APO, and publishes updated forecast charts to the supply planning Teams channel.

naftiko: '0.5'
info:
  label: Demand Forecast Refresh
  description: Triggers a demand forecast model run in Snowflake, pushes forecast data back to SAP APO, and publishes updated forecast charts to the supply planning Teams channel.
  tags:
  - supply-chain
  - forecasting
  - snowflake
  - sap
  - microsoft-teams
  - planning
capability:
  exposes:
  - type: mcp
    namespace: demand-planning
    port: 8080
    tools:
    - name: refresh-demand-forecast
      description: Given a product family and horizon, run forecast model, update SAP APO, and notify supply planning.
      inputParameters:
      - name: product_family
        in: body
        type: string
        description: The product family code for forecasting.
      - name: forecast_horizon_months
        in: body
        type: string
        description: Number of months to forecast ahead.
      steps:
      - name: run-forecast-model
        type: call
        call: snowflake.run-query
        with:
          statement: CALL SUPPLY_CHAIN.RUN_DEMAND_FORECAST('{{product_family}}', {{forecast_horizon_months}})
          warehouse: PLANNING_WH
      - name: push-to-sap
        type: call
        call: sap.update-forecast
        with:
          product_family: '{{product_family}}'
          forecast_data: '{{run-forecast-model.result}}'
      - name: notify-planning
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.supply_planning_team_id
          channel_id: $secrets.planning_channel_id
          text: Demand forecast refreshed for {{product_family}} ({{forecast_horizon_months}}M horizon). SAP APO updated.
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://3m.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: run-query
        method: POST
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/APO_FORECAST_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: forecasts
      path: /ForecastData
      operations:
      - name: update-forecast
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Reviews a customer credit limit by pulling AR aging from SAP, checking Salesforce account health, and routing the approval decision to the credit manager in Teams.

naftiko: '0.5'
info:
  label: Customer Credit Limit Review
  description: Reviews a customer credit limit by pulling AR aging from SAP, checking Salesforce account health, and routing the approval decision to the credit manager in Teams.
  tags:
  - finance
  - credit-management
  - sap
  - salesforce
  - microsoft-teams
  - accounts-receivable
capability:
  exposes:
  - type: mcp
    namespace: credit-management
    port: 8080
    tools:
    - name: review-credit-limit
      description: Given a customer number and requested limit, pull AR data, check CRM health, and route for approval.
      inputParameters:
      - name: customer_number
        in: body
        type: string
        description: The SAP customer account number.
      - name: requested_limit
        in: body
        type: string
        description: Requested credit limit in USD.
      - name: salesforce_account_id
        in: body
        type: string
        description: Salesforce account ID.
      - name: credit_manager_upn
        in: body
        type: string
        description: UPN of the credit manager.
      steps:
      - name: get-ar-aging
        type: call
        call: sap.get-ar-aging
        with:
          customer: '{{customer_number}}'
      - name: get-account-health
        type: call
        call: salesforce.get-account
        with:
          account_id: '{{salesforce_account_id}}'
      - name: route-approval
        type: call
        call: msteams.send-chat
        with:
          recipient_upn: '{{credit_manager_upn}}'
          text: 'Credit Limit Review: Customer {{customer_number}} | Requested: ${{requested_limit}} | Current AR: ${{get-ar-aging.total_outstanding}} | Overdue: ${{get-ar-aging.overdue_amount}} | CRM Revenue: ${{get-account-health.annual_revenue}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/FI_AR_AGING_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: ar-aging
      path: /CustomerAging(Customer='{{customer}}')
      inputParameters:
      - name: customer
        in: path
      operations:
      - name: get-ar-aging
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: accounts
      path: /sobjects/Account/{{account_id}}
      inputParameters:
      - name: account_id
        in: path
      operations:
      - name: get-account
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: chats
      path: /users/{{recipient_upn}}/chats
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-chat
        method: POST

Queries Datadog for the current health status of a monitored service, returning monitor state, last triggered time, and alert details.

naftiko: '0.5'
info:
  label: Datadog Service Health Check
  description: Queries Datadog for the current health status of a monitored service, returning monitor state, last triggered time, and alert details.
  tags:
  - monitoring
  - datadog
  - observability
  - infrastructure
capability:
  exposes:
  - type: mcp
    namespace: observability
    port: 8080
    tools:
    - name: get-monitor-status
      description: Check the status of a Datadog monitor by monitor ID. Returns overall state, last triggered timestamp, and message.
      inputParameters:
      - name: monitor_id
        in: body
        type: string
        description: The Datadog monitor ID.
      call: datadog.get-monitor
      with:
        monitor_id: '{{monitor_id}}'
      outputParameters:
      - name: overall_state
        type: string
        mapping: $.overall_state
      - name: name
        type: string
        mapping: $.name
      - name: last_triggered
        type: string
        mapping: $.overall_state_modified
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: bearer
      token: $secrets.datadog_api_key
    inputParameters:
    - name: DD-APPLICATION-KEY
      in: header
      value: $secrets.datadog_app_key
    resources:
    - name: monitors
      path: /monitor/{{monitor_id}}
      inputParameters:
      - name: monitor_id
        in: path
      operations:
      - name: get-monitor
        method: GET

Looks up a SAP S/4HANA purchase order by number and returns header status, vendor, total value, and open line items. Used by procurement and finance teams to check PO health without logging into SAP.

naftiko: '0.5'
info:
  label: SAP Purchase Order Status
  description: Looks up a SAP S/4HANA purchase order by number and returns header status, vendor, total value, and open line items. Used by procurement and finance teams to check PO health without logging into SAP.
  tags:
  - procurement
  - erp
  - sap
  - sap-s4hana
  - purchase-order
  - finance
capability:
  exposes:
  - type: mcp
    namespace: erp-procurement
    port: 8080
    tools:
    - name: get-purchase-order
      description: Look up a SAP S/4HANA purchase order by PO number. Returns header status, vendor name, total value, currency, and delivery date.
      inputParameters:
      - name: po_number
        in: body
        type: string
        description: The SAP purchase order number (10-digit).
      call: sap.get-po
      with:
        po_number: '{{po_number}}'
      outputParameters:
      - name: status
        type: string
        mapping: $.d.OverallStatus
      - name: vendor
        type: string
        mapping: $.d.Supplier.CompanyName
      - name: total_value
        type: string
        mapping: $.d.TotalAmount
      - name: currency
        type: string
        mapping: $.d.TransactionCurrency
      - name: delivery_date
        type: string
        mapping: $.d.DeliveryDate
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/MM_PUR_PO_MAINT_V2_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    inputParameters:
    - name: Accept
      in: header
      value: application/json
    - name: sap-client
      in: header
      value: '100'
    resources:
    - name: purchase-orders
      path: /A_PurchaseOrder('{{po_number}}')
      inputParameters:
      - name: po_number
        in: path
      operations:
      - name: get-po
        method: GET
        outputRawFormat: xml

When AWS or Azure cost anomaly detection fires, annotates in Datadog, opens a ServiceNow cost-management ticket, and posts a summary to the FinOps Microsoft Teams channel.

naftiko: '0.5'
info:
  label: Cloud Cost Anomaly Response
  description: When AWS or Azure cost anomaly detection fires, annotates in Datadog, opens a ServiceNow cost-management ticket, and posts a summary to the FinOps Microsoft Teams channel.
  tags:
  - finops
  - cloud-cost
  - aws
  - azure
  - datadog
  - servicenow
  - microsoft-teams
  - cost-management
capability:
  exposes:
  - type: mcp
    namespace: finops
    port: 8080
    tools:
    - name: handle-cost-anomaly
      description: Given a cloud cost anomaly event (AWS or Azure), create a Datadog annotation, open a ServiceNow cost-management ticket, and alert the FinOps team in Microsoft Teams.
      inputParameters:
      - name: cloud_provider
        in: body
        type: string
        description: Cloud provider where the anomaly was detected (aws or azure).
      - name: anomaly_id
        in: body
        type: string
        description: The anomaly identifier from the cloud provider.
      - name: service_name
        in: body
        type: string
        description: The cloud service or resource group with the anomaly.
      - name: estimated_overage_usd
        in: body
        type: number
        description: Estimated cost overage in USD.
      - name: business_unit
        in: body
        type: string
        description: The 3M business unit responsible for the spend.
      steps:
      - name: annotate-datadog
        type: call
        call: datadog.create-event
        with:
          title: '{{cloud_provider}} Cost Anomaly: {{service_name}}'
          text: 'Anomaly {{anomaly_id}} — estimated overage: ${{estimated_overage_usd}} — BU: {{business_unit}}'
          alert_type: warning
          tags: cloud_provider:{{cloud_provider}},business_unit:{{business_unit}}
      - name: open-ticket
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Cloud Cost Anomaly: {{cloud_provider}} {{service_name}} — ${{estimated_overage_usd}} overage'
          description: 'Anomaly {{anomaly_id}} on {{service_name}} ({{cloud_provider}}). BU: {{business_unit}}. Datadog event: {{annotate-datadog.id}}'
          category: cloud_cost
          assigned_group: FinOps
      - name: notify-finops
        type: call
        call: msteams.send-message
        with:
          recipient_upn: finops-alerts@3m.com
          text: 'Cost Anomaly: {{cloud_provider}} | Service: {{service_name}} | Overage: ${{estimated_overage_usd}} | BU: {{business_unit}} | Ticket: {{open-ticket.number}} | Datadog: {{annotate-datadog.url}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/task
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

When a new engineer is added to GitHub org, provisions Jira and Confluence access, opens a ServiceNow onboarding ticket, and sends a welcome message with resource links via Microsoft Teams.

naftiko: '0.5'
info:
  label: Developer Onboarding
  description: When a new engineer is added to GitHub org, provisions Jira and Confluence access, opens a ServiceNow onboarding ticket, and sends a welcome message with resource links via Microsoft Teams.
  tags:
  - developer-experience
  - onboarding
  - github
  - jira
  - confluence
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: dev-onboarding
    port: 8080
    tools:
    - name: onboard-developer
      description: Given a GitHub username and Workday employee ID, provision Jira/Confluence, create a ServiceNow onboarding task, and send Teams welcome message.
      inputParameters:
      - name: github_username
        in: body
        type: string
        description: The new developer's GitHub username.
      - name: employee_id
        in: body
        type: string
        description: The Workday employee ID.
      - name: team_name
        in: body
        type: string
        description: The engineering team the developer is joining.
      steps:
      - name: get-employee
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{employee_id}}'
      - name: add-to-jira
        type: call
        call: jira.add-user-to-project
        with:
          username: '{{get-employee.work_email}}'
          project_key: '{{team_name}}'
          role: Developer
      - name: open-onboarding-task
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Developer onboarding: {{get-employee.full_name}} — {{team_name}}'
          category: dev_onboarding
          assigned_group: DevOps_Platform
      - name: send-welcome
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{get-employee.work_email}}'
          text: 'Welcome to 3M Engineering, {{get-employee.first_name}}! GitHub: {{github_username}} | Team: {{team_name}} | Jira access provisioned | Onboarding ticket: {{open-onboarding-task.number}}'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: project-roles
      path: /project/{{project_key}}/role
      inputParameters:
      - name: project_key
        in: path
      operations:
      - name: add-user-to-project
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/task
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Creates a patent filing tracking entry in Jira, uploads invention disclosure documents to SharePoint, and notifies the IP legal team in Microsoft Teams.

naftiko: '0.5'
info:
  label: Patent Filing Tracker
  description: Creates a patent filing tracking entry in Jira, uploads invention disclosure documents to SharePoint, and notifies the IP legal team in Microsoft Teams.
  tags:
  - intellectual-property
  - legal
  - jira
  - sharepoint
  - microsoft-teams
  - research
capability:
  exposes:
  - type: mcp
    namespace: ip-management
    port: 8080
    tools:
    - name: track-patent-filing
      description: Given invention details, create a Jira tracker, upload documents to SharePoint, and notify IP legal.
      inputParameters:
      - name: invention_title
        in: body
        type: string
        description: Title of the invention.
      - name: inventor_names
        in: body
        type: string
        description: Comma-separated list of inventor names.
      - name: technology_area
        in: body
        type: string
        description: Technology domain (e.g., adhesives, abrasives, healthcare).
      steps:
      - name: create-patent-ticket
        type: call
        call: jira.create-issue
        with:
          project_key: IP
          issuetype: Epic
          summary: 'Patent Filing: {{invention_title}}'
          description: 'Inventors: {{inventor_names}} | Technology: {{technology_area}}'
      - name: create-document-folder
        type: call
        call: sharepoint.create-folder
        with:
          site_id: $secrets.ip_site_id
          parent_path: /Patents/{{technology_area}}
          folder_name: '{{create-patent-ticket.key}}-{{invention_title}}'
      - name: notify-ip-legal
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.ip_legal_team_id
          channel_id: $secrets.ip_legal_channel_id
          text: 'New patent filing initiated: {{invention_title}} | Inventors: {{inventor_names}} | Tech: {{technology_area}} | Jira: {{create-patent-ticket.key}}'
  consumes:
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: folders
      path: /{{site_id}}/drive/root:{{parent_path}}/{{folder_name}}
      inputParameters:
      - name: site_id
        in: path
      - name: parent_path
        in: path
      - name: folder_name
        in: path
      operations:
      - name: create-folder
        method: PUT
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

When a GitHub Dependabot or SonarQube alert fires, enriches the finding with Datadog service context, opens a Jira security ticket, and routes a ServiceNow change request for high-severity vulnerabilities.

naftiko: '0.5'
info:
  label: Security Vulnerability Triage
  description: When a GitHub Dependabot or SonarQube alert fires, enriches the finding with Datadog service context, opens a Jira security ticket, and routes a ServiceNow change request for high-severity vulnerabilities.
  tags:
  - security
  - devsecops
  - github
  - datadog
  - jira
  - servicenow
  - vulnerability-management
capability:
  exposes:
  - type: mcp
    namespace: security-ops
    port: 8080
    tools:
    - name: triage-vulnerability
      description: Given a GitHub vulnerability alert (Dependabot or SonarQube), fetch Datadog service metadata, open a Jira security ticket, and for CVSS >= 7.0 also open a ServiceNow change request.
      inputParameters:
      - name: repository
        in: body
        type: string
        description: The GitHub repository in owner/repo format.
      - name: alert_number
        in: body
        type: string
        description: The GitHub Dependabot or code scanning alert number.
      - name: cve_id
        in: body
        type: string
        description: The CVE identifier (e.g., CVE-2024-12345).
      - name: cvss_score
        in: body
        type: number
        description: The CVSS score of the vulnerability (0.0–10.0).
      - name: affected_package
        in: body
        type: string
        description: The name of the affected library or package.
      - name: service_name
        in: body
        type: string
        description: The Datadog service name associated with this repository.
      steps:
      - name: get-service-context
        type: call
        call: datadog.get-service
        with:
          service_name: '{{service_name}}'
      - name: create-jira-ticket
        type: call
        call: jira.create-issue
        with:
          project_key: SEC
          issuetype: Security Vulnerability
          summary: '[{{cve_id}}] {{affected_package}} in {{repository}} — CVSS {{cvss_score}}'
          description: 'CVE: {{cve_id}}

            Repo: {{repository}}

            Alert: {{alert_number}}

            Package: {{affected_package}}

            CVSS: {{cvss_score}}

            Service owner: {{get-service-context.team}}'
          priority: High
      - name: open-change-request
        type: call
        call: servicenow.create-change-request
        with:
          short_description: 'Security patch: {{cve_id}} in {{affected_package}} ({{repository}})'
          description: 'High-severity vulnerability {{cve_id}} (CVSS {{cvss_score}}) found in {{affected_package}}. Jira: {{create-jira-ticket.key}}. Service: {{service_name}} owned by {{get-service-context.team}}.'
          category: security_patch
          risk: moderate
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v2
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: services
      path: /services/definitions/{{service_name}}
      inputParameters:
      - name: service_name
        in: path
      operations:
      - name: get-service
        method: GET
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: change-requests
      path: /table/change_request
      operations:
      - name: create-change-request
        method: POST

When a SAP master data record is created or changed, routes the record for approval via ServiceNow, and notifies the responsible data steward in Microsoft Teams.

naftiko: '0.5'
info:
  label: SAP Master Data Governance Alert
  description: When a SAP master data record is created or changed, routes the record for approval via ServiceNow, and notifies the responsible data steward in Microsoft Teams.
  tags:
  - master-data
  - sap
  - data-governance
  - servicenow
  - microsoft-teams
  - erp
capability:
  exposes:
  - type: mcp
    namespace: mdg
    port: 8080
    tools:
    - name: route-master-data-approval
      description: Given a SAP master data record type, ID, and change type, create a ServiceNow approval task and notify the data steward in Teams.
      inputParameters:
      - name: record_type
        in: body
        type: string
        description: Master data type (material, vendor, customer).
      - name: record_id
        in: body
        type: string
        description: The SAP master data record ID.
      - name: change_type
        in: body
        type: string
        description: Change type (create, update, block, delete).
      - name: data_steward_upn
        in: body
        type: string
        description: Microsoft UPN of the responsible data steward.
      steps:
      - name: create-approval-task
        type: call
        call: servicenow-mdg.create-task
        with:
          short_description: 'MDG approval: {{change_type}} {{record_type}} {{record_id}}'
          description: 'Record: {{record_id}} ({{record_type}}) | Change: {{change_type}}'
          category: master_data_governance
          assigned_to: '{{data_steward_upn}}'
      - name: notify-steward
        type: call
        call: msteams-mdg.send-message
        with:
          recipient_upn: '{{data_steward_upn}}'
          text: 'MDG Review Required: {{change_type}} on {{record_type}} {{record_id}} | ServiceNow: {{create-approval-task.number}}'
  consumes:
  - type: http
    namespace: servicenow-mdg
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/task
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: msteams-mdg
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Submits a SQL query to 3M's Snowflake data warehouse and returns the result set for ad-hoc analytics and data exploration.

naftiko: '0.5'
info:
  label: Snowflake Query Execution
  description: Submits a SQL query to 3M's Snowflake data warehouse and returns the result set for ad-hoc analytics and data exploration.
  tags:
  - analytics
  - snowflake
  - data-warehouse
  - sql
capability:
  exposes:
  - type: mcp
    namespace: data-analytics
    port: 8080
    tools:
    - name: run-query
      description: Execute a SQL query against the 3M Snowflake data warehouse. Returns the result set as JSON rows.
      inputParameters:
      - name: sql_statement
        in: body
        type: string
        description: The SQL query to execute.
      - name: warehouse
        in: body
        type: string
        description: The Snowflake warehouse to use (e.g., ANALYTICS_WH).
      call: snowflake.submit-query
      with:
        statement: '{{sql_statement}}'
        warehouse: '{{warehouse}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://3m.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: submit-query
        method: POST

Captures R&D experiment results by logging data in Snowflake, updating the Jira research ticket, and archiving the experiment report in SharePoint for knowledge retention.

naftiko: '0.5'
info:
  label: R&D Experiment Log Capture
  description: Captures R&D experiment results by logging data in Snowflake, updating the Jira research ticket, and archiving the experiment report in SharePoint for knowledge retention.
  tags:
  - research
  - innovation
  - snowflake
  - jira
  - sharepoint
  - data-science
capability:
  exposes:
  - type: mcp
    namespace: rd-experiments
    port: 8080
    tools:
    - name: log-experiment
      description: Given experiment details, log results in Snowflake, update Jira, and archive report in SharePoint.
      inputParameters:
      - name: experiment_id
        in: body
        type: string
        description: Unique experiment identifier.
      - name: jira_key
        in: body
        type: string
        description: The Jira R&D issue key.
      - name: result_summary
        in: body
        type: string
        description: Summary of experiment results.
      - name: technology_area
        in: body
        type: string
        description: Technology area (e.g., adhesives, abrasives, films).
      steps:
      - name: log-to-snowflake
        type: call
        call: snowflake.run-query
        with:
          statement: INSERT INTO RD.EXPERIMENT_LOG VALUES ('{{experiment_id}}', '{{jira_key}}', '{{result_summary}}', '{{technology_area}}', CURRENT_TIMESTAMP())
          warehouse: RD_WH
      - name: update-jira
        type: call
        call: jira.add-comment
        with:
          issue_key: '{{jira_key}}'
          body: 'Experiment {{experiment_id}} completed. Results: {{result_summary}}'
      - name: archive-report
        type: call
        call: sharepoint.upload-file
        with:
          site_id: $secrets.rd_site_id
          folder_path: /Experiments/{{technology_area}}
          file_name: '{{experiment_id}}-report.json'
          content: '{{result_summary}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://3m.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: run-query
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: comments
      path: /issue/{{issue_key}}/comment
      inputParameters:
      - name: issue_key
        in: path
      operations:
      - name: add-comment
        method: POST
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /{{site_id}}/drive/root:{{folder_path}}/{{file_name}}:/content
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      - name: file_name
        in: path
      operations:
      - name: upload-file
        method: PUT

Monitors Informatica IICS job completions and logs failures to Datadog, opens a Jira data incident, and notifies the ETL team in Microsoft Teams.

naftiko: '0.5'
info:
  label: Informatica Data Integration Failure
  description: Monitors Informatica IICS job completions and logs failures to Datadog, opens a Jira data incident, and notifies the ETL team in Microsoft Teams.
  tags:
  - data-integration
  - informatica
  - datadog
  - jira
  - microsoft-teams
  - etl
capability:
  exposes:
  - type: mcp
    namespace: etl-ops
    port: 8080
    tools:
    - name: handle-informatica-failure
      description: Given an Informatica job name, source, and target, log the failure to Datadog, open a Jira incident, and notify the ETL team in Teams.
      inputParameters:
      - name: job_name
        in: body
        type: string
        description: The Informatica mapping or workflow job name.
      - name: source_system
        in: body
        type: string
        description: Source system (e.g., SAP, Oracle, Salesforce).
      - name: target_system
        in: body
        type: string
        description: Target system (e.g., Snowflake, Oracle DW).
      - name: error_message
        in: body
        type: string
        description: Error message from the failed job.
      steps:
      - name: log-datadog
        type: call
        call: datadog-etl.create-event
        with:
          title: 'Informatica Failure: {{job_name}}'
          text: 'Source: {{source_system}} → Target: {{target_system}} | Error: {{error_message}}'
          alert_type: error
          tags: etl:informatica,source:{{source_system}},target:{{target_system}}
      - name: open-jira
        type: call
        call: jira-etl.create-issue
        with:
          project_key: DATA
          issuetype: Incident
          summary: 'Informatica failure: {{job_name}} ({{source_system}} → {{target_system}})'
          description: 'Job: {{job_name}}

            Source: {{source_system}}

            Target: {{target_system}}

            Error: {{error_message}}

            Datadog: {{log-datadog.url}}'
      - name: notify-team
        type: call
        call: msteams-etl.send-message
        with:
          recipient_upn: etl-team@3m.com
          text: 'Informatica Failure: {{job_name}} | {{source_system}} → {{target_system}} | Jira: {{open-jira.key}}'
  consumes:
  - type: http
    namespace: datadog-etl
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: jira-etl
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams-etl
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

When a Jira change ticket is approved, creates a ServiceNow change request, updates the linked Confluence runbook, and notifies the change advisory board in Microsoft Teams.

naftiko: '0.5'
info:
  label: IT Change Management Workflow
  description: When a Jira change ticket is approved, creates a ServiceNow change request, updates the linked Confluence runbook, and notifies the change advisory board in Microsoft Teams.
  tags:
  - itsm
  - change-management
  - servicenow
  - jira
  - confluence
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: it-change
    port: 8080
    tools:
    - name: submit-change-request
      description: Given an approved Jira change ticket, open a ServiceNow change request, link the Confluence runbook, and notify the CAB channel in Teams.
      inputParameters:
      - name: jira_issue_key
        in: body
        type: string
        description: The approved Jira change ticket key (e.g., CHG-1234).
      - name: confluence_page_id
        in: body
        type: string
        description: The Confluence runbook page ID to attach.
      - name: scheduled_start
        in: body
        type: string
        description: Planned change start time in ISO 8601 format.
      steps:
      - name: get-jira-issue
        type: call
        call: jira.get-issue
        with:
          issue_key: '{{jira_issue_key}}'
      - name: get-runbook
        type: call
        call: confluence.get-page
        with:
          page_id: '{{confluence_page_id}}'
      - name: create-change
        type: call
        call: servicenow.create-change-request
        with:
          short_description: '{{get-jira-issue.summary}}'
          description: '{{get-jira-issue.description}}

            Runbook: {{get-runbook.url}}'
          start_date: '{{scheduled_start}}'
          category: infrastructure
      - name: notify-cab
        type: call
        call: msteams.send-message
        with:
          recipient_upn: cab-board@3m.com
          text: 'Change Submitted: {{get-jira-issue.summary}} | Jira: {{jira_issue_key}} | ServiceNow: {{create-change.number}} | Start: {{scheduled_start}} | Runbook: {{get-runbook.url}}'
  consumes:
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue/{{issue_key}}
      inputParameters:
      - name: issue_key
        in: path
      operations:
      - name: get-issue
        method: GET
  - type: http
    namespace: confluence
    baseUri: https://3m.atlassian.net/wiki/rest/api
    authentication:
      type: basic
      username: $secrets.confluence_user
      password: $secrets.confluence_token
    resources:
    - name: pages
      path: /content/{{page_id}}
      inputParameters:
      - name: page_id
        in: path
      operations:
      - name: get-page
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: change-requests
      path: /table/change_request
      operations:
      - name: create-change-request
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves a document from SharePoint, sends it to Claude via the Anthropic API for summarization, saves the result back to SharePoint, and notifies the requester in Microsoft Teams.

naftiko: '0.5'
info:
  label: AI-Assisted Document Summarization
  description: Retrieves a document from SharePoint, sends it to Claude via the Anthropic API for summarization, saves the result back to SharePoint, and notifies the requester in Microsoft Teams.
  tags:
  - ai
  - anthropic
  - document-management
  - sharepoint
  - microsoft-teams
  - productivity
capability:
  exposes:
  - type: mcp
    namespace: ai-productivity
    port: 8080
    tools:
    - name: summarize-document
      description: Given a SharePoint document path and requester UPN, fetch the document, summarize via Claude, save the summary, and notify the requester in Teams.
      inputParameters:
      - name: sharepoint_site_id
        in: body
        type: string
        description: SharePoint site ID containing the document.
      - name: document_path
        in: body
        type: string
        description: Path to the document within the SharePoint drive.
      - name: requester_upn
        in: body
        type: string
        description: Microsoft UPN of the person requesting the summary.
      steps:
      - name: get-document
        type: call
        call: sharepoint-ai.get-file
        with:
          site_id: '{{sharepoint_site_id}}'
          file_path: '{{document_path}}'
      - name: summarize
        type: call
        call: anthropic-ai.create-message
        with:
          model: claude-sonnet-4-6
          max_tokens: '1024'
          system: You are a concise business document summarizer for 3M executives.
          user_message: 'Summarize this document:


            {{get-document.content}}'
      - name: save-summary
        type: call
        call: sharepoint-ai.create-file
        with:
          site_id: '{{sharepoint_site_id}}'
          file_path: Summaries/{{document_path}}.summary.md
          content: '{{summarize.content}}'
      - name: notify-requester
        type: call
        call: msteams-ai.send-message
        with:
          recipient_upn: '{{requester_upn}}'
          text: 'Your document summary is ready: {{save-summary.url}}'
  consumes:
  - type: http
    namespace: sharepoint-ai
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /{{site_id}}/drive/root:/{{file_path}}:/content
      inputParameters:
      - name: site_id
        in: path
      - name: file_path
        in: path
      operations:
      - name: get-file
        method: GET
      - name: create-file
        method: PUT
  - type: http
    namespace: anthropic-ai
    baseUri: https://api.anthropic.com/v1
    authentication:
      type: apikey
      key: x-api-key
      value: $secrets.anthropic_api_key
      placement: header
    resources:
    - name: messages
      path: /messages
      operations:
      - name: create-message
        method: POST
  - type: http
    namespace: msteams-ai
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves a ServiceNow incident record by number, returning priority, state, assigned group, and resolution notes for IT support teams.

naftiko: '0.5'
info:
  label: ServiceNow Incident Lookup
  description: Retrieves a ServiceNow incident record by number, returning priority, state, assigned group, and resolution notes for IT support teams.
  tags:
  - it-service
  - servicenow
  - incident
  - support
capability:
  exposes:
  - type: mcp
    namespace: itsm
    port: 8080
    tools:
    - name: get-incident
      description: Look up a ServiceNow incident by number. Returns priority, state, assignment group, and short description.
      inputParameters:
      - name: incident_number
        in: body
        type: string
        description: The ServiceNow incident number (e.g., INC0012345).
      call: servicenow.get-incident
      with:
        incident_number: '{{incident_number}}'
      outputParameters:
      - name: priority
        type: string
        mapping: $.result.priority
      - name: state
        type: string
        mapping: $.result.state
      - name: assigned_to
        type: string
        mapping: $.result.assigned_to.display_value
      - name: short_description
        type: string
        mapping: $.result.short_description
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      inputParameters:
      - name: incident_number
        in: query
        value: number={{incident_number}}
      operations:
      - name: get-incident
        method: GET

Onboards contractors for plant access by verifying training records in ServiceNow, creating a Workday contingent worker record, and issuing a badge request through Microsoft Power Automate.

naftiko: '0.5'
info:
  label: Contractor Safety Onboarding
  description: Onboards contractors for plant access by verifying training records in ServiceNow, creating a Workday contingent worker record, and issuing a badge request through Microsoft Power Automate.
  tags:
  - safety
  - contractor
  - servicenow
  - workday
  - microsoft-power-automate
  - onboarding
capability:
  exposes:
  - type: mcp
    namespace: contractor-safety
    port: 8080
    tools:
    - name: onboard-contractor
      description: Given contractor details, verify safety training, create worker record, and issue badge request.
      inputParameters:
      - name: contractor_name
        in: body
        type: string
        description: Full name of the contractor.
      - name: company_name
        in: body
        type: string
        description: Contractor's employer company.
      - name: plant_code
        in: body
        type: string
        description: 3M plant code for access.
      - name: start_date
        in: body
        type: string
        description: Contract start date.
      - name: training_cert_id
        in: body
        type: string
        description: Safety training certification ID.
      steps:
      - name: verify-training
        type: call
        call: servicenow.verify-training-cert
        with:
          cert_id: '{{training_cert_id}}'
          contractor_name: '{{contractor_name}}'
      - name: create-worker-record
        type: call
        call: workday.create-contingent-worker
        with:
          name: '{{contractor_name}}'
          company: '{{company_name}}'
          location: '{{plant_code}}'
          start_date: '{{start_date}}'
      - name: request-badge
        type: call
        call: power-automate.trigger-flow
        with:
          flow_id: $secrets.badge_request_flow_id
          contractor_name: '{{contractor_name}}'
          plant: '{{plant_code}}'
          worker_id: '{{create-worker-record.worker_id}}'
          training_status: '{{verify-training.status}}'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: training-certs
      path: /table/sn_ehs_training_cert
      inputParameters:
      - name: cert_id
        in: query
      - name: contractor_name
        in: query
      operations:
      - name: verify-training-cert
        method: GET
  - type: http
    namespace: workday
    baseUri: https://wd5-impl-services1.workday.com/ccx/api/v1/3m
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: contingent-workers
      path: /contingentWorkers
      operations:
      - name: create-contingent-worker
        method: POST
  - type: http
    namespace: power-automate
    baseUri: https://prod-00.westus.logic.azure.com/workflows
    authentication:
      type: bearer
      token: $secrets.power_automate_token
    resources:
    - name: flows
      path: /{{flow_id}}/triggers/manual/paths/invoke
      inputParameters:
      - name: flow_id
        in: path
      operations:
      - name: trigger-flow
        method: POST

When Palo Alto Networks fires a threat alert, correlates with Datadog network metrics, opens a ServiceNow security incident, and notifies the security operations center in Microsoft Teams.

naftiko: '0.5'
info:
  label: Network Security Event Triage
  description: When Palo Alto Networks fires a threat alert, correlates with Datadog network metrics, opens a ServiceNow security incident, and notifies the security operations center in Microsoft Teams.
  tags:
  - security
  - network
  - palo-alto-networks
  - datadog
  - servicenow
  - microsoft-teams
  - soc
capability:
  exposes:
  - type: mcp
    namespace: network-security
    port: 8080
    tools:
    - name: triage-network-threat
      description: Given a Palo Alto threat alert ID and source IP, correlate with Datadog, open a ServiceNow security incident, and alert the SOC in Teams.
      inputParameters:
      - name: threat_id
        in: body
        type: string
        description: The Palo Alto Networks threat alert ID.
      - name: source_ip
        in: body
        type: string
        description: Source IP address of the threat.
      - name: threat_severity
        in: body
        type: string
        description: Threat severity level (critical, high, medium, low).
      - name: affected_host
        in: body
        type: string
        description: Hostname or resource affected by the threat.
      steps:
      - name: log-datadog-event
        type: call
        call: datadog.create-event
        with:
          title: 'Network Threat: {{threat_id}} from {{source_ip}}'
          text: 'Severity: {{threat_severity}} | Host: {{affected_host}}'
          alert_type: error
          tags: security:network,severity:{{threat_severity}}
      - name: create-security-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Network Threat ({{threat_severity}}): {{threat_id}} — {{source_ip}}'
          description: 'Palo Alto alert {{threat_id}} | Source: {{source_ip}} | Host: {{affected_host}} | Datadog: {{log-datadog-event.url}}'
          category: security
          urgency: '1'
          impact: '1'
      - name: alert-soc
        type: call
        call: msteams.send-message
        with:
          recipient_upn: soc-team@3m.com
          text: 'Network Threat: {{threat_id}} | Severity: {{threat_severity}} | Source IP: {{source_ip}} | Host: {{affected_host}} | ServiceNow: {{create-security-incident.number}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Runs Terraform to provision AWS or Azure infrastructure, registers the new resources in Datadog for monitoring, and posts a provisioning summary to the DevOps Microsoft Teams channel.

naftiko: '0.5'
info:
  label: Infrastructure Provisioning Pipeline
  description: Runs Terraform to provision AWS or Azure infrastructure, registers the new resources in Datadog for monitoring, and posts a provisioning summary to the DevOps Microsoft Teams channel.
  tags:
  - devops
  - infrastructure
  - terraform
  - aws
  - azure
  - datadog
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: infra-provisioning
    port: 8080
    tools:
    - name: provision-infrastructure
      description: Trigger a Terraform infrastructure provisioning run for AWS or Azure, register resulting resources in Datadog, and notify the DevOps team in Teams.
      inputParameters:
      - name: workspace_name
        in: body
        type: string
        description: The Terraform Cloud workspace name to trigger.
      - name: cloud_provider
        in: body
        type: string
        description: 'Target cloud provider: aws or azure.'
      - name: environment
        in: body
        type: string
        description: 'Target environment: dev, staging, or prod.'
      steps:
      - name: trigger-terraform
        type: call
        call: terraform.create-run
        with:
          workspace: '{{workspace_name}}'
          message: Provisioning {{environment}} on {{cloud_provider}}
      - name: register-monitor
        type: call
        call: datadog.create-monitor
        with:
          name: '{{workspace_name}} — {{environment}} health'
          type: service check
          message: Infrastructure {{workspace_name}} on {{cloud_provider}} in {{environment}} is unhealthy.
      - name: notify-devops
        type: call
        call: msteams.send-message
        with:
          recipient_upn: devops-team@3m.com
          text: 'Infrastructure Provisioned: {{workspace_name}} | Cloud: {{cloud_provider}} | Env: {{environment}} | Terraform Run: {{trigger-terraform.run_id}} | Datadog Monitor: {{register-monitor.id}}'
  consumes:
  - type: http
    namespace: terraform
    baseUri: https://app.terraform.io/api/v2
    authentication:
      type: bearer
      token: $secrets.terraform_token
    resources:
    - name: runs
      path: /runs
      operations:
      - name: create-run
        method: POST
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: monitors
      path: /monitor
      operations:
      - name: create-monitor
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Aggregates campaign performance data from Adobe Analytics and HubSpot, updates Salesforce campaign records with current metrics, and posts a digest to the marketing Microsoft Teams channel.

naftiko: '0.5'
info:
  label: Marketing Campaign Performance Digest
  description: Aggregates campaign performance data from Adobe Analytics and HubSpot, updates Salesforce campaign records with current metrics, and posts a digest to the marketing Microsoft Teams channel.
  tags:
  - marketing
  - analytics
  - adobe-analytics
  - hubspot
  - salesforce
  - microsoft-teams
  - campaign-management
capability:
  exposes:
  - type: mcp
    namespace: marketing
    port: 8080
    tools:
    - name: digest-campaign-performance
      description: Given a campaign ID, fetch Adobe Analytics web metrics and HubSpot email metrics, update the Salesforce campaign record, and post a summary to Teams.
      inputParameters:
      - name: campaign_id
        in: body
        type: string
        description: The campaign identifier (shared across Adobe Analytics, HubSpot, and Salesforce).
      - name: date_range
        in: body
        type: string
        description: Date range for the report in YYYY-MM-DD/YYYY-MM-DD format.
      - name: salesforce_campaign_id
        in: body
        type: string
        description: The Salesforce campaign record ID.
      steps:
      - name: get-web-metrics
        type: call
        call: adobe-analytics.get-campaign-metrics
        with:
          campaign_id: '{{campaign_id}}'
          date_range: '{{date_range}}'
      - name: get-email-metrics
        type: call
        call: hubspot.get-campaign-stats
        with:
          campaign_id: '{{campaign_id}}'
      - name: update-salesforce-campaign
        type: call
        call: salesforce.update-campaign
        with:
          campaign_id: '{{salesforce_campaign_id}}'
          impressions: '{{get-web-metrics.impressions}}'
          clicks: '{{get-web-metrics.clicks}}'
          email_opens: '{{get-email-metrics.opens}}'
          email_clicks: '{{get-email-metrics.clicks}}'
      - name: post-digest
        type: call
        call: msteams.send-message
        with:
          recipient_upn: marketing-team@3m.com
          text: 'Campaign {{campaign_id}} digest ({{date_range}}): Impressions: {{get-web-metrics.impressions}} | Web Clicks: {{get-web-metrics.clicks}} | Email Opens: {{get-email-metrics.opens}} | Email Clicks: {{get-email-metrics.clicks}} | Salesforce updated.'
  consumes:
  - type: http
    namespace: adobe-analytics
    baseUri: https://analytics.adobe.io/api/{{company_id}}/reports
    authentication:
      type: bearer
      token: $secrets.adobe_analytics_token
    resources:
    - name: campaign-reports
      path: /campaigns/{{campaign_id}}
      inputParameters:
      - name: campaign_id
        in: path
      - name: date_range
        in: query
      operations:
      - name: get-campaign-metrics
        method: GET
  - type: http
    namespace: hubspot
    baseUri: https://api.hubapi.com/marketing/v3
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: campaigns
      path: /campaigns/{{campaign_id}}/stats
      inputParameters:
      - name: campaign_id
        in: path
      operations:
      - name: get-campaign-stats
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: campaigns
      path: /sobjects/Campaign/{{campaign_id}}
      inputParameters:
      - name: campaign_id
        in: path
      operations:
      - name: update-campaign
        method: PATCH
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Creates an inter-plant stock transfer in SAP, logs the shipment in Oracle TMS, and notifies the receiving plant warehouse team in Microsoft Teams.

naftiko: '0.5'
info:
  label: Warehouse Transfer Order Creation
  description: Creates an inter-plant stock transfer in SAP, logs the shipment in Oracle TMS, and notifies the receiving plant warehouse team in Microsoft Teams.
  tags:
  - supply-chain
  - logistics
  - sap
  - oracle
  - microsoft-teams
  - warehouse
capability:
  exposes:
  - type: mcp
    namespace: warehouse-ops
    port: 8080
    tools:
    - name: create-transfer-order
      description: Given source and destination plants, material, and quantity, create a SAP stock transfer, log the shipment, and notify receiving warehouse.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number to transfer.
      - name: source_plant
        in: body
        type: string
        description: The originating 3M plant code.
      - name: destination_plant
        in: body
        type: string
        description: The receiving 3M plant code.
      - name: quantity
        in: body
        type: string
        description: Quantity to transfer.
      steps:
      - name: create-sto
        type: call
        call: sap.create-stock-transfer
        with:
          material: '{{material_number}}'
          supplying_plant: '{{source_plant}}'
          receiving_plant: '{{destination_plant}}'
          quantity: '{{quantity}}'
      - name: log-shipment
        type: call
        call: oracle-tms.create-shipment
        with:
          origin: '{{source_plant}}'
          destination: '{{destination_plant}}'
          reference: '{{create-sto.transfer_order_number}}'
          weight: '{{quantity}}'
      - name: notify-receiving
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.warehouse_team_id
          channel_id: $secrets.warehouse_channel_id
          text: 'Inbound Transfer: {{material_number}} x{{quantity}} from {{source_plant}} | SAP STO: {{create-sto.transfer_order_number}} | Shipment: {{log-shipment.shipment_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/MM_STOCK_TRANSFER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: stock-transfers
      path: /StockTransferOrder
      operations:
      - name: create-stock-transfer
        method: POST
  - type: http
    namespace: oracle-tms
    baseUri: https://3m-ebs.oracle.com/fscmRestApi/resources/v1
    authentication:
      type: basic
      username: $secrets.oracle_ebs_user
      password: $secrets.oracle_ebs_password
    resources:
    - name: shipments
      path: /shipments
      operations:
      - name: create-shipment
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Deploys a trained ML model by registering it in Azure Machine Learning, creating a Jira deployment ticket, updating the model registry in Snowflake, and notifying the data science team in Teams.

naftiko: '0.5'
info:
  label: Machine Learning Model Deployment
  description: Deploys a trained ML model by registering it in Azure Machine Learning, creating a Jira deployment ticket, updating the model registry in Snowflake, and notifying the data science team in Teams.
  tags:
  - data-science
  - machine-learning
  - azure-machine-learning
  - jira
  - snowflake
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: ml-ops
    port: 8080
    tools:
    - name: deploy-model
      description: Given a model name, version, and endpoint, register in Azure ML, create Jira ticket, update registry, and notify data science.
      inputParameters:
      - name: model_name
        in: body
        type: string
        description: Name of the ML model.
      - name: model_version
        in: body
        type: string
        description: Model version to deploy.
      - name: endpoint_name
        in: body
        type: string
        description: Azure ML endpoint name.
      - name: use_case
        in: body
        type: string
        description: Business use case (e.g., demand_forecast, defect_detection, predictive_maintenance).
      steps:
      - name: register-model
        type: call
        call: azureml.register-model
        with:
          model_name: '{{model_name}}'
          model_version: '{{model_version}}'
          endpoint: '{{endpoint_name}}'
      - name: create-deployment-ticket
        type: call
        call: jira.create-issue
        with:
          project_key: MLOPS
          issuetype: Task
          summary: 'Model Deployment: {{model_name}} v{{model_version}} to {{endpoint_name}}'
          description: 'Use case: {{use_case}} | Azure ML endpoint: {{endpoint_name}} | Registration: {{register-model.model_id}}'
      - name: update-registry
        type: call
        call: snowflake.run-query
        with:
          statement: INSERT INTO MLOPS.MODEL_REGISTRY VALUES ('{{model_name}}', '{{model_version}}', '{{endpoint_name}}', '{{use_case}}', CURRENT_TIMESTAMP())
          warehouse: MLOPS_WH
      - name: notify-data-science
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.datascience_team_id
          channel_id: $secrets.datascience_channel_id
          text: 'Model Deployed: {{model_name}} v{{model_version}} to {{endpoint_name}} | Use case: {{use_case}} | Jira: {{create-deployment-ticket.key}}'
  consumes:
  - type: http
    namespace: azureml
    baseUri: https://3m-ml.api.azureml.ms
    authentication:
      type: bearer
      token: $secrets.azureml_token
    resources:
    - name: models
      path: /models/{{model_name}}/versions/{{model_version}}/deploy
      inputParameters:
      - name: model_name
        in: path
      - name: model_version
        in: path
      operations:
      - name: register-model
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://3m.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: run-query
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Pulls a supplier profile from SAP Ariba, enriches it with ZoomInfo firmographic data, scores risk, and creates a ServiceNow vendor risk review task for the procurement team.

naftiko: '0.5'
info:
  label: Supplier Risk Assessment
  description: Pulls a supplier profile from SAP Ariba, enriches it with ZoomInfo firmographic data, scores risk, and creates a ServiceNow vendor risk review task for the procurement team.
  tags:
  - procurement
  - vendor-risk
  - sap-ariba
  - zoominfo
  - servicenow
  - supply-chain
capability:
  exposes:
  - type: mcp
    namespace: vendor-risk
    port: 8080
    tools:
    - name: assess-supplier-risk
      description: Given an Ariba supplier ID and company name, enrich with ZoomInfo data, compute a risk tier, and open a ServiceNow vendor risk task.
      inputParameters:
      - name: ariba_supplier_id
        in: body
        type: string
        description: The SAP Ariba supplier ID.
      - name: company_name
        in: body
        type: string
        description: Legal company name for ZoomInfo enrichment.
      steps:
      - name: get-supplier
        type: call
        call: ariba.get-supplier
        with:
          supplier_id: '{{ariba_supplier_id}}'
      - name: enrich-firmographics
        type: call
        call: zoominfo.get-company
        with:
          company_name: '{{company_name}}'
      - name: create-risk-task
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Vendor risk review: {{company_name}}'
          description: 'Supplier: {{ariba_supplier_id}} | Revenue: {{enrich-firmographics.revenue}} | Employees: {{enrich-firmographics.employee_count}} | Country: {{get-supplier.country}} | Status: {{get-supplier.qualification_status}}'
          category: vendor_risk
          assigned_group: Procurement_Risk
  consumes:
  - type: http
    namespace: ariba
    baseUri: https://openapi.ariba.com/api/supplier-management/v1
    authentication:
      type: bearer
      token: $secrets.ariba_token
    resources:
    - name: suppliers
      path: /suppliers/{{supplier_id}}
      inputParameters:
      - name: supplier_id
        in: path
      operations:
      - name: get-supplier
        method: GET
  - type: http
    namespace: zoominfo
    baseUri: https://api.zoominfo.com/search
    authentication:
      type: bearer
      token: $secrets.zoominfo_token
    resources:
    - name: companies
      path: /company
      inputParameters:
      - name: company_name
        in: query
      operations:
      - name: get-company
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/task
      operations:
      - name: create-task
        method: POST

Collects energy consumption data from SAP Plant Maintenance, calculates KPIs in Snowflake, and publishes a summary report to a Power BI dataset and the sustainability Teams channel.

naftiko: '0.5'
info:
  label: Plant Energy Consumption Report
  description: Collects energy consumption data from SAP Plant Maintenance, calculates KPIs in Snowflake, and publishes a summary report to a Power BI dataset and the sustainability Teams channel.
  tags:
  - sustainability
  - energy
  - sap
  - snowflake
  - power-bi
  - microsoft-teams
  - manufacturing
capability:
  exposes:
  - type: mcp
    namespace: sustainability
    port: 8080
    tools:
    - name: generate-energy-report
      description: Given a plant code and reporting period, collect energy data, compute KPIs, refresh Power BI, and notify sustainability team.
      inputParameters:
      - name: plant_code
        in: body
        type: string
        description: The 3M plant code.
      - name: period
        in: body
        type: string
        description: Reporting period (e.g., 2026-Q1).
      steps:
      - name: get-energy-data
        type: call
        call: sap.get-energy-readings
        with:
          plant: '{{plant_code}}'
          period: '{{period}}'
      - name: compute-kpis
        type: call
        call: snowflake.run-query
        with:
          statement: CALL SUSTAINABILITY.COMPUTE_ENERGY_KPIS('{{plant_code}}', '{{period}}')
          warehouse: SUSTAINABILITY_WH
      - name: refresh-powerbi
        type: call
        call: powerbi.trigger-refresh
        with:
          group_id: $secrets.sustainability_pbi_group
          dataset_id: $secrets.energy_dataset_id
      - name: notify-sustainability
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.sustainability_team_id
          channel_id: $secrets.sustainability_channel_id
          text: Energy report for {{plant_code}} ({{period}}) published. Power BI dashboard refreshed.
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/PM_MEASUREMENT_DOC_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: energy-readings
      path: /MeasurementDocument
      inputParameters:
      - name: plant
        in: query
      - name: period
        in: query
      operations:
      - name: get-energy-readings
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://3m.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: run-query
        method: POST
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: dataset-refresh
      path: /groups/{{group_id}}/datasets/{{dataset_id}}/refreshes
      inputParameters:
      - name: group_id
        in: path
      - name: dataset_id
        in: path
      operations:
      - name: trigger-refresh
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Updates controlled documents for ISO compliance by versioning in SharePoint, creating a Jira review task, and notifying the document control team in Microsoft Teams.

naftiko: '0.5'
info:
  label: ISO Document Control Update
  description: Updates controlled documents for ISO compliance by versioning in SharePoint, creating a Jira review task, and notifying the document control team in Microsoft Teams.
  tags:
  - compliance
  - iso
  - sharepoint
  - jira
  - microsoft-teams
  - quality
  - document-control
capability:
  exposes:
  - type: mcp
    namespace: document-control
    port: 8080
    tools:
    - name: update-controlled-document
      description: Given a document ID, new version, and change summary, version in SharePoint, create review task, and notify.
      inputParameters:
      - name: document_id
        in: body
        type: string
        description: SharePoint document ID.
      - name: document_title
        in: body
        type: string
        description: Title of the controlled document.
      - name: new_version
        in: body
        type: string
        description: New document version number.
      - name: change_summary
        in: body
        type: string
        description: Summary of changes in this version.
      steps:
      - name: upload-new-version
        type: call
        call: sharepoint.upload-file
        with:
          site_id: $secrets.qms_site_id
          folder_path: /ControlledDocs
          file_name: '{{document_id}}-v{{new_version}}.pdf'
          content: '{{change_summary}}'
      - name: create-review-task
        type: call
        call: jira.create-issue
        with:
          project_key: QMS
          issuetype: Task
          summary: 'Doc Review: {{document_title}} v{{new_version}}'
          description: 'Document: {{document_id}} | Version: {{new_version}} | Changes: {{change_summary}}'
      - name: notify-doc-control
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.quality_team_id
          channel_id: $secrets.doc_control_channel_id
          text: 'Document Updated: {{document_title}} v{{new_version}} | Changes: {{change_summary}} | Review: {{create-review-task.key}}'
  consumes:
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /{{site_id}}/drive/root:{{folder_path}}/{{file_name}}:/content
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      - name: file_name
        in: path
      operations:
      - name: upload-file
        method: PUT
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Generates shipping labels by retrieving order details from SAP, creating a shipment in Oracle TMS, and posting the tracking information to the Salesforce opportunity record.

naftiko: '0.5'
info:
  label: Shipping Label Generation
  description: Generates shipping labels by retrieving order details from SAP, creating a shipment in Oracle TMS, and posting the tracking information to the Salesforce opportunity record.
  tags:
  - logistics
  - shipping
  - sap
  - oracle
  - salesforce
  - supply-chain
capability:
  exposes:
  - type: mcp
    namespace: shipping
    port: 8080
    tools:
    - name: generate-shipping-label
      description: Given an order number, create shipment, generate label, and update Salesforce with tracking.
      inputParameters:
      - name: order_number
        in: body
        type: string
        description: The SAP sales order number.
      - name: salesforce_opportunity_id
        in: body
        type: string
        description: Linked Salesforce opportunity ID.
      steps:
      - name: get-order-details
        type: call
        call: sap.get-delivery
        with:
          order_number: '{{order_number}}'
      - name: create-shipment
        type: call
        call: oracle-tms.create-shipment
        with:
          origin: '{{get-order-details.shipping_plant}}'
          destination: '{{get-order-details.ship_to_address}}'
          weight: '{{get-order-details.total_weight}}'
          reference: '{{order_number}}'
      - name: update-salesforce
        type: call
        call: salesforce.update-opportunity
        with:
          opportunity_id: '{{salesforce_opportunity_id}}'
          tracking_number: '{{create-shipment.tracking_number}}'
          ship_date: '{{create-shipment.ship_date}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/SD_DELIVERY_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: deliveries
      path: /A_OutboundDelivery('{{order_number}}')
      inputParameters:
      - name: order_number
        in: path
      operations:
      - name: get-delivery
        method: GET
  - type: http
    namespace: oracle-tms
    baseUri: https://3m-ebs.oracle.com/fscmRestApi/resources/v1
    authentication:
      type: basic
      username: $secrets.oracle_ebs_user
      password: $secrets.oracle_ebs_password
    resources:
    - name: shipments
      path: /shipments
      operations:
      - name: create-shipment
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: opportunities
      path: /sobjects/Opportunity/{{opportunity_id}}
      inputParameters:
      - name: opportunity_id
        in: path
      operations:
      - name: update-opportunity
        method: PATCH

When Workday creates a new job requisition, schedules interviews via Microsoft Teams, creates a shared Confluence evaluation page, and notifies the hiring panel.

naftiko: '0.5'
info:
  label: Candidate Interview Pipeline
  description: When Workday creates a new job requisition, schedules interviews via Microsoft Teams, creates a shared Confluence evaluation page, and notifies the hiring panel.
  tags:
  - hr
  - recruiting
  - workday
  - microsoft-teams
  - confluence
  - hiring
capability:
  exposes:
  - type: mcp
    namespace: talent-acquisition
    port: 8080
    tools:
    - name: schedule-interview-panel
      description: Given a Workday requisition ID and candidate name, create Teams meeting invites for the panel and a Confluence evaluation scorecard page.
      inputParameters:
      - name: requisition_id
        in: body
        type: string
        description: The Workday job requisition ID.
      - name: candidate_name
        in: body
        type: string
        description: Full name of the candidate.
      - name: interview_date
        in: body
        type: string
        description: Interview date in YYYY-MM-DD format.
      - name: panel_upns
        in: body
        type: string
        description: Comma-separated list of interviewer Microsoft UPNs.
      steps:
      - name: get-requisition
        type: call
        call: workday.get-job-requisition
        with:
          requisition_id: '{{requisition_id}}'
      - name: create-teams-meeting
        type: call
        call: msteams.create-meeting
        with:
          subject: 'Interview: {{candidate_name}} — {{get-requisition.job_title}}'
          start_datetime: '{{interview_date}}T09:00:00'
          attendees: '{{panel_upns}}'
      - name: create-scorecard
        type: call
        call: confluence.create-page
        with:
          space_key: HR
          title: 'Interview Scorecard: {{candidate_name}} — {{get-requisition.job_title}}'
          body: 'Requisition: {{requisition_id}} | Role: {{get-requisition.job_title}} | Date: {{interview_date}} | Meeting: {{create-teams-meeting.join_url}}'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: job-requisitions
      path: /jobRequisitions/{{requisition_id}}
      inputParameters:
      - name: requisition_id
        in: path
      operations:
      - name: get-job-requisition
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: meetings
      path: /me/onlineMeetings
      operations:
      - name: create-meeting
        method: POST
  - type: http
    namespace: confluence
    baseUri: https://3m.atlassian.net/wiki/rest/api
    authentication:
      type: basic
      username: $secrets.confluence_user
      password: $secrets.confluence_token
    resources:
    - name: pages
      path: /content
      operations:
      - name: create-page
        method: POST

On a protected-branch GitHub Actions pipeline failure, creates a New Relic deployment marker, opens a Jira bug, and alerts the engineering team in Microsoft Teams with full log context.

naftiko: '0.5'
info:
  label: CI/CD Pipeline Failure Triage
  description: On a protected-branch GitHub Actions pipeline failure, creates a New Relic deployment marker, opens a Jira bug, and alerts the engineering team in Microsoft Teams with full log context.
  tags:
  - devops
  - ci-cd
  - github
  - github-actions
  - jira
  - new-relic
  - microsoft-teams
  - engineering
capability:
  exposes:
  - type: mcp
    namespace: devops
    port: 8080
    tools:
    - name: handle-pipeline-failure
      description: Given a GitHub Actions pipeline failure event, create a New Relic deployment marker, open a Jira bug, and alert the engineering channel in Microsoft Teams.
      inputParameters:
      - name: pipeline_id
        in: body
        type: string
        description: The GitHub Actions workflow run ID.
      - name: repository
        in: body
        type: string
        description: The GitHub repository in owner/repo format.
      - name: branch
        in: body
        type: string
        description: The branch where the pipeline failed.
      - name: failed_job_name
        in: body
        type: string
        description: Name of the failing job in the pipeline.
      - name: commit_sha
        in: body
        type: string
        description: The commit SHA that triggered the pipeline.
      - name: log_url
        in: body
        type: string
        description: URL to the failed pipeline run logs.
      steps:
      - name: create-marker
        type: call
        call: newrelic.create-deployment-marker
        with:
          entity_name: '{{repository}}'
          version: '{{commit_sha}}'
          description: 'Pipeline failure on {{branch}} — job: {{failed_job_name}}'
      - name: create-bug
        type: call
        call: jira.create-issue
        with:
          project_key: ENG
          issuetype: Bug
          summary: '[CI Failure] {{repository}} / {{branch}} — {{failed_job_name}}'
          description: 'Pipeline: {{pipeline_id}}

            Repo: {{repository}}

            Branch: {{branch}}

            Commit: {{commit_sha}}

            Log: {{log_url}}

            New Relic marker: {{create-marker.id}}'
      - name: alert-engineering
        type: call
        call: msteams.send-message
        with:
          recipient_upn: engineering-alerts@3m.com
          text: 'Pipeline Failure: {{repository}} | Branch: {{branch}} | Job: {{failed_job_name}} | Jira: {{create-bug.key}} | Log: {{log_url}}'
  consumes:
  - type: http
    namespace: newrelic
    baseUri: https://api.newrelic.com/v2
    authentication:
      type: apikey
      key: X-Api-Key
      value: $secrets.newrelic_api_key
      placement: header
    resources:
    - name: deployments
      path: /applications/{{entity_name}}/deployments.json
      inputParameters:
      - name: entity_name
        in: path
      operations:
      - name: create-deployment-marker
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Initiates a product specification change by creating a SAP engineering change order, opening a Jira review task, and notifying the product engineering team in Microsoft Teams.

naftiko: '0.5'
info:
  label: Product Specification Change Request
  description: Initiates a product specification change by creating a SAP engineering change order, opening a Jira review task, and notifying the product engineering team in Microsoft Teams.
  tags:
  - engineering
  - product-development
  - sap
  - jira
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: product-engineering
    port: 8080
    tools:
    - name: request-spec-change
      description: Given a material, change description, and justification, create SAP ECO, Jira task, and notify engineering.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number being changed.
      - name: change_description
        in: body
        type: string
        description: Description of the specification change.
      - name: justification
        in: body
        type: string
        description: Business justification for the change.
      - name: priority
        in: body
        type: string
        description: 'Change priority: low, medium, high, critical.'
      steps:
      - name: create-eco
        type: call
        call: sap.create-change-order
        with:
          material: '{{material_number}}'
          description: '{{change_description}}'
          reason: '{{justification}}'
          priority: '{{priority}}'
      - name: create-review-task
        type: call
        call: jira.create-issue
        with:
          project_key: ENG
          issuetype: Task
          summary: 'Spec Change Review: {{material_number}} — {{change_description}}'
          description: 'SAP ECO: {{create-eco.change_number}} | Justification: {{justification}} | Priority: {{priority}}'
          priority: '{{priority}}'
      - name: notify-engineering
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.engineering_team_id
          channel_id: $secrets.engineering_channel_id
          text: 'Spec Change Request: {{material_number}} | {{change_description}} | Priority: {{priority}} | SAP ECO: {{create-eco.change_number}} | Jira: {{create-review-task.key}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/PLM_CHANGE_ORDER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: change-orders
      path: /EngineeringChangeOrder
      operations:
      - name: create-change-order
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Looks up a supply chain order across SAP S/4HANA and Oracle E-Business Suite, reconciles inventory and delivery status, and surfaces consolidated status to Salesforce customer-facing records.

naftiko: '0.5'
info:
  label: Supply Chain Order Status
  description: Looks up a supply chain order across SAP S/4HANA and Oracle E-Business Suite, reconciles inventory and delivery status, and surfaces consolidated status to Salesforce customer-facing records.
  tags:
  - supply-chain
  - erp
  - sap
  - oracle
  - salesforce
  - order-management
  - logistics
capability:
  exposes:
  - type: mcp
    namespace: supply-chain
    port: 8080
    tools:
    - name: get-order-status
      description: Look up a customer order across SAP and Oracle EBS, return consolidated fulfillment status, inventory availability, and estimated delivery date.
      inputParameters:
      - name: order_number
        in: body
        type: string
        description: The customer order number, present in both SAP and Oracle EBS.
      - name: salesforce_opportunity_id
        in: body
        type: string
        description: The Salesforce opportunity ID linked to this order.
      steps:
      - name: get-sap-order
        type: call
        call: sap.get-sales-order
        with:
          order_number: '{{order_number}}'
      - name: get-oracle-inventory
        type: call
        call: oracle-ebs.get-inventory-status
        with:
          item_number: '{{get-sap-order.material_number}}'
          warehouse: '{{get-sap-order.shipping_plant}}'
      - name: update-salesforce-opportunity
        type: call
        call: salesforce.update-opportunity
        with:
          opportunity_id: '{{salesforce_opportunity_id}}'
          delivery_date: '{{get-sap-order.requested_delivery_date}}'
          fulfillment_status: '{{get-sap-order.overall_status}}'
          available_stock: '{{get-oracle-inventory.available_qty}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/SD_SALES_ORDER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: sales-orders
      path: /A_SalesOrder('{{order_number}}')
      inputParameters:
      - name: order_number
        in: path
      operations:
      - name: get-sales-order
        method: GET
        outputRawFormat: json
  - type: http
    namespace: oracle-ebs
    baseUri: https://3m-ebs.oracle.com/fscmRestApi/resources/v1
    authentication:
      type: basic
      username: $secrets.oracle_ebs_user
      password: $secrets.oracle_ebs_password
    resources:
    - name: inventory
      path: /inventoryOnhandQuantities
      inputParameters:
      - name: item_number
        in: query
      - name: warehouse
        in: query
      operations:
      - name: get-inventory-status
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: opportunities
      path: /sobjects/Opportunity/{{opportunity_id}}
      inputParameters:
      - name: opportunity_id
        in: path
      operations:
      - name: update-opportunity
        method: PATCH

When an Azure DevOps release pipeline reaches a manual gate, queries Datadog SLO status, checks ServiceNow for open P1 incidents, and posts a go/no-go recommendation to the release management Teams channel.

naftiko: '0.5'
info:
  label: Azure DevOps Release Gate
  description: When an Azure DevOps release pipeline reaches a manual gate, queries Datadog SLO status, checks ServiceNow for open P1 incidents, and posts a go/no-go recommendation to the release management Teams channel.
  tags:
  - devops
  - azure-devops
  - datadog
  - servicenow
  - release-management
  - ci-cd
capability:
  exposes:
  - type: mcp
    namespace: release-gate
    port: 8080
    tools:
    - name: evaluate-release-gate
      description: Given a release ID and target environment, check Datadog SLO health and open P1 ServiceNow incidents to produce a go/no-go recommendation.
      inputParameters:
      - name: release_id
        in: body
        type: string
        description: The Azure DevOps release ID.
      - name: target_environment
        in: body
        type: string
        description: Target deployment environment (staging, prod).
      - name: service_name
        in: body
        type: string
        description: Datadog service name to check SLO for.
      steps:
      - name: check-slo
        type: call
        call: datadog.get-slo-status
        with:
          service: '{{service_name}}'
      - name: check-open-incidents
        type: call
        call: servicenow.get-incidents
        with:
          urgency: '1'
          state: '1'
      - name: notify-release-team
        type: call
        call: msteams-release.send-message
        with:
          recipient_upn: release-mgmt@3m.com
          text: 'Release Gate: {{release_id}} → {{target_environment}} | SLO: {{check-slo.status}} | Open P1s: {{check-open-incidents.count}} | Recommendation: review before proceeding.'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: slo-status
      path: /slo
      inputParameters:
      - name: service
        in: query
      operations:
      - name: get-slo-status
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      inputParameters:
      - name: urgency
        in: query
      - name: state
        in: query
      operations:
      - name: get-incidents
        method: GET
  - type: http
    namespace: msteams-release
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Processes intercompany invoices by matching SAP FI documents between company codes, logging discrepancies in Jira, and notifying the shared services team in Teams.

naftiko: '0.5'
info:
  label: Intercompany Invoice Processing
  description: Processes intercompany invoices by matching SAP FI documents between company codes, logging discrepancies in Jira, and notifying the shared services team in Teams.
  tags:
  - finance
  - intercompany
  - sap
  - sap-s4hana
  - jira
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: intercompany-finance
    port: 8080
    tools:
    - name: process-intercompany-invoice
      description: Given sending and receiving company codes and invoice number, match documents, log issues, and notify shared services.
      inputParameters:
      - name: sending_company
        in: body
        type: string
        description: SAP company code of the sending entity.
      - name: receiving_company
        in: body
        type: string
        description: SAP company code of the receiving entity.
      - name: invoice_number
        in: body
        type: string
        description: The intercompany invoice number.
      steps:
      - name: get-sending-doc
        type: call
        call: sap.get-fi-document
        with:
          company_code: '{{sending_company}}'
          invoice: '{{invoice_number}}'
      - name: get-receiving-doc
        type: call
        call: sap.get-fi-document
        with:
          company_code: '{{receiving_company}}'
          invoice: '{{invoice_number}}'
      - name: log-discrepancy
        type: call
        call: jira.create-issue
        with:
          project_key: FIN
          issuetype: Task
          summary: 'IC Match: Invoice {{invoice_number}} ({{sending_company}} → {{receiving_company}})'
          description: 'Sending amount: {{get-sending-doc.amount}} | Receiving amount: {{get-receiving-doc.amount}} | Currency: {{get-sending-doc.currency}}'
      - name: notify-shared-services
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.shared_services_team_id
          channel_id: $secrets.ic_channel_id
          text: 'IC Invoice {{invoice_number}}: {{sending_company}} → {{receiving_company}} | Sending: {{get-sending-doc.amount}} | Receiving: {{get-receiving-doc.amount}} | Jira: {{log-discrepancy.key}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/FI_DOCUMENT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: fi-documents
      path: /FIDocument(CompanyCode='{{company_code}}',Invoice='{{invoice}}')
      inputParameters:
      - name: company_code
        in: path
      - name: invoice
        in: path
      operations:
      - name: get-fi-document
        method: GET
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Processes incoming NPS survey responses from Salesforce, segments detractors for immediate follow-up via HubSpot, and updates the Power BI customer satisfaction dashboard.

naftiko: '0.5'
info:
  label: Customer NPS Survey Processing
  description: Processes incoming NPS survey responses from Salesforce, segments detractors for immediate follow-up via HubSpot, and updates the Power BI customer satisfaction dashboard.
  tags:
  - customer-experience
  - nps
  - salesforce
  - hubspot
  - power-bi
  - customer-success
capability:
  exposes:
  - type: mcp
    namespace: customer-experience
    port: 8080
    tools:
    - name: process-nps-response
      description: Given an NPS survey response and Salesforce contact ID, route detractors for follow-up in HubSpot and refresh the Power BI CX dashboard.
      inputParameters:
      - name: salesforce_contact_id
        in: body
        type: string
        description: The Salesforce contact ID of the survey respondent.
      - name: nps_score
        in: body
        type: integer
        description: NPS score 0–10.
      - name: survey_comment
        in: body
        type: string
        description: Optional open-text comment from the respondent.
      steps:
      - name: get-contact
        type: call
        call: salesforce.get-contact
        with:
          contact_id: '{{salesforce_contact_id}}'
      - name: update-salesforce-nps
        type: call
        call: salesforce.update-contact
        with:
          contact_id: '{{salesforce_contact_id}}'
          nps_score: '{{nps_score}}'
          nps_comment: '{{survey_comment}}'
      - name: create-hubspot-task
        type: call
        call: hubspot.create-task
        with:
          contact_email: '{{get-contact.email}}'
          subject: 'NPS Detractor Follow-up: {{get-contact.name}} (score {{nps_score}})'
          body: 'Comment: {{survey_comment}}'
          due_date_days: '2'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: contacts
      path: /sobjects/Contact/{{contact_id}}
      inputParameters:
      - name: contact_id
        in: path
      operations:
      - name: get-contact
        method: GET
      - name: update-contact
        method: PATCH
  - type: http
    namespace: hubspot
    baseUri: https://api.hubapi.com/crm/v3
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: tasks
      path: /objects/tasks
      operations:
      - name: create-task
        method: POST

When Workday records a termination, disables the Microsoft 365 account, raises a ServiceNow access revocation task, and notifies HR and IT in Microsoft Teams.

naftiko: '0.5'
info:
  label: Employee Offboarding
  description: When Workday records a termination, disables the Microsoft 365 account, raises a ServiceNow access revocation task, and notifies HR and IT in Microsoft Teams.
  tags:
  - hr
  - offboarding
  - workday
  - microsoft-365
  - servicenow
  - microsoft-teams
  - iam
capability:
  exposes:
  - type: mcp
    namespace: hr-offboarding
    port: 8080
    tools:
    - name: offboard-employee
      description: Given a Workday employee ID and termination date, disable their Microsoft 365 account, open a ServiceNow revocation task, and notify HR and IT in Teams.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The Workday employee ID.
      - name: termination_date
        in: body
        type: string
        description: Effective termination date in YYYY-MM-DD format.
      - name: termination_type
        in: body
        type: string
        description: Type of termination (voluntary, involuntary, retirement).
      steps:
      - name: get-employee
        type: call
        call: workday-offboard.get-worker
        with:
          worker_id: '{{employee_id}}'
      - name: disable-m365
        type: call
        call: msgraph-offboard.disable-user
        with:
          upn: '{{get-employee.work_email}}'
      - name: create-revocation-task
        type: call
        call: servicenow-offboard.create-task
        with:
          short_description: 'Offboarding access revocation: {{get-employee.full_name}}'
          description: Employee {{employee_id}} terminated {{termination_date}} ({{termination_type}}). Revoke all system access.
          category: offboarding
          assigned_group: IT_Security
      - name: notify-hr-it
        type: call
        call: msteams-offboard.send-message
        with:
          recipient_upn: hr-it-ops@3m.com
          text: 'Offboarding: {{get-employee.full_name}} | Date: {{termination_date}} | Type: {{termination_type}} | M365 disabled | Task: {{create-revocation-task.number}}'
  consumes:
  - type: http
    namespace: workday-offboard
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: msgraph-offboard
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: users
      path: /users/{{upn}}
      inputParameters:
      - name: upn
        in: path
      operations:
      - name: disable-user
        method: PATCH
  - type: http
    namespace: servicenow-offboard
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/task
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: msteams-offboard
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

When a supplier delivery is delayed, updates the SAP purchase order schedule, creates a ServiceNow case for procurement follow-up, and notifies the category manager in Teams.

naftiko: '0.5'
info:
  label: Supplier Delivery Delay Escalation
  description: When a supplier delivery is delayed, updates the SAP purchase order schedule, creates a ServiceNow case for procurement follow-up, and notifies the category manager in Teams.
  tags:
  - supply-chain
  - procurement
  - sap
  - servicenow
  - microsoft-teams
  - vendor-management
capability:
  exposes:
  - type: mcp
    namespace: supply-chain-escalation
    port: 8080
    tools:
    - name: escalate-delivery-delay
      description: Given a PO number, new estimated delivery date, and delay reason, update SAP schedule, create a ServiceNow case, and notify the category manager.
      inputParameters:
      - name: po_number
        in: body
        type: string
        description: The SAP purchase order number.
      - name: new_delivery_date
        in: body
        type: string
        description: The revised estimated delivery date.
      - name: delay_reason
        in: body
        type: string
        description: Reason provided by the supplier for the delay.
      - name: category_manager_upn
        in: body
        type: string
        description: Microsoft UPN of the procurement category manager.
      steps:
      - name: update-po-schedule
        type: call
        call: sap.update-po-delivery
        with:
          po_number: '{{po_number}}'
          delivery_date: '{{new_delivery_date}}'
          note: 'Supplier delay: {{delay_reason}}'
      - name: create-procurement-case
        type: call
        call: servicenow.create-case
        with:
          short_description: 'Supplier Delivery Delay: PO {{po_number}}'
          description: 'PO {{po_number}} delayed to {{new_delivery_date}}. Reason: {{delay_reason}}'
          category: procurement
          priority: '2'
      - name: notify-category-manager
        type: call
        call: msteams.send-chat
        with:
          recipient_upn: '{{category_manager_upn}}'
          text: 'Supplier Delay on PO {{po_number}} | New ETA: {{new_delivery_date}} | Reason: {{delay_reason}} | ServiceNow: {{create-procurement-case.number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/MM_PUR_PO_MAINT_V2_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: purchase-orders
      path: /A_PurchaseOrder('{{po_number}}')
      inputParameters:
      - name: po_number
        in: path
      operations:
      - name: update-po-delivery
        method: PATCH
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: cases
      path: /table/sn_customerservice_case
      operations:
      - name: create-case
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: chats
      path: /users/{{recipient_upn}}/chats
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-chat
        method: POST

Routes a capital expenditure request through SAP for financial posting, creates a Jira approval workflow, and notifies the plant controller and finance VP in Teams.

naftiko: '0.5'
info:
  label: Capital Expenditure Approval
  description: Routes a capital expenditure request through SAP for financial posting, creates a Jira approval workflow, and notifies the plant controller and finance VP in Teams.
  tags:
  - finance
  - capital-expenditure
  - sap
  - jira
  - microsoft-teams
  - approval
capability:
  exposes:
  - type: mcp
    namespace: capex
    port: 8080
    tools:
    - name: submit-capex-request
      description: Given a project description, amount, cost center, and approver, create SAP investment order, Jira approval, and notify finance.
      inputParameters:
      - name: project_description
        in: body
        type: string
        description: Description of the capital project.
      - name: amount
        in: body
        type: string
        description: Requested capital amount in USD.
      - name: cost_center
        in: body
        type: string
        description: SAP cost center for the expenditure.
      - name: approver_upn
        in: body
        type: string
        description: UPN of the finance approver.
      steps:
      - name: create-investment-order
        type: call
        call: sap.create-investment-order
        with:
          description: '{{project_description}}'
          planned_amount: '{{amount}}'
          cost_center: '{{cost_center}}'
          order_type: I001
      - name: create-approval-ticket
        type: call
        call: jira.create-issue
        with:
          project_key: CAPEX
          issuetype: Task
          summary: 'CapEx Approval: {{project_description}} (${{amount}})'
          description: 'Cost Center: {{cost_center}} | SAP Order: {{create-investment-order.order_number}} | Amount: ${{amount}}'
      - name: notify-approver
        type: call
        call: msteams.send-chat
        with:
          recipient_upn: '{{approver_upn}}'
          text: 'CapEx request pending your approval: {{project_description}} | ${{amount}} | SAP: {{create-investment-order.order_number}} | Jira: {{create-approval-ticket.key}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/IM_INVESTMENT_ORDER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: investment-orders
      path: /InvestmentOrder
      operations:
      - name: create-investment-order
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: chats
      path: /users/{{recipient_upn}}/chats
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-chat
        method: POST

Queries Workday to retrieve employee profile details including department, manager, location, and job title for HR and people operations.

naftiko: '0.5'
info:
  label: Workday Employee Lookup
  description: Queries Workday to retrieve employee profile details including department, manager, location, and job title for HR and people operations.
  tags:
  - hr
  - workday
  - employee
  - people-operations
capability:
  exposes:
  - type: mcp
    namespace: hr
    port: 8080
    tools:
    - name: get-employee-profile
      description: Look up a Workday employee by employee ID. Returns name, department, manager, job title, and work location.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The Workday employee ID.
      call: workday.get-worker
      with:
        employee_id: '{{employee_id}}'
      outputParameters:
      - name: full_name
        type: string
        mapping: $.Worker.Name
      - name: department
        type: string
        mapping: $.Worker.Organization
      - name: manager
        type: string
        mapping: $.Worker.Manager.Name
      - name: job_title
        type: string
        mapping: $.Worker.JobTitle
      - name: location
        type: string
        mapping: $.Worker.Location
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd5-impl-services1.workday.com/ccx/api/v1/3m
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /workers/{{employee_id}}
      inputParameters:
      - name: employee_id
        in: path
      operations:
      - name: get-worker
        method: GET

Retrieves a Safety Data Sheet from SAP EHS, uploads it to SharePoint, and distributes a notification to affected plant safety coordinators via Microsoft Teams.

naftiko: '0.5'
info:
  label: SDS Document Distribution
  description: Retrieves a Safety Data Sheet from SAP EHS, uploads it to SharePoint, and distributes a notification to affected plant safety coordinators via Microsoft Teams.
  tags:
  - safety
  - ehs
  - sap
  - sharepoint
  - microsoft-teams
  - compliance
capability:
  exposes:
  - type: mcp
    namespace: ehs-documents
    port: 8080
    tools:
    - name: distribute-sds
      description: Given a material number, retrieve the SDS from SAP, upload to SharePoint, and notify plant safety coordinators.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number.
      - name: revision_reason
        in: body
        type: string
        description: Reason for the SDS revision.
      steps:
      - name: get-sds
        type: call
        call: sap.get-sds-document
        with:
          material: '{{material_number}}'
      - name: upload-to-sharepoint
        type: call
        call: sharepoint.upload-file
        with:
          site_id: $secrets.ehs_site_id
          folder_path: /SDS/{{material_number}}
          file_name: SDS-{{material_number}}-latest.pdf
          content: '{{get-sds.document_content}}'
      - name: notify-safety-coordinators
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.safety_team_id
          channel_id: $secrets.safety_sds_channel_id
          text: 'Updated SDS for {{material_number}} now available on SharePoint. Reason: {{revision_reason}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/EHS_SDS_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: sds-documents
      path: /SafetyDataSheet(Material='{{material}}')
      inputParameters:
      - name: material
        in: path
      operations:
      - name: get-sds-document
        method: GET
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /{{site_id}}/drive/root:{{folder_path}}/{{file_name}}:/content
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      - name: file_name
        in: path
      operations:
      - name: upload-file
        method: PUT
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Performs competitive pricing analysis by pulling 3M product prices from SAP, querying market intelligence from Snowflake, and publishing insights to the Salesforce opportunity and marketing Teams channel.

naftiko: '0.5'
info:
  label: Competitive Pricing Analysis
  description: Performs competitive pricing analysis by pulling 3M product prices from SAP, querying market intelligence from Snowflake, and publishing insights to the Salesforce opportunity and marketing Teams channel.
  tags:
  - sales
  - pricing
  - sap
  - snowflake
  - salesforce
  - microsoft-teams
  - market-intelligence
capability:
  exposes:
  - type: mcp
    namespace: competitive-analysis
    port: 8080
    tools:
    - name: analyze-competitive-pricing
      description: Given a product line and competitor, pull 3M prices, market data, and publish analysis.
      inputParameters:
      - name: product_line
        in: body
        type: string
        description: 3M product line identifier.
      - name: competitor_name
        in: body
        type: string
        description: Competitor name for comparison.
      - name: salesforce_opportunity_id
        in: body
        type: string
        description: Salesforce opportunity to attach analysis.
      steps:
      - name: get-3m-pricing
        type: call
        call: sap.get-product-pricing
        with:
          product_line: '{{product_line}}'
      - name: get-market-intel
        type: call
        call: snowflake.run-query
        with:
          statement: SELECT * FROM MARKET_INTEL.COMPETITOR_PRICING WHERE competitor = '{{competitor_name}}' AND product_line = '{{product_line}}'
          warehouse: ANALYTICS_WH
      - name: update-opportunity
        type: call
        call: salesforce.add-note
        with:
          opportunity_id: '{{salesforce_opportunity_id}}'
          title: 'Competitive Pricing: {{product_line}} vs {{competitor_name}}'
          body: '3M avg price: {{get-3m-pricing.avg_price}} | Competitor avg: {{get-market-intel.competitor_avg_price}} | Delta: {{get-market-intel.price_delta_pct}}%'
      - name: notify-marketing
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.marketing_team_id
          channel_id: $secrets.pricing_channel_id
          text: 'Pricing Analysis: {{product_line}} vs {{competitor_name}} | 3M: {{get-3m-pricing.avg_price}} | Competitor: {{get-market-intel.competitor_avg_price}} | Opp: {{salesforce_opportunity_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/SD_PRICING_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: product-pricing
      path: /ProductLinePricing(ProductLine='{{product_line}}')
      inputParameters:
      - name: product_line
        in: path
      operations:
      - name: get-product-pricing
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://3m.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: run-query
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: notes
      path: /sobjects/ContentNote
      inputParameters:
      - name: opportunity_id
        in: query
      operations:
      - name: add-note
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Pulls the current Salesforce sales forecast by region, writes the data into SAP Business Warehouse for planning, and refreshes the Power BI sales leadership dashboard.

naftiko: '0.5'
info:
  label: Sales Forecast Sync
  description: Pulls the current Salesforce sales forecast by region, writes the data into SAP Business Warehouse for planning, and refreshes the Power BI sales leadership dashboard.
  tags:
  - sales
  - forecasting
  - salesforce
  - sap
  - sap-bw
  - power-bi
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: sales-planning
    port: 8080
    tools:
    - name: sync-sales-forecast
      description: Pull Salesforce opportunity forecast for a region and period, load into SAP BW, and refresh the Power BI sales dashboard.
      inputParameters:
      - name: region
        in: body
        type: string
        description: Sales region (e.g., APAC, EMEA, Americas).
      - name: forecast_period
        in: body
        type: string
        description: Forecast period in YYYY-MM format.
      steps:
      - name: get-forecast
        type: call
        call: salesforce.get-forecast
        with:
          region: '{{region}}'
          period: '{{forecast_period}}'
      - name: load-bw
        type: call
        call: sap-bw.load-forecast-data
        with:
          region: '{{region}}'
          period: '{{forecast_period}}'
          amount: '{{get-forecast.forecast_amount}}'
          currency: '{{get-forecast.currency}}'
      - name: refresh-dashboard
        type: call
        call: powerbi.refresh-dataset
        with:
          dataset_name: sales-forecast-{{region}}-{{forecast_period}}
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: forecasts
      path: /query
      inputParameters:
      - name: region
        in: query
      - name: period
        in: query
      operations:
      - name: get-forecast
        method: GET
  - type: http
    namespace: sap-bw
    baseUri: https://3m-bw.sap.com/sap/opu/odata/sap/ZBWFORECAST_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: forecast-data
      path: /ForecastSet
      operations:
      - name: load-forecast-data
        method: POST
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets/{{dataset_name}}/refreshes
      inputParameters:
      - name: dataset_name
        in: path
      operations:
      - name: refresh-dataset
        method: POST

Initiates a product batch recall by flagging the batch in SAP QM, creating a Jira tracking epic, notifying regulatory affairs via email, and posting to the quality leadership Teams channel.

naftiko: '0.5'
info:
  label: Batch Recall Initiation
  description: Initiates a product batch recall by flagging the batch in SAP QM, creating a Jira tracking epic, notifying regulatory affairs via email, and posting to the quality leadership Teams channel.
  tags:
  - quality
  - recall
  - sap
  - jira
  - microsoft-teams
  - regulatory
  - manufacturing
capability:
  exposes:
  - type: mcp
    namespace: quality-recall
    port: 8080
    tools:
    - name: initiate-batch-recall
      description: Given a material number, batch number, and recall reason, flag the batch in SAP, create a Jira epic, notify regulatory, and alert quality leadership.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number of the recalled product.
      - name: batch_number
        in: body
        type: string
        description: The production batch number to recall.
      - name: recall_reason
        in: body
        type: string
        description: Reason for the product recall.
      - name: recall_class
        in: body
        type: string
        description: 'FDA recall classification: class_i, class_ii, or class_iii.'
      steps:
      - name: create-quality-notification
        type: call
        call: sap.create-qn
        with:
          material: '{{material_number}}'
          batch: '{{batch_number}}'
          notification_type: Q2
          short_text: 'RECALL: {{material_number}} Batch {{batch_number}}'
          long_text: '{{recall_reason}} | Classification: {{recall_class}}'
      - name: create-recall-epic
        type: call
        call: jira.create-issue
        with:
          project_key: RECALL
          issuetype: Epic
          summary: 'Recall: {{material_number}} Batch {{batch_number}} ({{recall_class}})'
          description: '{{recall_reason}} | SAP QN: {{create-quality-notification.notification_id}}'
      - name: notify-regulatory
        type: call
        call: msgraph.send-mail
        with:
          to: $secrets.regulatory_affairs_dl
          subject: 'URGENT: Batch Recall Initiated — {{material_number}} / {{batch_number}}'
          body: 'A {{recall_class}} recall has been initiated for material {{material_number}}, batch {{batch_number}}. Reason: {{recall_reason}}. SAP QN: {{create-quality-notification.notification_id}}. Jira: {{create-recall-epic.key}}'
      - name: alert-quality-leadership
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.quality_team_id
          channel_id: $secrets.quality_alerts_channel_id
          text: 'RECALL INITIATED: {{material_number}} Batch {{batch_number}} | Class: {{recall_class}} | Reason: {{recall_reason}} | SAP QN: {{create-quality-notification.notification_id}} | Jira: {{create-recall-epic.key}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/QM_NOTIFICATION_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: quality-notifications
      path: /QualityNotification
      operations:
      - name: create-qn
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msgraph
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: mail
      path: /users/$secrets.service_account_upn/sendMail
      operations:
      - name: send-mail
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Monitors Apache Airflow DAG run status, logs failures to Datadog, updates the Snowflake data pipeline audit table, and opens a Jira incident when a critical DAG fails.

naftiko: '0.5'
info:
  label: Data Pipeline Monitoring
  description: Monitors Apache Airflow DAG run status, logs failures to Datadog, updates the Snowflake data pipeline audit table, and opens a Jira incident when a critical DAG fails.
  tags:
  - data-engineering
  - apache-airflow
  - datadog
  - snowflake
  - jira
  - observability
capability:
  exposes:
  - type: mcp
    namespace: data-ops
    port: 8080
    tools:
    - name: handle-dag-failure
      description: Given a failed Airflow DAG run ID, log the failure to Datadog, write an audit record to Snowflake, and open a Jira incident for the data engineering team.
      inputParameters:
      - name: dag_id
        in: body
        type: string
        description: The Airflow DAG identifier.
      - name: run_id
        in: body
        type: string
        description: The Airflow DAG run ID.
      - name: failure_reason
        in: body
        type: string
        description: Error message or reason for failure.
      - name: data_domain
        in: body
        type: string
        description: Business data domain (e.g., finance, supply_chain, hr).
      steps:
      - name: log-to-datadog
        type: call
        call: datadog.create-event
        with:
          title: 'Airflow DAG Failed: {{dag_id}}'
          text: 'Run {{run_id}} failed. Reason: {{failure_reason}}'
          alert_type: error
          tags: dag:{{dag_id}},domain:{{data_domain}}
      - name: open-jira-incident
        type: call
        call: jira.create-issue
        with:
          project_key: DATA
          issuetype: Incident
          summary: 'DAG Failure: {{dag_id}} — {{run_id}}'
          description: 'DAG {{dag_id}} run {{run_id}} failed.

            Domain: {{data_domain}}

            Reason: {{failure_reason}}

            Datadog: {{log-to-datadog.url}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST

Retrieves a Salesforce account record by ID, returning account name, industry, annual revenue, and account owner for sales and customer operations.

naftiko: '0.5'
info:
  label: Salesforce Account Lookup
  description: Retrieves a Salesforce account record by ID, returning account name, industry, annual revenue, and account owner for sales and customer operations.
  tags:
  - sales
  - salesforce
  - crm
  - account-management
capability:
  exposes:
  - type: mcp
    namespace: crm
    port: 8080
    tools:
    - name: get-account
      description: Look up a Salesforce account by account ID. Returns name, industry, revenue, owner, and billing country.
      inputParameters:
      - name: account_id
        in: body
        type: string
        description: The Salesforce account ID.
      call: salesforce.get-account
      with:
        account_id: '{{account_id}}'
      outputParameters:
      - name: name
        type: string
        mapping: $.Name
      - name: industry
        type: string
        mapping: $.Industry
      - name: annual_revenue
        type: string
        mapping: $.AnnualRevenue
      - name: owner
        type: string
        mapping: $.Owner.Name
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: accounts
      path: /sobjects/Account/{{account_id}}
      inputParameters:
      - name: account_id
        in: path
      operations:
      - name: get-account
        method: GET

Generates a Certificate of Analysis by pulling test results from SAP QM, formatting the document, uploading to SharePoint, and emailing it to the customer.

naftiko: '0.5'
info:
  label: Quality Certificate Generation
  description: Generates a Certificate of Analysis by pulling test results from SAP QM, formatting the document, uploading to SharePoint, and emailing it to the customer.
  tags:
  - quality
  - sap
  - sharepoint
  - microsoft-outlook
  - manufacturing
  - certification
capability:
  exposes:
  - type: mcp
    namespace: quality-certs
    port: 8080
    tools:
    - name: generate-coa
      description: Given a batch number and customer email, pull SAP QM results, upload COA to SharePoint, and email to customer.
      inputParameters:
      - name: batch_number
        in: body
        type: string
        description: The production batch number.
      - name: material_number
        in: body
        type: string
        description: The SAP material number.
      - name: customer_email
        in: body
        type: string
        description: Customer email address for the COA.
      steps:
      - name: get-test-results
        type: call
        call: sap.get-batch-results
        with:
          batch: '{{batch_number}}'
          material: '{{material_number}}'
      - name: upload-coa
        type: call
        call: sharepoint.upload-file
        with:
          site_id: $secrets.quality_site_id
          folder_path: /COA/{{material_number}}
          file_name: COA-{{batch_number}}.pdf
          content: '{{get-test-results.certificate_content}}'
      - name: email-customer
        type: call
        call: msgraph.send-mail
        with:
          to: '{{customer_email}}'
          subject: 3M Certificate of Analysis — {{material_number}} Batch {{batch_number}}
          body: Please find attached the Certificate of Analysis for material {{material_number}}, batch {{batch_number}}. All test parameters within specification.
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/QM_BATCH_RESULTS_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: batch-results
      path: /BatchInspectionResult(Batch='{{batch}}',Material='{{material}}')
      inputParameters:
      - name: batch
        in: path
      - name: material
        in: path
      operations:
      - name: get-batch-results
        method: GET
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /{{site_id}}/drive/root:{{folder_path}}/{{file_name}}:/content
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      - name: file_name
        in: path
      operations:
      - name: upload-file
        method: PUT
  - type: http
    namespace: msgraph
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: mail
      path: /users/$secrets.service_account_upn/sendMail
      operations:
      - name: send-mail
        method: POST

When R&D lab test results are available, records them in SAP QM, updates the Jira R&D tracker, and notifies the project scientist in Microsoft Teams.

naftiko: '0.5'
info:
  label: Lab Test Result Processing
  description: When R&D lab test results are available, records them in SAP QM, updates the Jira R&D tracker, and notifies the project scientist in Microsoft Teams.
  tags:
  - research
  - quality
  - sap
  - jira
  - microsoft-teams
  - lab-testing
capability:
  exposes:
  - type: mcp
    namespace: rd-lab
    port: 8080
    tools:
    - name: process-lab-results
      description: Given test results, material, and project info, log results in SAP QM, update Jira, and notify the project lead.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: Material number tested.
      - name: test_plan_id
        in: body
        type: string
        description: SAP QM test plan identifier.
      - name: result_status
        in: body
        type: string
        description: 'Overall result: pass, fail, or conditional.'
      - name: jira_key
        in: body
        type: string
        description: The Jira R&D project issue key.
      - name: scientist_upn
        in: body
        type: string
        description: UPN of the lead scientist.
      steps:
      - name: record-results
        type: call
        call: sap.record-inspection-results
        with:
          inspection_plan: '{{test_plan_id}}'
          material: '{{material_number}}'
          result_status: '{{result_status}}'
      - name: update-jira
        type: call
        call: jira.add-comment
        with:
          issue_key: '{{jira_key}}'
          body: 'Lab test results recorded. Material: {{material_number}} | Status: {{result_status}} | SAP Inspection: {{record-results.inspection_lot}}'
      - name: notify-scientist
        type: call
        call: msteams.send-chat
        with:
          recipient_upn: '{{scientist_upn}}'
          text: 'Lab results for {{material_number}} are in: {{result_status}} | SAP: {{record-results.inspection_lot}} | Jira: {{jira_key}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/QM_INSPECTION_RESULT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: inspection-results
      path: /InspectionResult
      operations:
      - name: record-inspection-results
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: comments
      path: /issue/{{issue_key}}/comment
      inputParameters:
      - name: issue_key
        in: path
      operations:
      - name: add-comment
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: chats
      path: /users/{{recipient_upn}}/chats
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-chat
        method: POST

Aggregates 3M content performance from LinkedIn and Meta, pushes the combined metrics to HubSpot campaign records, and posts a weekly digest to the social media Microsoft Teams channel.

naftiko: '0.5'
info:
  label: Social Media Performance Digest
  description: Aggregates 3M content performance from LinkedIn and Meta, pushes the combined metrics to HubSpot campaign records, and posts a weekly digest to the social media Microsoft Teams channel.
  tags:
  - marketing
  - social-media
  - linkedin
  - meta
  - hubspot
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: social-media
    port: 8080
    tools:
    - name: digest-social-performance
      description: Pull post engagement from LinkedIn and Meta for a given campaign ID, update HubSpot, and post a digest to Teams.
      inputParameters:
      - name: campaign_id
        in: body
        type: string
        description: Campaign identifier shared across LinkedIn, Meta, and HubSpot.
      - name: date_range
        in: body
        type: string
        description: Reporting date range in YYYY-MM-DD/YYYY-MM-DD format.
      steps:
      - name: get-linkedin-stats
        type: call
        call: linkedin.get-campaign-analytics
        with:
          campaign_id: '{{campaign_id}}'
          date_range: '{{date_range}}'
      - name: get-meta-stats
        type: call
        call: meta.get-campaign-insights
        with:
          campaign_id: '{{campaign_id}}'
          date_preset: '{{date_range}}'
      - name: update-hubspot-campaign
        type: call
        call: hubspot.update-campaign
        with:
          campaign_id: '{{campaign_id}}'
          linkedin_impressions: '{{get-linkedin-stats.impressions}}'
          linkedin_clicks: '{{get-linkedin-stats.clicks}}'
          meta_reach: '{{get-meta-stats.reach}}'
          meta_engagement: '{{get-meta-stats.engagement}}'
      - name: post-digest
        type: call
        call: msteams.send-message
        with:
          recipient_upn: social-media@3m.com
          text: 'Social Digest ({{date_range}}): LinkedIn — {{get-linkedin-stats.impressions}} impressions, {{get-linkedin-stats.clicks}} clicks | Meta — {{get-meta-stats.reach}} reach, {{get-meta-stats.engagement}} engagements | HubSpot updated.'
  consumes:
  - type: http
    namespace: linkedin
    baseUri: https://api.linkedin.com/v2
    authentication:
      type: bearer
      token: $secrets.linkedin_token
    resources:
    - name: campaign-analytics
      path: /adAnalytics
      inputParameters:
      - name: campaign_id
        in: query
      - name: date_range
        in: query
      operations:
      - name: get-campaign-analytics
        method: GET
  - type: http
    namespace: meta
    baseUri: https://graph.facebook.com/v18.0
    authentication:
      type: bearer
      token: $secrets.meta_access_token
    resources:
    - name: campaign-insights
      path: /{{campaign_id}}/insights
      inputParameters:
      - name: campaign_id
        in: path
      - name: date_preset
        in: query
      operations:
      - name: get-campaign-insights
        method: GET
  - type: http
    namespace: hubspot
    baseUri: https://api.hubapi.com/marketing/v3
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: campaigns
      path: /campaigns/{{campaign_id}}
      inputParameters:
      - name: campaign_id
        in: path
      operations:
      - name: update-campaign
        method: PATCH
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Creates a hazardous waste shipping manifest by pulling waste profile data from SAP EHS, generating the manifest in ServiceNow, and notifying the plant EHS coordinator in Teams.

naftiko: '0.5'
info:
  label: Hazardous Waste Manifest Creation
  description: Creates a hazardous waste shipping manifest by pulling waste profile data from SAP EHS, generating the manifest in ServiceNow, and notifying the plant EHS coordinator in Teams.
  tags:
  - ehs
  - safety
  - sap
  - servicenow
  - microsoft-teams
  - waste-management
  - compliance
capability:
  exposes:
  - type: mcp
    namespace: waste-management
    port: 8080
    tools:
    - name: create-waste-manifest
      description: Given waste stream details, pull SAP EHS data, create ServiceNow manifest, and notify EHS coordinator.
      inputParameters:
      - name: waste_stream_id
        in: body
        type: string
        description: SAP EHS waste stream identifier.
      - name: plant_code
        in: body
        type: string
        description: The 3M plant code.
      - name: quantity_kg
        in: body
        type: string
        description: Quantity of waste in kilograms.
      - name: disposal_facility
        in: body
        type: string
        description: Name of the disposal facility.
      steps:
      - name: get-waste-profile
        type: call
        call: sap.get-waste-profile
        with:
          waste_stream: '{{waste_stream_id}}'
          plant: '{{plant_code}}'
      - name: create-manifest
        type: call
        call: servicenow.create-manifest
        with:
          short_description: 'Hazwaste Manifest: {{waste_stream_id}} from {{plant_code}}'
          waste_class: '{{get-waste-profile.waste_class}}'
          un_number: '{{get-waste-profile.un_number}}'
          quantity: '{{quantity_kg}}'
          facility: '{{disposal_facility}}'
      - name: notify-ehs
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.ehs_team_id
          channel_id: $secrets.ehs_waste_channel_id
          text: 'Hazwaste Manifest Created: {{waste_stream_id}} | {{quantity_kg}} kg | Class: {{get-waste-profile.waste_class}} | Facility: {{disposal_facility}} | Manifest: {{create-manifest.number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/EHS_WASTE_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: waste-profiles
      path: /WasteProfile(WasteStream='{{waste_stream}}',Plant='{{plant}}')
      inputParameters:
      - name: waste_stream
        in: path
      - name: plant
        in: path
      operations:
      - name: get-waste-profile
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: manifests
      path: /table/sn_ehs_manifest
      operations:
      - name: create-manifest
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Monitors scrap rates by querying SAP production data, analyzing trends in Snowflake, and alerting the plant manager in Teams when thresholds are exceeded.

naftiko: '0.5'
info:
  label: Scrap Rate Monitoring
  description: Monitors scrap rates by querying SAP production data, analyzing trends in Snowflake, and alerting the plant manager in Teams when thresholds are exceeded.
  tags:
  - manufacturing
  - quality
  - sap
  - snowflake
  - microsoft-teams
  - production
capability:
  exposes:
  - type: mcp
    namespace: production-monitoring
    port: 8080
    tools:
    - name: check-scrap-rate
      description: Given a production line and period, check scrap rate against threshold and alert if exceeded.
      inputParameters:
      - name: production_line
        in: body
        type: string
        description: The production line identifier.
      - name: plant_code
        in: body
        type: string
        description: The 3M plant code.
      - name: period
        in: body
        type: string
        description: Reporting period (e.g., 2026-03).
      - name: threshold_pct
        in: body
        type: string
        description: Scrap rate threshold percentage.
      steps:
      - name: get-scrap-data
        type: call
        call: sap.get-production-scrap
        with:
          line: '{{production_line}}'
          plant: '{{plant_code}}'
          period: '{{period}}'
      - name: analyze-trend
        type: call
        call: snowflake.run-query
        with:
          statement: CALL MANUFACTURING.ANALYZE_SCRAP_TREND('{{production_line}}', '{{plant_code}}', '{{period}}')
          warehouse: MANUFACTURING_WH
      - name: alert-plant-manager
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.plant_ops_team_id
          channel_id: $secrets.plant_ops_channel_id
          text: 'Scrap Rate Report: Line {{production_line}} at {{plant_code}} ({{period}}) | Current: {{get-scrap-data.scrap_rate}}% | Threshold: {{threshold_pct}}% | Trend: {{analyze-trend.trend_direction}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/PP_SCRAP_ANALYSIS_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: scrap-data
      path: /ProductionScrap
      inputParameters:
      - name: line
        in: query
      - name: plant
        in: query
      - name: period
        in: query
      operations:
      - name: get-production-scrap
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://3m.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: run-query
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Retrieves the bill of materials for a finished good from SAP S/4HANA, returning component list, quantities, and assembly details for manufacturing engineering.

naftiko: '0.5'
info:
  label: SAP Bill of Materials Lookup
  description: Retrieves the bill of materials for a finished good from SAP S/4HANA, returning component list, quantities, and assembly details for manufacturing engineering.
  tags:
  - manufacturing
  - bom
  - sap
  - sap-s4hana
  - engineering
  - materials
capability:
  exposes:
  - type: mcp
    namespace: manufacturing-engineering
    port: 8080
    tools:
    - name: get-bom
      description: Look up a SAP bill of materials by material number and plant. Returns component list with quantities and units.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP finished good material number.
      - name: plant_code
        in: body
        type: string
        description: The 3M manufacturing plant code.
      call: sap.get-bom
      with:
        material_number: '{{material_number}}'
        plant: '{{plant_code}}'
      outputParameters:
      - name: bom_number
        type: string
        mapping: $.d.BillOfMaterial
      - name: components
        type: string
        mapping: $.d.to_BillOfMaterialItem.results
      - name: base_quantity
        type: string
        mapping: $.d.BOMHeaderBaseQuantity
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/API_BILL_OF_MATERIAL_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: bom
      path: /MaterialBOM(Material='{{material_number}}',Plant='{{plant}}')
      inputParameters:
      - name: material_number
        in: path
      - name: plant
        in: path
      operations:
      - name: get-bom
        method: GET
        outputRawFormat: json

When Workday creates a new employee, provisions their Microsoft 365 account, creates a personal SharePoint site, and raises a ServiceNow hardware provisioning task.

naftiko: '0.5'
info:
  label: Workspace Provisioning
  description: When Workday creates a new employee, provisions their Microsoft 365 account, creates a personal SharePoint site, and raises a ServiceNow hardware provisioning task.
  tags:
  - hr
  - it
  - microsoft-365
  - sharepoint
  - servicenow
  - workday
  - provisioning
capability:
  exposes:
  - type: mcp
    namespace: workspace-provisioning
    port: 8080
    tools:
    - name: provision-workspace
      description: Given a new Workday employee ID, create their Microsoft 365 account, SharePoint personal site, and a ServiceNow hardware request.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The Workday employee ID.
      - name: hardware_type
        in: body
        type: string
        description: Required hardware type (e.g., laptop_windows, laptop_mac, mobile).
      steps:
      - name: get-employee
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{employee_id}}'
      - name: create-m365-account
        type: call
        call: msgraph.create-user
        with:
          display_name: '{{get-employee.full_name}}'
          upn: '{{get-employee.work_email}}'
          department: '{{get-employee.department}}'
          job_title: '{{get-employee.job_title}}'
      - name: create-sharepoint-site
        type: call
        call: sharepoint.create-site
        with:
          owner_upn: '{{get-employee.work_email}}'
          site_name: '{{get-employee.full_name}}'
      - name: request-hardware
        type: call
        call: servicenow.create-request
        with:
          short_description: 'Hardware request: {{hardware_type}} for {{get-employee.full_name}}'
          category: hardware
          requested_for: '{{get-employee.work_email}}'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: msgraph
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: users
      path: /users
      operations:
      - name: create-user
        method: POST
    - name: sites
      path: /sites
      operations:
      - name: create-site
        method: POST
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: sites
      path: /
      operations:
      - name: create-site
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: requests
      path: /table/sc_request
      operations:
      - name: create-request
        method: POST

Processes a customer complaint from Salesforce by creating a SAP quality notification, opening a Jira investigation ticket, and sending an acknowledgment email to the customer through Microsoft Graph.

naftiko: '0.5'
info:
  label: Customer Complaint Processing
  description: Processes a customer complaint from Salesforce by creating a SAP quality notification, opening a Jira investigation ticket, and sending an acknowledgment email to the customer through Microsoft Graph.
  tags:
  - quality
  - customer-service
  - salesforce
  - sap
  - jira
  - microsoft-outlook
capability:
  exposes:
  - type: mcp
    namespace: customer-quality
    port: 8080
    tools:
    - name: process-complaint
      description: Given a Salesforce case ID, create a SAP quality notification, open a Jira ticket, and send a customer acknowledgment email.
      inputParameters:
      - name: case_id
        in: body
        type: string
        description: The Salesforce case ID for the complaint.
      - name: product_number
        in: body
        type: string
        description: The product material number.
      - name: complaint_description
        in: body
        type: string
        description: Description of the customer complaint.
      - name: customer_email
        in: body
        type: string
        description: Customer email for acknowledgment.
      steps:
      - name: create-sap-qn
        type: call
        call: sap.create-quality-notification
        with:
          material: '{{product_number}}'
          notification_type: Q3
          short_text: 'Customer Complaint: {{product_number}}'
          long_text: '{{complaint_description}} | Salesforce Case: {{case_id}}'
      - name: create-jira-investigation
        type: call
        call: jira.create-issue
        with:
          project_key: QA
          issuetype: Task
          summary: 'Investigate complaint: {{product_number}} — Case {{case_id}}'
          description: '{{complaint_description}} | SAP QN: {{create-sap-qn.notification_id}}'
      - name: send-acknowledgment
        type: call
        call: msgraph.send-mail
        with:
          to: '{{customer_email}}'
          subject: 3M — Your complaint has been received (Case {{case_id}})
          body: 'Thank you for contacting 3M. Your complaint regarding product {{product_number}} has been logged and assigned for investigation. Reference: {{create-sap-qn.notification_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/QM_NOTIFICATION_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: quality-notifications
      path: /QualityNotification
      operations:
      - name: create-quality-notification
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msgraph
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: mail
      path: /users/$secrets.service_account_upn/sendMail
      operations:
      - name: send-mail
        method: POST

When a Snowflake data quality check fails (row count anomaly, null threshold breach, or schema drift), logs the failure to Datadog, opens a Jira data quality ticket, and notifies the data engineering team in Microsoft Teams.

naftiko: '0.5'
info:
  label: Snowflake Data Quality Alert
  description: When a Snowflake data quality check fails (row count anomaly, null threshold breach, or schema drift), logs the failure to Datadog, opens a Jira data quality ticket, and notifies the data engineering team in Microsoft Teams.
  tags:
  - data-quality
  - snowflake
  - datadog
  - jira
  - microsoft-teams
  - data-engineering
capability:
  exposes:
  - type: mcp
    namespace: data-quality
    port: 8080
    tools:
    - name: handle-data-quality-failure
      description: Given a Snowflake table and data quality check failure type, log to Datadog, open a Jira ticket, and notify the data team in Teams.
      inputParameters:
      - name: table_name
        in: body
        type: string
        description: Fully-qualified Snowflake table name (database.schema.table).
      - name: check_type
        in: body
        type: string
        description: Type of check that failed (row_count, null_threshold, schema_drift, duplicate_key).
      - name: expected_value
        in: body
        type: string
        description: Expected value or threshold.
      - name: actual_value
        in: body
        type: string
        description: Actual observed value.
      - name: data_domain
        in: body
        type: string
        description: Business data domain (finance, hr, supply_chain, etc.).
      steps:
      - name: log-datadog
        type: call
        call: datadog.create-event
        with:
          title: 'Data Quality Failure: {{check_type}} on {{table_name}}'
          text: 'Expected: {{expected_value}} | Actual: {{actual_value}} | Domain: {{data_domain}}'
          alert_type: error
          tags: data_quality:{{check_type}},domain:{{data_domain}}
      - name: open-jira-ticket
        type: call
        call: jira.create-issue
        with:
          project_key: DATA
          issuetype: Bug
          summary: 'Data Quality: {{check_type}} failure on {{table_name}}'
          description: 'Table: {{table_name}}

            Check: {{check_type}}

            Expected: {{expected_value}}

            Actual: {{actual_value}}

            Domain: {{data_domain}}

            Datadog: {{log-datadog.url}}'
      - name: notify-team
        type: call
        call: msteams.send-message
        with:
          recipient_upn: data-engineering@3m.com
          text: 'Data Quality Failure: {{check_type}} on {{table_name}} | Expected: {{expected_value}} | Actual: {{actual_value}} | Jira: {{open-jira-ticket.key}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Updates distributor pricing by pulling new price conditions from SAP, generating a price list in Snowflake, and distributing it via email to the channel sales team and distributor contacts.

naftiko: '0.5'
info:
  label: Distributor Price List Update
  description: Updates distributor pricing by pulling new price conditions from SAP, generating a price list in Snowflake, and distributing it via email to the channel sales team and distributor contacts.
  tags:
  - sales
  - pricing
  - sap
  - snowflake
  - microsoft-outlook
  - distribution
capability:
  exposes:
  - type: mcp
    namespace: pricing
    port: 8080
    tools:
    - name: update-price-list
      description: Given a distributor ID and effective date, pull SAP pricing, generate price list, and distribute via email.
      inputParameters:
      - name: distributor_id
        in: body
        type: string
        description: SAP customer number of the distributor.
      - name: effective_date
        in: body
        type: string
        description: Effective date for new pricing.
      - name: distributor_email
        in: body
        type: string
        description: Distributor contact email.
      steps:
      - name: get-price-conditions
        type: call
        call: sap.get-pricing
        with:
          customer: '{{distributor_id}}'
          valid_from: '{{effective_date}}'
      - name: generate-price-list
        type: call
        call: snowflake.run-query
        with:
          statement: CALL SALES.GENERATE_PRICE_LIST('{{distributor_id}}', '{{effective_date}}')
          warehouse: SALES_WH
      - name: send-price-list
        type: call
        call: msgraph.send-mail
        with:
          to: '{{distributor_email}}'
          subject: 3M Updated Price List — Effective {{effective_date}}
          body: 'Please find the updated price list effective {{effective_date}}. Total items: {{generate-price-list.item_count}}. Contact your 3M representative for questions.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/SD_PRICING_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: pricing
      path: /PriceCondition
      inputParameters:
      - name: customer
        in: query
      - name: valid_from
        in: query
      operations:
      - name: get-pricing
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://3m.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: run-query
        method: POST
  - type: http
    namespace: msgraph
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: mail
      path: /users/$secrets.service_account_upn/sendMail
      operations:
      - name: send-mail
        method: POST

When a SAP Ariba requisition exceeds a spend threshold, routes for manager approval via Workday and notifies the requestor in Microsoft Teams with approval status.

naftiko: '0.5'
info:
  label: Procurement Approval Pipeline
  description: When a SAP Ariba requisition exceeds a spend threshold, routes for manager approval via Workday and notifies the requestor in Microsoft Teams with approval status.
  tags:
  - procurement
  - ariba
  - sap-ariba
  - workday
  - microsoft-teams
  - approval
  - spend-management
capability:
  exposes:
  - type: mcp
    namespace: procurement
    port: 8080
    tools:
    - name: route-requisition-approval
      description: Given an Ariba requisition ID and requestor employee ID, check the requisition amount, resolve the approver from Workday, and notify both parties in Microsoft Teams.
      inputParameters:
      - name: requisition_id
        in: body
        type: string
        description: The SAP Ariba requisition identifier.
      - name: requestor_employee_id
        in: body
        type: string
        description: The Workday employee ID of the requestor.
      - name: spend_amount
        in: body
        type: number
        description: The total spend amount on the requisition.
      steps:
      - name: get-requisition
        type: call
        call: ariba.get-requisition
        with:
          requisition_id: '{{requisition_id}}'
      - name: get-requestor
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{requestor_employee_id}}'
      - name: get-manager
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{get-requestor.manager_id}}'
      - name: notify-approver
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{get-manager.work_email}}'
          text: 'Approval Required: Ariba requisition {{requisition_id}} from {{get-requestor.full_name}} for ${{spend_amount}}. Vendor: {{get-requisition.vendor_name}}. Please review: {{get-requisition.approval_url}}'
      - name: notify-requestor
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{get-requestor.work_email}}'
          text: Your requisition {{requisition_id}} (${{spend_amount}}) has been routed to {{get-manager.full_name}} for approval.
  consumes:
  - type: http
    namespace: ariba
    baseUri: https://openapi.ariba.com/api/purchase-req/v1
    authentication:
      type: bearer
      token: $secrets.ariba_token
    resources:
    - name: requisitions
      path: /requisitions/{{requisition_id}}
      inputParameters:
      - name: requisition_id
        in: path
      operations:
      - name: get-requisition
        method: GET
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Triggers a Kubernetes rolling deployment from a GitHub Actions release, monitors rollout health via Datadog, and posts the deployment result to the engineering Microsoft Teams channel.

naftiko: '0.5'
info:
  label: Kubernetes Deployment Rollout
  description: Triggers a Kubernetes rolling deployment from a GitHub Actions release, monitors rollout health via Datadog, and posts the deployment result to the engineering Microsoft Teams channel.
  tags:
  - devops
  - kubernetes
  - github-actions
  - datadog
  - microsoft-teams
  - deployment
capability:
  exposes:
  - type: mcp
    namespace: k8s-deploy
    port: 8080
    tools:
    - name: rollout-deployment
      description: Given a GitHub release tag and Kubernetes namespace, trigger a rolling deployment and monitor health via Datadog. Post the result to Teams.
      inputParameters:
      - name: repository
        in: body
        type: string
        description: GitHub repository in owner/repo format.
      - name: release_tag
        in: body
        type: string
        description: The Git tag to deploy (e.g., v2.4.1).
      - name: k8s_namespace
        in: body
        type: string
        description: Kubernetes namespace to deploy into.
      - name: service_name
        in: body
        type: string
        description: Datadog service name for health monitoring.
      steps:
      - name: trigger-workflow
        type: call
        call: github.create-workflow-dispatch
        with:
          repository: '{{repository}}'
          workflow_id: deploy.yml
          ref: '{{release_tag}}'
          namespace: '{{k8s_namespace}}'
      - name: create-deployment-marker
        type: call
        call: datadog.create-event
        with:
          title: 'Deployment: {{repository}} {{release_tag}} → {{k8s_namespace}}'
          text: 'Rolling deployment triggered. Workflow: {{trigger-workflow.run_id}}'
          alert_type: info
          tags: service:{{service_name}},env:{{k8s_namespace}}
      - name: notify-team
        type: call
        call: msteams.send-message
        with:
          recipient_upn: engineering-deploys@3m.com
          text: 'Deployment: {{repository}} {{release_tag}} → {{k8s_namespace}} | Run: {{trigger-workflow.run_id}} | Datadog: {{create-deployment-marker.url}}'
  consumes:
  - type: http
    namespace: github
    baseUri: https://api.github.com
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: workflow-dispatches
      path: /repos/{{repository}}/actions/workflows/{{workflow_id}}/dispatches
      inputParameters:
      - name: repository
        in: path
      - name: workflow_id
        in: path
      operations:
      - name: create-workflow-dispatch
        method: POST
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

When a Salesforce opportunity closes as won, enrolls the customer in a HubSpot onboarding workflow, provisions a SharePoint customer portal, and notifies the customer success team in Teams.

naftiko: '0.5'
info:
  label: Customer Onboarding Provisioning
  description: When a Salesforce opportunity closes as won, enrolls the customer in a HubSpot onboarding workflow, provisions a SharePoint customer portal, and notifies the customer success team in Teams.
  tags:
  - sales
  - customer-success
  - salesforce
  - hubspot
  - sharepoint
  - microsoft-teams
  - onboarding
capability:
  exposes:
  - type: mcp
    namespace: customer-onboarding
    port: 8080
    tools:
    - name: provision-customer-onboarding
      description: Given a closed-won Salesforce opportunity ID, enroll in HubSpot onboarding, provision a SharePoint portal, and notify the CSM in Teams.
      inputParameters:
      - name: salesforce_opportunity_id
        in: body
        type: string
        description: The closed-won Salesforce opportunity ID.
      - name: Cm_upn
        in: body
        type: string
        description: Microsoft UPN of the assigned customer success manager.
      steps:
      - name: get-opportunity
        type: call
        call: salesforce-cx.get-opportunity
        with:
          opportunity_id: '{{salesforce_opportunity_id}}'
      - name: enroll-hubspot
        type: call
        call: hubspot-cx.enroll-workflow
        with:
          contact_email: '{{get-opportunity.primary_contact_email}}'
          workflow_name: enterprise-onboarding
      - name: create-portal
        type: call
        call: sharepoint-cx.create-folder
        with:
          site_id: customer_portals_site
          folder_path: Customers/{{get-opportunity.account_name}}
      - name: notify-csm
        type: call
        call: msteams-cx.send-message
        with:
          recipient_upn: '{{csm_upn}}'
          text: 'New Customer: {{get-opportunity.account_name}} | Value: {{get-opportunity.amount}} | Portal: {{create-portal.url}} | HubSpot enrolled.'
  consumes:
  - type: http
    namespace: salesforce-cx
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: opportunities
      path: /sobjects/Opportunity/{{opportunity_id}}
      inputParameters:
      - name: opportunity_id
        in: path
      operations:
      - name: get-opportunity
        method: GET
  - type: http
    namespace: hubspot-cx
    baseUri: https://api.hubapi.com/automation/v4
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: workflow-enrollments
      path: /flows/enrollments
      operations:
      - name: enroll-workflow
        method: POST
  - type: http
    namespace: sharepoint-cx
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: folders
      path: /{{site_id}}/drive/root:/{{folder_path}}
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      operations:
      - name: create-folder
        method: POST
  - type: http
    namespace: msteams-cx
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves submitted expense reports from SAP Concur, validates against Workday cost center data, and opens a ServiceNow task for finance review when policy exceptions are detected.

naftiko: '0.5'
info:
  label: Expense Report Processing
  description: Retrieves submitted expense reports from SAP Concur, validates against Workday cost center data, and opens a ServiceNow task for finance review when policy exceptions are detected.
  tags:
  - finance
  - expense
  - concur
  - sap-concur
  - workday
  - servicenow
  - policy-compliance
capability:
  exposes:
  - type: mcp
    namespace: finance-expense
    port: 8080
    tools:
    - name: review-expense-report
      description: Given a Concur expense report ID and employee ID, fetch the report details, validate the cost center against Workday, and flag any policy violations to ServiceNow.
      inputParameters:
      - name: expense_report_id
        in: body
        type: string
        description: The SAP Concur expense report ID.
      - name: employee_id
        in: body
        type: string
        description: The Workday employee ID of the expense submitter.
      steps:
      - name: get-expense-report
        type: call
        call: concur.get-expense-report
        with:
          report_id: '{{expense_report_id}}'
      - name: get-employee
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{employee_id}}'
      - name: open-review-task
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Expense policy review: {{get-expense-report.report_name}} — {{get-employee.full_name}}'
          description: 'Report {{expense_report_id}} total: {{get-expense-report.total_amount}} {{get-expense-report.currency}}. Cost center: {{get-employee.cost_center}}. Submitted: {{get-expense-report.submit_date}}.'
          assigned_group: Finance_Audit
          category: expense_review
  consumes:
  - type: http
    namespace: concur
    baseUri: https://www.concursolutions.com/api/v3.0
    authentication:
      type: bearer
      token: $secrets.concur_token
    resources:
    - name: expense-reports
      path: /expense/reports/{{report_id}}
      inputParameters:
      - name: report_id
        in: path
      operations:
      - name: get-expense-report
        method: GET
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/task
      operations:
      - name: create-task
        method: POST

Files customs declarations for international shipments by pulling export data from SAP GTS, creating a compliance record in ServiceNow, and notifying the trade compliance team in Teams.

naftiko: '0.5'
info:
  label: Customs Declaration Filing
  description: Files customs declarations for international shipments by pulling export data from SAP GTS, creating a compliance record in ServiceNow, and notifying the trade compliance team in Teams.
  tags:
  - logistics
  - trade-compliance
  - sap
  - servicenow
  - microsoft-teams
  - customs
capability:
  exposes:
  - type: mcp
    namespace: trade-compliance
    port: 8080
    tools:
    - name: file-customs-declaration
      description: Given a shipment reference and destination country, pull SAP GTS data, create compliance record, and notify trade team.
      inputParameters:
      - name: shipment_reference
        in: body
        type: string
        description: SAP shipment document number.
      - name: destination_country
        in: body
        type: string
        description: ISO country code of destination.
      - name: incoterms
        in: body
        type: string
        description: Incoterms code (e.g., FOB, CIF, DDP).
      steps:
      - name: get-export-data
        type: call
        call: sap.get-gts-declaration
        with:
          shipment: '{{shipment_reference}}'
          country: '{{destination_country}}'
      - name: create-compliance-record
        type: call
        call: servicenow.create-compliance-record
        with:
          short_description: 'Customs Declaration: {{shipment_reference}} to {{destination_country}}'
          classification: '{{get-export-data.tariff_code}}'
          value: '{{get-export-data.declared_value}}'
          incoterms: '{{incoterms}}'
      - name: notify-trade-team
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.trade_team_id
          channel_id: $secrets.trade_channel_id
          text: 'Customs Declaration Filed: {{shipment_reference}} to {{destination_country}} | Tariff: {{get-export-data.tariff_code}} | Value: {{get-export-data.declared_value}} | ServiceNow: {{create-compliance-record.number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/GTS_DECLARATION_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: declarations
      path: /CustomsDeclaration(Shipment='{{shipment}}',Country='{{country}}')
      inputParameters:
      - name: shipment
        in: path
      - name: country
        in: path
      operations:
      - name: get-gts-declaration
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: compliance
      path: /table/sn_compliance_record
      operations:
      - name: create-compliance-record
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Retrieves a procurement contract from SAP Ariba by contract ID, returning status, expiry date, supplier, and contract value for strategic sourcing.

naftiko: '0.5'
info:
  label: SAP Ariba Contract Lookup
  description: Retrieves a procurement contract from SAP Ariba by contract ID, returning status, expiry date, supplier, and contract value for strategic sourcing.
  tags:
  - procurement
  - sap-ariba
  - contract-management
  - sourcing
capability:
  exposes:
  - type: mcp
    namespace: sourcing
    port: 8080
    tools:
    - name: get-contract
      description: Look up an SAP Ariba contract by contract ID. Returns status, supplier, value, and expiry date.
      inputParameters:
      - name: contract_id
        in: body
        type: string
        description: The SAP Ariba contract ID.
      call: ariba.get-contract
      with:
        contract_id: '{{contract_id}}'
      outputParameters:
      - name: status
        type: string
        mapping: $.Status
      - name: supplier
        type: string
        mapping: $.Supplier.Name
      - name: contract_value
        type: string
        mapping: $.Amount.Amount
      - name: expiry_date
        type: string
        mapping: $.ExpirationDate
  consumes:
  - type: http
    namespace: ariba
    baseUri: https://openapi.ariba.com/api/contract-compliance/v1/prod
    authentication:
      type: bearer
      token: $secrets.ariba_token
    inputParameters:
    - name: apiKey
      in: header
      value: $secrets.ariba_api_key
    resources:
    - name: contracts
      path: /contracts/{{contract_id}}
      inputParameters:
      - name: contract_id
        in: path
      operations:
      - name: get-contract
        method: GET

Creates a preventive maintenance work order in SAP Plant Maintenance, assigns a technician in ServiceNow, and sends a calendar invite via Microsoft Graph for scheduled maintenance windows.

naftiko: '0.5'
info:
  label: Preventive Maintenance Scheduling
  description: Creates a preventive maintenance work order in SAP Plant Maintenance, assigns a technician in ServiceNow, and sends a calendar invite via Microsoft Graph for scheduled maintenance windows.
  tags:
  - maintenance
  - sap
  - servicenow
  - microsoft-outlook
  - manufacturing
  - scheduling
capability:
  exposes:
  - type: mcp
    namespace: maintenance-scheduling
    port: 8080
    tools:
    - name: schedule-preventive-maintenance
      description: Given equipment ID, maintenance type, and scheduled date, create SAP PM order, assign in ServiceNow, and send calendar invite.
      inputParameters:
      - name: equipment_id
        in: body
        type: string
        description: The SAP equipment ID.
      - name: plant_code
        in: body
        type: string
        description: The 3M plant code.
      - name: maintenance_type
        in: body
        type: string
        description: Type of maintenance (e.g., calibration, inspection, overhaul).
      - name: scheduled_date
        in: body
        type: string
        description: Scheduled date for maintenance.
      - name: technician_upn
        in: body
        type: string
        description: UPN of the assigned maintenance technician.
      steps:
      - name: create-pm-order
        type: call
        call: sap.create-pm-order
        with:
          equipment: '{{equipment_id}}'
          plant: '{{plant_code}}'
          order_type: PM01
          short_text: 'PM: {{maintenance_type}} — {{equipment_id}}'
          scheduled_start: '{{scheduled_date}}'
      - name: create-snow-task
        type: call
        call: servicenow.create-task
        with:
          short_description: 'PM: {{maintenance_type}} for {{equipment_id}}'
          assigned_to: '{{technician_upn}}'
          scheduled_date: '{{scheduled_date}}'
          reference: '{{create-pm-order.order_number}}'
      - name: send-calendar-invite
        type: call
        call: msgraph.create-event
        with:
          attendee: '{{technician_upn}}'
          subject: 'Preventive Maintenance: {{maintenance_type}} — {{equipment_id}}'
          start: '{{scheduled_date}}T08:00:00'
          end: '{{scheduled_date}}T12:00:00'
          body: 'SAP Order: {{create-pm-order.order_number}} | Plant: {{plant_code}} | Equipment: {{equipment_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/PM_ORDER_CREATE_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: pm-orders
      path: /MaintenanceOrder
      operations:
      - name: create-pm-order
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/sc_task
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: msgraph
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: events
      path: /users/{{attendee}}/events
      inputParameters:
      - name: attendee
        in: path
      operations:
      - name: create-event
        method: POST

When a Salesforce case breaches SLA, escalates to a ServiceNow priority incident, notifies the customer success manager in Microsoft Teams, and logs the escalation in Confluence.

naftiko: '0.5'
info:
  label: Customer Support Ticket Escalation
  description: When a Salesforce case breaches SLA, escalates to a ServiceNow priority incident, notifies the customer success manager in Microsoft Teams, and logs the escalation in Confluence.
  tags:
  - customer-support
  - crm
  - salesforce
  - servicenow
  - confluence
  - microsoft-teams
  - sla
capability:
  exposes:
  - type: mcp
    namespace: customer-support
    port: 8080
    tools:
    - name: escalate-sla-breach
      description: Given a Salesforce case ID that has breached SLA, open a ServiceNow priority incident, notify the CSM in Teams, and document in Confluence.
      inputParameters:
      - name: salesforce_case_id
        in: body
        type: string
        description: The Salesforce case record ID.
      - name: Cm_upn
        in: body
        type: string
        description: Microsoft UPN of the customer success manager.
      - name: escalation_reason
        in: body
        type: string
        description: Description of why SLA was breached.
      steps:
      - name: get-case
        type: call
        call: salesforce.get-case
        with:
          case_id: '{{salesforce_case_id}}'
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'SLA Breach Escalation: {{get-case.subject}}'
          description: 'Salesforce Case {{salesforce_case_id}} breached SLA. Customer: {{get-case.account_name}}. Reason: {{escalation_reason}}'
          urgency: '2'
          impact: '2'
          category: customer_escalation
      - name: notify-csm
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{csm_upn}}'
          text: 'SLA Breach: Case {{salesforce_case_id}} — {{get-case.subject}} | Customer: {{get-case.account_name}} | ServiceNow: {{create-incident.number}} | Reason: {{escalation_reason}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: cases
      path: /sobjects/Case/{{case_id}}
      inputParameters:
      - name: case_id
        in: path
      operations:
      - name: get-case
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Monitors MuleSoft API Manager for failed flows, correlates with Datadog APM traces, opens a ServiceNow integration incident, and notifies the integration team in Microsoft Teams.

naftiko: '0.5'
info:
  label: MuleSoft Integration Health Monitor
  description: Monitors MuleSoft API Manager for failed flows, correlates with Datadog APM traces, opens a ServiceNow integration incident, and notifies the integration team in Microsoft Teams.
  tags:
  - integration
  - mulesoft
  - datadog
  - servicenow
  - microsoft-teams
  - api-management
capability:
  exposes:
  - type: mcp
    namespace: integration-ops
    port: 8080
    tools:
    - name: handle-integration-failure
      description: Given a MuleSoft flow failure event, correlate with Datadog traces, open a ServiceNow incident, and alert the integration team in Teams.
      inputParameters:
      - name: flow_name
        in: body
        type: string
        description: The name of the failed MuleSoft flow.
      - name: environment
        in: body
        type: string
        description: MuleSoft environment (dev, staging, prod).
      - name: error_message
        in: body
        type: string
        description: Error message from the failed flow.
      - name: correlation_id
        in: body
        type: string
        description: MuleSoft correlation ID for trace lookup.
      steps:
      - name: log-datadog
        type: call
        call: datadog.create-event
        with:
          title: 'MuleSoft Flow Failure: {{flow_name}} ({{environment}})'
          text: 'Error: {{error_message}} | Correlation: {{correlation_id}}'
          alert_type: error
          tags: integration:mulesoft,flow:{{flow_name}},env:{{environment}}
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Integration Failure: {{flow_name}} in {{environment}}'
          description: 'MuleSoft flow {{flow_name}} failed in {{environment}}.

            Error: {{error_message}}

            Correlation ID: {{correlation_id}}

            Datadog: {{log-datadog.url}}'
          category: integration
          urgency: '2'
      - name: notify-team
        type: call
        call: msteams.send-message
        with:
          recipient_upn: integration-ops@3m.com
          text: 'MuleSoft Failure: {{flow_name}} ({{environment}}) | Error: {{error_message}} | ServiceNow: {{create-incident.number}} | Datadog: {{log-datadog.url}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Tracks resolution of internal audit findings by creating corrective actions in ServiceNow, assigning owners in Jira, and reporting status to the audit committee in Teams.

naftiko: '0.5'
info:
  label: Plant Audit Finding Resolution
  description: Tracks resolution of internal audit findings by creating corrective actions in ServiceNow, assigning owners in Jira, and reporting status to the audit committee in Teams.
  tags:
  - audit
  - compliance
  - servicenow
  - jira
  - microsoft-teams
  - quality
capability:
  exposes:
  - type: mcp
    namespace: audit-management
    port: 8080
    tools:
    - name: resolve-audit-finding
      description: Given an audit finding, create corrective action in ServiceNow, assign in Jira, and notify audit committee.
      inputParameters:
      - name: finding_id
        in: body
        type: string
        description: The audit finding reference number.
      - name: finding_description
        in: body
        type: string
        description: Description of the audit finding.
      - name: severity
        in: body
        type: string
        description: 'Finding severity: minor, major, critical.'
      - name: owner_upn
        in: body
        type: string
        description: UPN of the corrective action owner.
      - name: due_date
        in: body
        type: string
        description: Due date for resolution.
      steps:
      - name: create-capa
        type: call
        call: servicenow.create-capa
        with:
          short_description: 'Audit Finding {{finding_id}}: {{finding_description}}'
          severity: '{{severity}}'
          assigned_to: '{{owner_upn}}'
          due_date: '{{due_date}}'
      - name: create-jira-task
        type: call
        call: jira.create-issue
        with:
          project_key: AUDIT
          issuetype: Task
          summary: 'CAPA: {{finding_id}} — {{finding_description}}'
          description: 'Severity: {{severity}} | Due: {{due_date}} | ServiceNow CAPA: {{create-capa.number}}'
          assignee: '{{owner_upn}}'
      - name: notify-audit-committee
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.audit_team_id
          channel_id: $secrets.audit_channel_id
          text: 'Audit Finding {{finding_id}} ({{severity}}): {{finding_description}} | Owner: {{owner_upn}} | Due: {{due_date}} | CAPA: {{create-capa.number}} | Jira: {{create-jira-task.key}}'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: capa
      path: /table/sn_quality_capa
      operations:
      - name: create-capa
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

When a product defect is reported from Salesforce field service, creates a Jira defect ticket, logs a SAP quality notification, and opens a ServiceNow change request for the engineering team.

naftiko: '0.5'
info:
  label: Product Defect Tracking
  description: When a product defect is reported from Salesforce field service, creates a Jira defect ticket, logs a SAP quality notification, and opens a ServiceNow change request for the engineering team.
  tags:
  - quality
  - product
  - salesforce
  - jira
  - sap
  - servicenow
  - manufacturing
capability:
  exposes:
  - type: mcp
    namespace: quality-management
    port: 8080
    tools:
    - name: report-product-defect
      description: Given a Salesforce field service case ID and product number, open a Jira defect, log a SAP quality notification, and create a ServiceNow change for engineering review.
      inputParameters:
      - name: salesforce_case_id
        in: body
        type: string
        description: The Salesforce field service case ID.
      - name: product_number
        in: body
        type: string
        description: The SAP material/product number with the defect.
      - name: defect_description
        in: body
        type: string
        description: Description of the product defect.
      - name: batch_number
        in: body
        type: string
        description: The production batch number if known.
      steps:
      - name: get-case
        type: call
        call: salesforce.get-case
        with:
          case_id: '{{salesforce_case_id}}'
      - name: create-jira-defect
        type: call
        call: jira.create-issue
        with:
          project_key: QA
          issuetype: Bug
          summary: 'Product Defect: {{product_number}} — {{defect_description}}'
          description: 'Customer: {{get-case.account_name}} | Batch: {{batch_number}} | Case: {{salesforce_case_id}} | Defect: {{defect_description}}'
      - name: log-sap-qn
        type: call
        call: sap.create-quality-notification
        with:
          material: '{{product_number}}'
          batch: '{{batch_number}}'
          short_text: 'Defect: {{defect_description}}'
          notification_type: Q1
      - name: create-change
        type: call
        call: servicenow.create-change-request
        with:
          short_description: 'Engineering review: product defect {{product_number}}'
          description: 'Defect in {{product_number}} (batch {{batch_number}}). Jira: {{create-jira-defect.key}} | SAP QN: {{log-sap-qn.notification_id}}'
          category: product_quality
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: cases
      path: /sobjects/Case/{{case_id}}
      inputParameters:
      - name: case_id
        in: path
      operations:
      - name: get-case
        method: GET
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/QM_NOTIFICATION_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: quality-notifications
      path: /QualityNotification
      operations:
      - name: create-quality-notification
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: change-requests
      path: /table/change_request
      operations:
      - name: create-change-request
        method: POST

Retrieves vendor master data from SAP S/4HANA by vendor number, returning company name, payment terms, currency, and purchasing organization details.

naftiko: '0.5'
info:
  label: SAP Vendor Master Lookup
  description: Retrieves vendor master data from SAP S/4HANA by vendor number, returning company name, payment terms, currency, and purchasing organization details.
  tags:
  - procurement
  - vendor
  - sap
  - sap-s4hana
  - master-data
capability:
  exposes:
  - type: mcp
    namespace: vendor-management
    port: 8080
    tools:
    - name: get-vendor
      description: Look up SAP vendor master data by vendor number. Returns company name, payment terms, and purchasing organization.
      inputParameters:
      - name: vendor_number
        in: body
        type: string
        description: The SAP vendor account number.
      call: sap.get-vendor
      with:
        vendor_number: '{{vendor_number}}'
      outputParameters:
      - name: company_name
        type: string
        mapping: $.d.SupplierName
      - name: payment_terms
        type: string
        mapping: $.d.PaymentTerms
      - name: currency
        type: string
        mapping: $.d.Currency
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/API_BUSINESS_PARTNER
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: vendors
      path: /A_Supplier('{{vendor_number}}')
      inputParameters:
      - name: vendor_number
        in: path
      operations:
      - name: get-vendor
        method: GET
        outputRawFormat: json

Prepares for an OSHA compliance audit by pulling safety incident records from ServiceNow, gathering training completion data from Workday, and compiling an audit readiness report in SharePoint.

naftiko: '0.5'
info:
  label: OSHA Compliance Audit Preparation
  description: Prepares for an OSHA compliance audit by pulling safety incident records from ServiceNow, gathering training completion data from Workday, and compiling an audit readiness report in SharePoint.
  tags:
  - safety
  - compliance
  - osha
  - servicenow
  - workday
  - sharepoint
capability:
  exposes:
  - type: mcp
    namespace: compliance-audit
    port: 8080
    tools:
    - name: prepare-osha-audit
      description: Given a plant code and audit date, pull incident records, training data, and compile an audit report.
      inputParameters:
      - name: plant_code
        in: body
        type: string
        description: The 3M plant code being audited.
      - name: audit_date
        in: body
        type: string
        description: Scheduled audit date.
      - name: audit_scope
        in: body
        type: string
        description: Scope of the OSHA audit (e.g., general_safety, chemical_handling, lockout_tagout).
      steps:
      - name: get-incident-records
        type: call
        call: servicenow.get-ehs-cases
        with:
          location: '{{plant_code}}'
          date_range: last_12_months
          category: '{{audit_scope}}'
      - name: get-training-compliance
        type: call
        call: workday.get-training-completions
        with:
          location: '{{plant_code}}'
          training_category: '{{audit_scope}}'
      - name: upload-audit-report
        type: call
        call: sharepoint.upload-file
        with:
          site_id: $secrets.ehs_site_id
          folder_path: /Audits/OSHA/{{plant_code}}
          file_name: OSHA-Audit-Prep-{{plant_code}}-{{audit_date}}.json
          content: 'Incidents: {{get-incident-records.total_count}} | Training Compliance: {{get-training-compliance.completion_rate}}%'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: ehs-cases
      path: /table/sn_ehs_case
      inputParameters:
      - name: location
        in: query
      - name: date_range
        in: query
      - name: category
        in: query
      operations:
      - name: get-ehs-cases
        method: GET
  - type: http
    namespace: workday
    baseUri: https://wd5-impl-services1.workday.com/ccx/api/v1/3m
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: training
      path: /trainingCompletions
      inputParameters:
      - name: location
        in: query
      - name: training_category
        in: query
      operations:
      - name: get-training-completions
        method: GET
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /{{site_id}}/drive/root:{{folder_path}}/{{file_name}}:/content
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      - name: file_name
        in: path
      operations:
      - name: upload-file
        method: PUT

Triggers an Azure Databricks ML training job, tracks the experiment in the model registry, logs metrics to Datadog, and posts training results to the data science Microsoft Teams channel.

naftiko: '0.5'
info:
  label: ML Model Training Pipeline
  description: Triggers an Azure Databricks ML training job, tracks the experiment in the model registry, logs metrics to Datadog, and posts training results to the data science Microsoft Teams channel.
  tags:
  - machine-learning
  - azure-databricks
  - datadog
  - microsoft-teams
  - data-science
  - mlops
capability:
  exposes:
  - type: mcp
    namespace: mlops
    port: 8080
    tools:
    - name: run-training-job
      description: Given a Databricks job ID and model name, trigger training, log metrics to Datadog, and post results to Teams.
      inputParameters:
      - name: databricks_job_id
        in: body
        type: string
        description: The Azure Databricks job ID for the training pipeline.
      - name: model_name
        in: body
        type: string
        description: The registered model name in Databricks MLflow.
      - name: experiment_name
        in: body
        type: string
        description: The MLflow experiment name.
      steps:
      - name: trigger-job
        type: call
        call: databricks.run-job
        with:
          job_id: '{{databricks_job_id}}'
      - name: log-metrics
        type: call
        call: datadog.create-event
        with:
          title: 'ML Training Started: {{model_name}}'
          text: 'Job {{databricks_job_id}} | Experiment: {{experiment_name}} | Run: {{trigger-job.run_id}}'
          alert_type: info
          tags: ml_model:{{model_name}},experiment:{{experiment_name}}
      - name: notify-team
        type: call
        call: msteams.send-message
        with:
          recipient_upn: data-science@3m.com
          text: 'ML Training Job Started: {{model_name}} | Experiment: {{experiment_name}} | Databricks Run: {{trigger-job.run_id}} | Datadog: {{log-metrics.url}}'
  consumes:
  - type: http
    namespace: databricks
    baseUri: https://adb-3m.azuredatabricks.net/api/2.1
    authentication:
      type: bearer
      token: $secrets.databricks_token
    resources:
    - name: job-runs
      path: /jobs/run-now
      operations:
      - name: run-job
        method: POST
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Extracts financial and operational data from SAP S/4HANA into Snowflake, runs compliance aggregations via Azure Data Factory, and publishes the result to a Power BI dataset for regulatory reporting.

naftiko: '0.5'
info:
  label: Regulatory Compliance Reporting Pipeline
  description: Extracts financial and operational data from SAP S/4HANA into Snowflake, runs compliance aggregations via Azure Data Factory, and publishes the result to a Power BI dataset for regulatory reporting.
  tags:
  - compliance
  - finance
  - reporting
  - sap
  - snowflake
  - azure-data-factory
  - power-bi
  - regulatory
capability:
  exposes:
  - type: mcp
    namespace: compliance-reporting
    port: 8080
    tools:
    - name: run-compliance-report
      description: 'Trigger a regulatory compliance data pipeline: extract from SAP, load to Snowflake, refresh via Azure Data Factory, and push results to Power BI.'
      inputParameters:
      - name: report_period
        in: body
        type: string
        description: The reporting period in YYYY-MM format (e.g., 2025-03).
      - name: report_type
        in: body
        type: string
        description: The regulatory report type (e.g., sox_controls, ehs_emissions, product_safety).
      - name: company_code
        in: body
        type: string
        description: The SAP company code for the reporting entity.
      steps:
      - name: extract-sap-data
        type: call
        call: sap.get-financial-posting
        with:
          company_code: '{{company_code}}'
          period: '{{report_period}}'
      - name: trigger-adf-pipeline
        type: call
        call: azure-data-factory.run-pipeline
        with:
          pipeline_name: compliance-{{report_type}}
          parameters: period={{report_period}},company={{company_code}}
      - name: refresh-powerbi-dataset
        type: call
        call: powerbi.refresh-dataset
        with:
          dataset_name: compliance-{{report_type}}-{{report_period}}
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/FAC_GL_ITEMS_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: financial-postings
      path: /A_JournalEntry
      inputParameters:
      - name: company_code
        in: query
      - name: period
        in: query
      operations:
      - name: get-financial-posting
        method: GET
  - type: http
    namespace: azure-data-factory
    baseUri: https://management.azure.com/subscriptions/{{subscription_id}}/resourceGroups/{{resource_group}}/providers/Microsoft.DataFactory/factories/{{factory_name}}
    authentication:
      type: bearer
      token: $secrets.azure_token
    resources:
    - name: pipeline-runs
      path: /pipelines/{{pipeline_name}}/createRun
      inputParameters:
      - name: pipeline_name
        in: path
      operations:
      - name: run-pipeline
        method: POST
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets/{{dataset_name}}/refreshes
      inputParameters:
      - name: dataset_name
        in: path
      operations:
      - name: refresh-dataset
        method: POST

When Datadog detects Oracle Database query latency or tablespace saturation anomalies, opens a ServiceNow DBA task and opens a Jira ticket for the database engineering team.

naftiko: '0.5'
info:
  label: Oracle Database Performance Alert
  description: When Datadog detects Oracle Database query latency or tablespace saturation anomalies, opens a ServiceNow DBA task and opens a Jira ticket for the database engineering team.
  tags:
  - database
  - oracle
  - datadog
  - servicenow
  - jira
  - performance
  - dba
capability:
  exposes:
  - type: mcp
    namespace: dba-ops
    port: 8080
    tools:
    - name: handle-db-performance-alert
      description: Given an Oracle DB performance alert from Datadog, open a ServiceNow DBA task and a Jira ticket for investigation.
      inputParameters:
      - name: db_instance
        in: body
        type: string
        description: Oracle database instance name.
      - name: alert_type
        in: body
        type: string
        description: Alert type (query_latency, tablespace_full, connection_pool, lock_wait).
      - name: metric_value
        in: body
        type: string
        description: The metric value that triggered the alert.
      - name: datadog_alert_url
        in: body
        type: string
        description: URL to the Datadog monitor event.
      steps:
      - name: create-snow-task
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Oracle DB Alert: {{alert_type}} on {{db_instance}}'
          description: 'Metric: {{metric_value}} | Alert: {{datadog_alert_url}}'
          category: database_performance
          assigned_group: DBA_Team
      - name: create-jira-ticket
        type: call
        call: jira.create-issue
        with:
          project_key: DBA
          issuetype: Task
          summary: 'Oracle DB: {{alert_type}} on {{db_instance}} ({{metric_value}})'
          description: 'ServiceNow: {{create-snow-task.number}}

            Datadog: {{datadog_alert_url}}

            Instance: {{db_instance}}

            Alert: {{alert_type}}

            Value: {{metric_value}}'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/task
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST

Queries Oracle E-Business Suite general ledger for account balances by period, returning beginning balance, net activity, and ending balance for finance teams.

naftiko: '0.5'
info:
  label: Oracle GL Balance Lookup
  description: Queries Oracle E-Business Suite general ledger for account balances by period, returning beginning balance, net activity, and ending balance for finance teams.
  tags:
  - finance
  - oracle
  - general-ledger
  - accounting
capability:
  exposes:
  - type: mcp
    namespace: finance
    port: 8080
    tools:
    - name: get-gl-balance
      description: Look up Oracle general ledger balance by account and period. Returns beginning balance, debits, credits, and ending balance.
      inputParameters:
      - name: account_code
        in: body
        type: string
        description: The GL account code combination.
      - name: period_name
        in: body
        type: string
        description: The accounting period (e.g., JAN-26).
      call: oracle-ebs.get-gl-balance
      with:
        account_code: '{{account_code}}'
        period_name: '{{period_name}}'
      outputParameters:
      - name: beginning_balance
        type: string
        mapping: $.BeginningBalance
      - name: net_activity
        type: string
        mapping: $.NetActivity
      - name: ending_balance
        type: string
        mapping: $.EndingBalance
  consumes:
  - type: http
    namespace: oracle-ebs
    baseUri: https://3m-ebs.oracle.com/fscmRestApi/resources/v1
    authentication:
      type: basic
      username: $secrets.oracle_ebs_user
      password: $secrets.oracle_ebs_password
    resources:
    - name: gl-balances
      path: /glBalances
      inputParameters:
      - name: account_code
        in: query
      - name: period_name
        in: query
      operations:
      - name: get-gl-balance
        method: GET

When a SonarQube quality gate fails on a pull request, posts a quality report comment to the GitHub PR, opens a Jira engineering task, and notifies the team in Teams.

naftiko: '0.5'
info:
  label: SonarQube Code Quality Gate Failure
  description: When a SonarQube quality gate fails on a pull request, posts a quality report comment to the GitHub PR, opens a Jira engineering task, and notifies the team in Teams.
  tags:
  - code-quality
  - sonarqube
  - github
  - jira
  - microsoft-teams
  - devsecops
capability:
  exposes:
  - type: mcp
    namespace: code-quality
    port: 8080
    tools:
    - name: handle-quality-gate-failure
      description: Given a SonarQube project and GitHub PR number, post the quality report as a PR comment, open a Jira task, and alert the team in Teams.
      inputParameters:
      - name: sonarqube_project_key
        in: body
        type: string
        description: The SonarQube project key.
      - name: github_repo
        in: body
        type: string
        description: GitHub repository in owner/repo format.
      - name: pr_number
        in: body
        type: string
        description: The GitHub pull request number.
      - name: failed_conditions
        in: body
        type: string
        description: Description of the failed gate conditions.
      steps:
      - name: get-sonar-report
        type: call
        call: sonarqube-cq.get-project-status
        with:
          project_key: '{{sonarqube_project_key}}'
      - name: post-pr-comment
        type: call
        call: github-cq.create-pr-comment
        with:
          repository: '{{github_repo}}'
          pr_number: '{{pr_number}}'
          body: 'SonarQube Quality Gate FAILED


            Conditions: {{failed_conditions}}

            Bugs: {{get-sonar-report.bugs}} | Vulnerabilities: {{get-sonar-report.vulnerabilities}} | Coverage: {{get-sonar-report.coverage}}%'
      - name: open-jira
        type: call
        call: jira-cq.create-issue
        with:
          project_key: ENG
          issuetype: Task
          summary: 'Quality gate failure: {{sonarqube_project_key}} PR #{{pr_number}}'
          description: 'Failed: {{failed_conditions}}

            Bugs: {{get-sonar-report.bugs}}

            Vulnerabilities: {{get-sonar-report.vulnerabilities}}

            Coverage: {{get-sonar-report.coverage}}%'
  consumes:
  - type: http
    namespace: sonarqube-cq
    baseUri: https://3m-sonar.internal/api
    authentication:
      type: bearer
      token: $secrets.sonarqube_token
    resources:
    - name: project-status
      path: /qualitygates/project_status
      inputParameters:
      - name: project_key
        in: query
      operations:
      - name: get-project-status
        method: GET
  - type: http
    namespace: github-cq
    baseUri: https://api.github.com
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: pr-comments
      path: /repos/{{repository}}/issues/{{pr_number}}/comments
      inputParameters:
      - name: repository
        in: path
      - name: pr_number
        in: path
      operations:
      - name: create-pr-comment
        method: POST
  - type: http
    namespace: jira-cq
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST

On new hire creation in Workday, opens a ServiceNow onboarding ticket, provisions a SharePoint folder, and sends a Microsoft Teams welcome message to the new employee.

naftiko: '0.5'
info:
  label: Employee Onboarding Orchestrator
  description: On new hire creation in Workday, opens a ServiceNow onboarding ticket, provisions a SharePoint folder, and sends a Microsoft Teams welcome message to the new employee.
  tags:
  - hr
  - onboarding
  - workday
  - servicenow
  - sharepoint
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: hr-onboarding
    port: 8080
    tools:
    - name: trigger-onboarding
      description: Given a Workday employee ID and start date, orchestrate the full onboarding sequence across ServiceNow, SharePoint, and Microsoft Teams.
      inputParameters:
      - name: workday_employee_id
        in: body
        type: string
        description: The Workday worker ID for the new hire.
      - name: start_date
        in: body
        type: string
        description: The employee start date in YYYY-MM-DD format.
      - name: department
        in: body
        type: string
        description: The department or business unit the new hire is joining.
      steps:
      - name: get-employee
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{workday_employee_id}}'
      - name: open-ticket
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'New hire onboarding: {{get-employee.full_name}}'
          category: hr_onboarding
          assigned_group: IT_Onboarding
          description: Onboarding for {{get-employee.full_name}} starting {{start_date}} in {{department}}.
      - name: provision-folder
        type: call
        call: sharepoint.create-folder
        with:
          site_id: hr_onboarding_site
          folder_path: OnboardingDocs/{{get-employee.full_name}}_{{start_date}}
      - name: send-welcome
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{get-employee.work_email}}'
          text: Welcome to 3M, {{get-employee.first_name}}! Your IT onboarding ticket is {{open-ticket.number}}. Documents are ready at {{provision-folder.url}}.
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: drive-items
      path: /{{site_id}}/drive/root:/{{folder_path}}
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      operations:
      - name: create-folder
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

When an environmental health and safety incident is reported, creates a ServiceNow EHS case, logs the event in SAP Plant Maintenance, and notifies the site safety officer and EHS leadership in Microsoft Teams.

naftiko: '0.5'
info:
  label: EHS Safety Incident Reporting
  description: When an environmental health and safety incident is reported, creates a ServiceNow EHS case, logs the event in SAP Plant Maintenance, and notifies the site safety officer and EHS leadership in Microsoft Teams.
  tags:
  - ehs
  - safety
  - servicenow
  - sap
  - microsoft-teams
  - compliance
  - manufacturing
capability:
  exposes:
  - type: mcp
    namespace: ehs
    port: 8080
    tools:
    - name: report-safety-incident
      description: Given an EHS incident description and plant code, open a ServiceNow EHS case, log in SAP PM, and notify the site safety officer in Teams.
      inputParameters:
      - name: incident_description
        in: body
        type: string
        description: Description of the safety or environmental incident.
      - name: plant_code
        in: body
        type: string
        description: 3M plant or facility code where the incident occurred.
      - name: severity
        in: body
        type: string
        description: 'Incident severity: near_miss, first_aid, recordable, or lost_time.'
      - name: safety_officer_upn
        in: body
        type: string
        description: Microsoft UPN of the site safety officer.
      steps:
      - name: create-ehs-case
        type: call
        call: servicenow.create-ehs-case
        with:
          short_description: 'EHS Incident ({{severity}}): {{plant_code}}'
          description: '{{incident_description}}'
          category: safety_incident
          severity: '{{severity}}'
          location: '{{plant_code}}'
      - name: log-sap-notification
        type: call
        call: sap.create-pm-notification
        with:
          plant: '{{plant_code}}'
          notification_type: S2
          short_text: 'EHS: {{severity}} at {{plant_code}}'
          long_text: '{{incident_description}} | ServiceNow: {{create-ehs-case.number}}'
      - name: notify-safety-officer
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{safety_officer_upn}}'
          text: 'EHS Incident Reported: {{severity}} at {{plant_code}} | ServiceNow: {{create-ehs-case.number}} | SAP Notification: {{log-sap-notification.notification_id}} | Details: {{incident_description}}'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: ehs-cases
      path: /table/sn_ehs_case
      operations:
      - name: create-ehs-case
        method: POST
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/PM_NOTIFICATION_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: notifications
      path: /MaintenanceNotification
      operations:
      - name: create-pm-notification
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Automates production shift handover by collecting output data from SAP, summarizing open issues from ServiceNow, and posting a shift report to the plant operations Teams channel.

naftiko: '0.5'
info:
  label: Production Shift Handover
  description: Automates production shift handover by collecting output data from SAP, summarizing open issues from ServiceNow, and posting a shift report to the plant operations Teams channel.
  tags:
  - manufacturing
  - production
  - sap
  - servicenow
  - microsoft-teams
  - operations
capability:
  exposes:
  - type: mcp
    namespace: shift-management
    port: 8080
    tools:
    - name: generate-shift-handover
      description: Given a plant, line, and shift period, collect production data, open issues, and post handover report.
      inputParameters:
      - name: plant_code
        in: body
        type: string
        description: The 3M plant code.
      - name: production_line
        in: body
        type: string
        description: Production line identifier.
      - name: shift
        in: body
        type: string
        description: Shift identifier (e.g., day, swing, night).
      steps:
      - name: get-production-output
        type: call
        call: sap.get-shift-output
        with:
          plant: '{{plant_code}}'
          line: '{{production_line}}'
          shift: '{{shift}}'
      - name: get-open-issues
        type: call
        call: servicenow.get-open-incidents
        with:
          location: '{{plant_code}}'
          equipment: '{{production_line}}'
      - name: post-handover
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.plant_ops_team_id
          channel_id: $secrets.plant_ops_channel_id
          text: 'Shift Handover: {{production_line}} at {{plant_code}} ({{shift}}) | Output: {{get-production-output.total_qty}} units | Scrap: {{get-production-output.scrap_qty}} | Open Issues: {{get-open-issues.count}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/PP_SHIFT_REPORT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: shift-output
      path: /ShiftReport
      inputParameters:
      - name: plant
        in: query
      - name: line
        in: query
      - name: shift
        in: query
      operations:
      - name: get-shift-output
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      inputParameters:
      - name: location
        in: query
      - name: equipment
        in: query
      operations:
      - name: get-open-incidents
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Retrieves a quality inspection lot from SAP QM by lot number, returning inspection results, usage decision, and defect counts for quality assurance teams.

naftiko: '0.5'
info:
  label: SAP Quality Inspection Lot Lookup
  description: Retrieves a quality inspection lot from SAP QM by lot number, returning inspection results, usage decision, and defect counts for quality assurance teams.
  tags:
  - quality
  - sap
  - sap-s4hana
  - inspection
  - manufacturing
  - quality-control
capability:
  exposes:
  - type: mcp
    namespace: quality-inspection
    port: 8080
    tools:
    - name: get-inspection-lot
      description: Look up a SAP quality inspection lot by number. Returns usage decision, inspection result, and defect count.
      inputParameters:
      - name: lot_number
        in: body
        type: string
        description: The SAP inspection lot number.
      call: sap.get-inspection-lot
      with:
        lot_number: '{{lot_number}}'
      outputParameters:
      - name: usage_decision
        type: string
        mapping: $.d.UsageDecision
      - name: inspection_result
        type: string
        mapping: $.d.InspectionResult
      - name: defect_count
        type: string
        mapping: $.d.NumberOfDefects
      - name: material
        type: string
        mapping: $.d.Material
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/QM_INSPECTION_LOT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: inspection-lots
      path: /InspectionLot('{{lot_number}}')
      inputParameters:
      - name: lot_number
        in: path
      operations:
      - name: get-inspection-lot
        method: GET
        outputRawFormat: json

When a Tableau workbook extract refresh fails, logs the failure to Datadog, opens a Jira ticket for the BI team, and notifies the dashboard owner in Microsoft Teams.

naftiko: '0.5'
info:
  label: Tableau Dashboard Refresh Failure
  description: When a Tableau workbook extract refresh fails, logs the failure to Datadog, opens a Jira ticket for the BI team, and notifies the dashboard owner in Microsoft Teams.
  tags:
  - analytics
  - tableau
  - datadog
  - jira
  - microsoft-teams
  - business-intelligence
capability:
  exposes:
  - type: mcp
    namespace: bi-ops
    port: 8080
    tools:
    - name: handle-tableau-refresh-failure
      description: Given a failed Tableau workbook name and owner, log to Datadog, open a Jira BI ticket, and notify the owner in Teams.
      inputParameters:
      - name: workbook_name
        in: body
        type: string
        description: The Tableau workbook name.
      - name: workbook_id
        in: body
        type: string
        description: The Tableau workbook ID.
      - name: owner_upn
        in: body
        type: string
        description: Microsoft UPN of the workbook owner.
      - name: error_message
        in: body
        type: string
        description: Extract refresh error message.
      steps:
      - name: log-datadog
        type: call
        call: datadog-bi.create-event
        with:
          title: 'Tableau Refresh Failed: {{workbook_name}}'
          text: 'Workbook: {{workbook_id}} | Error: {{error_message}} | Owner: {{owner_upn}}'
          alert_type: error
          tags: bi:tableau,workbook:{{workbook_name}}
      - name: open-jira
        type: call
        call: jira-bi.create-issue
        with:
          project_key: BI
          issuetype: Bug
          summary: 'Tableau refresh failure: {{workbook_name}}'
          description: 'Workbook: {{workbook_name}} ({{workbook_id}})

            Owner: {{owner_upn}}

            Error: {{error_message}}

            Datadog: {{log-datadog.url}}'
      - name: notify-owner
        type: call
        call: msteams-bi.send-message
        with:
          recipient_upn: '{{owner_upn}}'
          text: 'Tableau Refresh Failed: {{workbook_name}} | Error: {{error_message}} | Jira: {{open-jira.key}}'
  consumes:
  - type: http
    namespace: datadog-bi
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: jira-bi
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams-bi
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Orchestrates a new product regulatory submission by gathering product specs from SAP, creating a Jira submission tracker, uploading documents to SharePoint, and notifying the regulatory affairs team.

naftiko: '0.5'
info:
  label: New Product Regulatory Submission
  description: Orchestrates a new product regulatory submission by gathering product specs from SAP, creating a Jira submission tracker, uploading documents to SharePoint, and notifying the regulatory affairs team.
  tags:
  - regulatory
  - compliance
  - sap
  - jira
  - sharepoint
  - product-development
capability:
  exposes:
  - type: mcp
    namespace: regulatory-submissions
    port: 8080
    tools:
    - name: submit-regulatory-package
      description: Given a product material number, submission type, and target market, gather specs, create a tracker, upload docs, and notify the regulatory team.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number for the new product.
      - name: submission_type
        in: body
        type: string
        description: Type of regulatory submission (e.g., 510k, CE_mark, REACH).
      - name: target_market
        in: body
        type: string
        description: Target market for the submission (e.g., US, EU, APAC).
      steps:
      - name: get-product-specs
        type: call
        call: sap.get-material-master
        with:
          material_number: '{{material_number}}'
      - name: create-submission-tracker
        type: call
        call: jira.create-issue
        with:
          project_key: REG
          issuetype: Task
          summary: 'Regulatory Submission: {{submission_type}} — {{material_number}} ({{target_market}})'
          description: 'Product: {{get-product-specs.material_description}} | Type: {{submission_type}} | Market: {{target_market}}'
      - name: create-sharepoint-folder
        type: call
        call: sharepoint.create-folder
        with:
          site_id: $secrets.regulatory_site_id
          parent_path: /Submissions/{{submission_type}}
          folder_name: '{{material_number}}-{{target_market}}'
      - name: notify-regulatory-team
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.regulatory_team_id
          channel_id: $secrets.regulatory_channel_id
          text: 'New Regulatory Submission: {{submission_type}} for {{material_number}} ({{target_market}}) | Jira: {{create-submission-tracker.key}} | SharePoint folder created'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/API_PRODUCT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: materials
      path: /A_Product('{{material_number}}')
      inputParameters:
      - name: material_number
        in: path
      operations:
      - name: get-material-master
        method: GET
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: folders
      path: /{{site_id}}/drive/root:{{parent_path}}/{{folder_name}}
      inputParameters:
      - name: site_id
        in: path
      - name: parent_path
        in: path
      - name: folder_name
        in: path
      operations:
      - name: create-folder
        method: PUT
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Assigns mandatory safety training in Workday Learning, creates a tracking record in ServiceNow, and sends a completion deadline reminder to the employee and their manager in Teams.

naftiko: '0.5'
info:
  label: Safety Training Assignment
  description: Assigns mandatory safety training in Workday Learning, creates a tracking record in ServiceNow, and sends a completion deadline reminder to the employee and their manager in Teams.
  tags:
  - safety
  - training
  - workday
  - servicenow
  - microsoft-teams
  - compliance
capability:
  exposes:
  - type: mcp
    namespace: safety-training
    port: 8080
    tools:
    - name: assign-safety-training
      description: Given an employee ID, training course, and deadline, assign in Workday, track in ServiceNow, and notify via Teams.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The Workday employee ID.
      - name: course_id
        in: body
        type: string
        description: The Workday Learning course ID.
      - name: deadline
        in: body
        type: string
        description: Completion deadline date.
      - name: employee_upn
        in: body
        type: string
        description: Microsoft UPN of the employee.
      steps:
      - name: assign-course
        type: call
        call: workday.assign-learning
        with:
          employee_id: '{{employee_id}}'
          course_id: '{{course_id}}'
          due_date: '{{deadline}}'
      - name: create-tracking-record
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Safety training due: {{course_id}} for {{employee_id}}'
          assigned_to: '{{employee_upn}}'
          due_date: '{{deadline}}'
          category: safety_training
      - name: notify-employee
        type: call
        call: msteams.send-chat
        with:
          recipient_upn: '{{employee_upn}}'
          text: 'You have been assigned mandatory safety training: {{course_id}}. Please complete by {{deadline}}. ServiceNow: {{create-tracking-record.number}}'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd5-impl-services1.workday.com/ccx/api/v1/3m
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: learning
      path: /learningAssignments
      operations:
      - name: assign-learning
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/sc_task
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: chats
      path: /users/{{recipient_upn}}/chats
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-chat
        method: POST

Manages environmental permit renewals by pulling permit data from ServiceNow, creating renewal tasks in Jira, and notifying the EHS director and regulatory team in Teams.

naftiko: '0.5'
info:
  label: Environmental Permit Renewal
  description: Manages environmental permit renewals by pulling permit data from ServiceNow, creating renewal tasks in Jira, and notifying the EHS director and regulatory team in Teams.
  tags:
  - ehs
  - compliance
  - regulatory
  - servicenow
  - jira
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: ehs-permits
    port: 8080
    tools:
    - name: initiate-permit-renewal
      description: Given a permit ID and plant code, pull permit data, create renewal tasks, and notify stakeholders.
      inputParameters:
      - name: permit_id
        in: body
        type: string
        description: The ServiceNow environmental permit record ID.
      - name: plant_code
        in: body
        type: string
        description: The 3M plant code.
      - name: permit_type
        in: body
        type: string
        description: Type of permit (e.g., air_emissions, water_discharge, waste_handling).
      - name: expiry_date
        in: body
        type: string
        description: Current permit expiry date.
      steps:
      - name: get-permit-details
        type: call
        call: servicenow.get-permit
        with:
          permit_id: '{{permit_id}}'
      - name: create-renewal-tasks
        type: call
        call: jira.create-issue
        with:
          project_key: EHS
          issuetype: Epic
          summary: 'Permit Renewal: {{permit_type}} — {{plant_code}} (expires {{expiry_date}})'
          description: 'Permit: {{permit_id}} | Type: {{permit_type}} | Plant: {{plant_code}} | Current expiry: {{expiry_date}} | Authority: {{get-permit-details.issuing_authority}}'
      - name: notify-ehs-leadership
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.ehs_team_id
          channel_id: $secrets.ehs_permits_channel_id
          text: 'Permit Renewal Required: {{permit_type}} at {{plant_code}} | Expires: {{expiry_date}} | Jira: {{create-renewal-tasks.key}}'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: permits
      path: /table/sn_ehs_permit/{{permit_id}}
      inputParameters:
      - name: permit_id
        in: path
      operations:
      - name: get-permit
        method: GET
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

Retrieves a Jira issue by key, returning summary, status, assignee, and priority for engineering and project management teams.

naftiko: '0.5'
info:
  label: Jira Ticket Lookup
  description: Retrieves a Jira issue by key, returning summary, status, assignee, and priority for engineering and project management teams.
  tags:
  - engineering
  - jira
  - project-management
  - development
capability:
  exposes:
  - type: mcp
    namespace: engineering
    port: 8080
    tools:
    - name: get-jira-issue
      description: Look up a Jira issue by key. Returns summary, status, assignee, priority, and sprint.
      inputParameters:
      - name: issue_key
        in: body
        type: string
        description: The Jira issue key (e.g., PROJ-1234).
      call: jira.get-issue
      with:
        issue_key: '{{issue_key}}'
      outputParameters:
      - name: summary
        type: string
        mapping: $.fields.summary
      - name: status
        type: string
        mapping: $.fields.status.name
      - name: assignee
        type: string
        mapping: $.fields.assignee.displayName
      - name: priority
        type: string
        mapping: $.fields.priority.name
  consumes:
  - type: http
    namespace: jira
    baseUri: https://3m.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_token
    resources:
    - name: issues
      path: /issue/{{issue_key}}
      inputParameters:
      - name: issue_key
        in: path
      operations:
      - name: get-issue
        method: GET

Checks the last refresh status and timing of a Power BI dataset to verify data freshness for reporting and analytics teams.

naftiko: '0.5'
info:
  label: Power BI Dataset Refresh Status
  description: Checks the last refresh status and timing of a Power BI dataset to verify data freshness for reporting and analytics teams.
  tags:
  - analytics
  - power-bi
  - reporting
  - data-quality
capability:
  exposes:
  - type: mcp
    namespace: analytics
    port: 8080
    tools:
    - name: get-dataset-refresh-status
      description: Check the last refresh status of a Power BI dataset. Returns status, start and end times, and error message if failed.
      inputParameters:
      - name: group_id
        in: body
        type: string
        description: The Power BI workspace (group) ID.
      - name: dataset_id
        in: body
        type: string
        description: The Power BI dataset ID.
      call: powerbi.get-refresh-history
      with:
        group_id: '{{group_id}}'
        dataset_id: '{{dataset_id}}'
      outputParameters:
      - name: status
        type: string
        mapping: $.value[0].status
      - name: start_time
        type: string
        mapping: $.value[0].startTime
      - name: end_time
        type: string
        mapping: $.value[0].endTime
  consumes:
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: refresh-history
      path: /groups/{{group_id}}/datasets/{{dataset_id}}/refreshes
      inputParameters:
      - name: group_id
        in: path
      - name: dataset_id
        in: path
      operations:
      - name: get-refresh-history
        method: GET

Assembles a weekly executive briefing by pulling sales pipeline from Salesforce, financial KPIs from Power BI, and operational metrics from Snowflake, then publishes the digest to a SharePoint executive portal and Teams channel.

naftiko: '0.5'
info:
  label: Executive Briefing Digest
  description: Assembles a weekly executive briefing by pulling sales pipeline from Salesforce, financial KPIs from Power BI, and operational metrics from Snowflake, then publishes the digest to a SharePoint executive portal and Teams channel.
  tags:
  - executive
  - reporting
  - salesforce
  - power-bi
  - snowflake
  - sharepoint
  - microsoft-teams
  - digest
capability:
  exposes:
  - type: mcp
    namespace: executive-reporting
    port: 8080
    tools:
    - name: publish-executive-briefing
      description: Pull pipeline from Salesforce, KPIs from Power BI, and ops metrics from Snowflake, then publish the digest to SharePoint and notify leadership in Teams.
      inputParameters:
      - name: week_ending
        in: body
        type: string
        description: Week ending date in YYYY-MM-DD format.
      - name: sharepoint_site_id
        in: body
        type: string
        description: SharePoint executive portal site ID.
      - name: leadership_channel_upn
        in: body
        type: string
        description: Microsoft Teams channel or distribution UPN for leadership.
      steps:
      - name: get-pipeline
        type: call
        call: salesforce.get-pipeline-summary
        with:
          week_ending: '{{week_ending}}'
      - name: get-financial-kpis
        type: call
        call: powerbi.get-dataset-rows
        with:
          dataset_name: executive-kpis
          filter: week_ending eq '{{week_ending}}'
      - name: publish-to-sharepoint
        type: call
        call: sharepoint.create-file
        with:
          site_id: '{{sharepoint_site_id}}'
          file_path: ExecutiveBriefings/briefing-{{week_ending}}.md
          content: '# 3M Executive Briefing — {{week_ending}}


            ## Pipeline

            {{get-pipeline.summary}}


            ## Financial KPIs

            {{get-financial-kpis.summary}}'
      - name: notify-leadership
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{leadership_channel_upn}}'
          text: 'Executive Briefing Published (week of {{week_ending}}): Pipeline: {{get-pipeline.total_value}} | SharePoint: {{publish-to-sharepoint.url}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://3m.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: pipeline
      path: /query
      inputParameters:
      - name: week_ending
        in: query
      operations:
      - name: get-pipeline-summary
        method: GET
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: dataset-rows
      path: /datasets/{{dataset_name}}/tables/KPIs/rows
      inputParameters:
      - name: dataset_name
        in: path
      - name: filter
        in: query
      operations:
      - name: get-dataset-rows
        method: GET
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /{{site_id}}/drive/root:/{{file_path}}:/content
      inputParameters:
      - name: site_id
        in: path
      - name: file_path
        in: path
      operations:
      - name: create-file
        method: PUT
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Promotes a SAP transport request through the landscape by triggering the release in SAP, logging the change in ServiceNow, and notifying the SAP Basis team in Teams.

naftiko: '0.5'
info:
  label: SAP Transport Request Promotion
  description: Promotes a SAP transport request through the landscape by triggering the release in SAP, logging the change in ServiceNow, and notifying the SAP Basis team in Teams.
  tags:
  - sap
  - sap-s4hana
  - servicenow
  - microsoft-teams
  - change-management
  - development
capability:
  exposes:
  - type: mcp
    namespace: sap-transport
    port: 8080
    tools:
    - name: promote-transport
      description: Given a transport number and target system, release the transport, log in ServiceNow, and notify SAP Basis.
      inputParameters:
      - name: transport_number
        in: body
        type: string
        description: The SAP transport request number.
      - name: target_system
        in: body
        type: string
        description: Target system (e.g., QAS, PRD).
      - name: change_ticket
        in: body
        type: string
        description: ServiceNow change ticket number.
      steps:
      - name: release-transport
        type: call
        call: sap.release-transport
        with:
          transport: '{{transport_number}}'
          target: '{{target_system}}'
      - name: update-change-ticket
        type: call
        call: servicenow.update-change
        with:
          change_number: '{{change_ticket}}'
          work_notes: 'Transport {{transport_number}} released to {{target_system}}. Status: {{release-transport.status}}'
      - name: notify-basis
        type: call
        call: msteams.post-channel-message
        with:
          team_id: $secrets.sap_basis_team_id
          channel_id: $secrets.sap_basis_channel_id
          text: 'Transport {{transport_number}} released to {{target_system}} | Change: {{change_ticket}} | Status: {{release-transport.status}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/CTS_TRANSPORT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: transports
      path: /Transport('{{transport}}')/Release
      inputParameters:
      - name: transport
        in: path
      operations:
      - name: release-transport
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: changes
      path: /table/change_request/{{change_number}}
      inputParameters:
      - name: change_number
        in: path
      operations:
      - name: update-change
        method: PATCH
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: team_id
        in: path
      - name: channel_id
        in: path
      operations:
      - name: post-channel-message
        method: POST

When a manufacturing asset health monitor signals degradation, creates a ServiceNow maintenance work order, cross-references the SAP Plant Maintenance module for asset details, and notifies the facility team in Microsoft Teams.

naftiko: '0.5'
info:
  label: Equipment Maintenance Request
  description: When a manufacturing asset health monitor signals degradation, creates a ServiceNow maintenance work order, cross-references the SAP Plant Maintenance module for asset details, and notifies the facility team in Microsoft Teams.
  tags:
  - manufacturing
  - maintenance
  - servicenow
  - sap
  - microsoft-teams
  - asset-management
  - industrial
capability:
  exposes:
  - type: mcp
    namespace: plant-operations
    port: 8080
    tools:
    - name: create-maintenance-request
      description: Given an equipment ID and failure signal, fetch asset details from SAP Plant Maintenance, open a ServiceNow work order, and notify the facility team in Microsoft Teams.
      inputParameters:
      - name: equipment_id
        in: body
        type: string
        description: The SAP Plant Maintenance equipment number.
      - name: failure_signal
        in: body
        type: string
        description: Description of the observed equipment fault or degradation signal.
      - name: plant_code
        in: body
        type: string
        description: The 3M manufacturing plant code where the equipment is located.
      - name: priority
        in: body
        type: string
        description: Maintenance priority (1=Emergency, 2=Urgent, 3=Normal, 4=Low).
      steps:
      - name: get-asset-details
        type: call
        call: sap.get-equipment
        with:
          equipment_id: '{{equipment_id}}'
          plant: '{{plant_code}}'
      - name: create-work-order
        type: call
        call: servicenow.create-work-order
        with:
          short_description: 'Maintenance Request: {{get-asset-details.equipment_description}} — {{failure_signal}}'
          category: plant_maintenance
          asset_tag: '{{equipment_id}}'
          location: '{{plant_code}}'
          priority: '{{priority}}'
          description: 'Equipment: {{get-asset-details.equipment_description}}

            Plant: {{plant_code}}

            Fault: {{failure_signal}}

            Last PM: {{get-asset-details.last_pm_date}}'
      - name: notify-facility
        type: call
        call: msteams.send-message
        with:
          recipient_upn: plant-{{plant_code}}-ops@3m.com
          text: 'Maintenance Request: {{get-asset-details.equipment_description}} ({{equipment_id}}) | Plant: {{plant_code}} | Priority: {{priority}} | Signal: {{failure_signal}} | Work Order: {{create-work-order.number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/PM_EQUIPMENT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: equipment
      path: /Equipment('{{equipment_id}}')
      inputParameters:
      - name: equipment_id
        in: path
      operations:
      - name: get-equipment
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: work-orders
      path: /table/wm_order
      operations:
      - name: create-work-order
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves a Confluence page by ID, returning title, content body, last modified date, and author for knowledge management and documentation teams.

naftiko: '0.5'
info:
  label: Confluence Page Lookup
  description: Retrieves a Confluence page by ID, returning title, content body, last modified date, and author for knowledge management and documentation teams.
  tags:
  - knowledge-management
  - confluence
  - documentation
  - collaboration
capability:
  exposes:
  - type: mcp
    namespace: knowledge
    port: 8080
    tools:
    - name: get-confluence-page
      description: Look up a Confluence page by page ID. Returns title, body content, last modifier, and version.
      inputParameters:
      - name: page_id
        in: body
        type: string
        description: The Confluence page ID.
      call: confluence.get-page
      with:
        page_id: '{{page_id}}'
      outputParameters:
      - name: title
        type: string
        mapping: $.title
      - name: body
        type: string
        mapping: $.body.storage.value
      - name: last_modified
        type: string
        mapping: $.version.when
      - name: author
        type: string
        mapping: $.version.by.displayName
  consumes:
  - type: http
    namespace: confluence
    baseUri: https://3m.atlassian.net/wiki/rest/api
    authentication:
      type: basic
      username: $secrets.confluence_user
      password: $secrets.confluence_token
    resources:
    - name: pages
      path: /content/{{page_id}}
      inputParameters:
      - name: page_id
        in: path
      operations:
      - name: get-page
        method: GET

Coordinates a 3M product launch by publishing brand assets from Adobe Creative Cloud to SharePoint, scheduling the HubSpot email campaign, and posting launch readiness to the marketing Microsoft Teams channel.

naftiko: '0.5'
info:
  label: Product Launch Content Pipeline
  description: Coordinates a 3M product launch by publishing brand assets from Adobe Creative Cloud to SharePoint, scheduling the HubSpot email campaign, and posting launch readiness to the marketing Microsoft Teams channel.
  tags:
  - marketing
  - product-launch
  - adobe-creative-cloud
  - sharepoint
  - hubspot
  - microsoft-teams
  - content
capability:
  exposes:
  - type: mcp
    namespace: product-launch
    port: 8080
    tools:
    - name: execute-launch-content-pipeline
      description: Given a product name and HubSpot campaign ID, publish approved brand assets to SharePoint, activate the HubSpot email campaign, and notify the marketing team in Teams.
      inputParameters:
      - name: product_name
        in: body
        type: string
        description: The product name being launched.
      - name: hubspot_campaign_id
        in: body
        type: string
        description: The HubSpot email campaign ID to activate.
      - name: sharepoint_library_id
        in: body
        type: string
        description: SharePoint document library ID for brand assets.
      - name: launch_date
        in: body
        type: string
        description: Planned launch date in YYYY-MM-DD format.
      steps:
      - name: publish-assets
        type: call
        call: sharepoint.create-folder
        with:
          site_id: marketing_assets_site
          folder_path: ProductLaunches/{{product_name}}_{{launch_date}}
      - name: activate-campaign
        type: call
        call: hubspot.activate-campaign
        with:
          campaign_id: '{{hubspot_campaign_id}}'
      - name: notify-marketing
        type: call
        call: msteams.send-message
        with:
          recipient_upn: marketing-team@3m.com
          text: 'Launch Pipeline Complete: {{product_name}} | Launch Date: {{launch_date}} | Assets: {{publish-assets.url}} | HubSpot Campaign: {{hubspot_campaign_id}} activated.'
  consumes:
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: drive-items
      path: /{{site_id}}/drive/root:/{{folder_path}}
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      operations:
      - name: create-folder
        method: POST
  - type: http
    namespace: hubspot
    baseUri: https://api.hubapi.com/marketing/v3
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: campaigns
      path: /campaigns/{{campaign_id}}/activate
      inputParameters:
      - name: campaign_id
        in: path
      operations:
      - name: activate-campaign
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Returns current headcount by department and cost center from Workday and ADP, cross-referenced against SAP cost center hierarchy, for use in headcount planning and budget reporting.

naftiko: '0.5'
info:
  label: Headcount and Payroll Snapshot
  description: Returns current headcount by department and cost center from Workday and ADP, cross-referenced against SAP cost center hierarchy, for use in headcount planning and budget reporting.
  tags:
  - hr
  - finance
  - payroll
  - workday
  - adp
  - sap
  - headcount
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: hr-finance
    port: 8080
    tools:
    - name: get-headcount-snapshot
      description: Returns employee headcount grouped by department and cost center from Workday, enriched with ADP payroll classification data.
      call: workday.headcount-export
      outputParameters:
      - name: employees
        type: array
        mapping: $.data
        items:
        - name: employee_id
          type: string
          mapping: $.workerId
        - name: full_name
          type: string
          mapping: $.name.formattedName
        - name: department
          type: string
          mapping: $.organizationInfo.department
        - name: cost_center
          type: string
          mapping: $.organizationInfo.costCenter
        - name: employment_type
          type: string
          mapping: $.workerType
    - name: get-payroll-by-cost-center
      description: Returns ADP payroll totals grouped by SAP cost center code for a given pay period. Use for budget vs. actuals reconciliation.
      inputParameters:
      - name: pay_period_start
        in: body
        type: string
        description: Start date of the pay period in YYYY-MM-DD format.
      - name: pay_period_end
        in: body
        type: string
        description: End date of the pay period in YYYY-MM-DD format.
      call: adp.payroll-summary
      with:
        start_date: '{{pay_period_start}}'
        end_date: '{{pay_period_end}}'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /workers
      operations:
      - name: headcount-export
        method: GET
  - type: http
    namespace: adp
    baseUri: https://api.adp.com
    authentication:
      type: bearer
      token: $secrets.adp_token
    resources:
    - name: payroll
      path: /payroll/v1/payroll-output
      inputParameters:
      - name: start_date
        in: query
      - name: end_date
        in: query
      operations:
      - name: payroll-summary
        method: GET

Extracts actuals from SAP S/4HANA and budget from Oracle Hyperion, computes variance, and publishes the result to the Power BI finance dashboard and posts a summary to the finance Microsoft Teams channel.

naftiko: '0.5'
info:
  label: Budget vs Actuals Reporting
  description: Extracts actuals from SAP S/4HANA and budget from Oracle Hyperion, computes variance, and publishes the result to the Power BI finance dashboard and posts a summary to the finance Microsoft Teams channel.
  tags:
  - finance
  - budgeting
  - sap
  - oracle-hyperion
  - power-bi
  - microsoft-teams
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: finance-reporting
    port: 8080
    tools:
    - name: run-budget-vs-actuals
      description: Pull actuals from SAP and budget from Hyperion for a cost center and period, compute variance, refresh Power BI, and post a summary to Teams.
      inputParameters:
      - name: cost_center
        in: body
        type: string
        description: SAP cost center code.
      - name: fiscal_year
        in: body
        type: string
        description: Four-digit fiscal year.
      - name: fiscal_period
        in: body
        type: string
        description: Two-digit fiscal period.
      steps:
      - name: get-actuals
        type: call
        call: sap.get-cost-center-actuals
        with:
          cost_center: '{{cost_center}}'
          fiscal_year: '{{fiscal_year}}'
          fiscal_period: '{{fiscal_period}}'
      - name: get-budget
        type: call
        call: oracle-hyperion.get-budget
        with:
          cost_center: '{{cost_center}}'
          period: '{{fiscal_year}}.{{fiscal_period}}'
      - name: refresh-dashboard
        type: call
        call: powerbi.refresh-dataset
        with:
          dataset_name: budget-vs-actuals-{{cost_center}}-{{fiscal_year}}-{{fiscal_period}}
      - name: notify-finance
        type: call
        call: msteams.send-message
        with:
          recipient_upn: finance-reporting@3m.com
          text: 'Budget vs Actuals: Cost Center {{cost_center}} | Period {{fiscal_year}}.{{fiscal_period}} | Actuals: {{get-actuals.total_actual}} | Budget: {{get-budget.total_budget}} | Power BI refreshed.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://3m-s4.sap.com/sap/opu/odata/sap/FAC_CO_COSTCENTER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: cost-center-actuals
      path: /CostCenterActuals
      inputParameters:
      - name: cost_center
        in: query
      - name: fiscal_year
        in: query
      - name: fiscal_period
        in: query
      operations:
      - name: get-cost-center-actuals
        method: GET
  - type: http
    namespace: oracle-hyperion
    baseUri: https://3m-hyperion.oracle.com/HyperionPlanning/rest/v3
    authentication:
      type: basic
      username: $secrets.hyperion_user
      password: $secrets.hyperion_password
    resources:
    - name: budget-data
      path: /applications/3M_CONSOL/dataExport
      inputParameters:
      - name: cost_center
        in: query
      - name: period
        in: query
      operations:
      - name: get-budget
        method: GET
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets/{{dataset_name}}/refreshes
      inputParameters:
      - name: dataset_name
        in: path
      operations:
      - name: refresh-dataset
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

When Datadog fires a critical alert, creates a ServiceNow P1 incident, posts an alert to the Microsoft Teams on-call channel, and attaches the Datadog dashboard link for rapid triage.

naftiko: '0.5'
info:
  label: IT Incident Response
  description: When Datadog fires a critical alert, creates a ServiceNow P1 incident, posts an alert to the Microsoft Teams on-call channel, and attaches the Datadog dashboard link for rapid triage.
  tags:
  - itsm
  - observability
  - datadog
  - servicenow
  - microsoft-teams
  - incident-response
  - operations
capability:
  exposes:
  - type: mcp
    namespace: it-ops
    port: 8080
    tools:
    - name: handle-critical-alert
      description: Given a Datadog monitor alert, open a ServiceNow P1 incident and notify the on-call channel in Microsoft Teams with full context.
      inputParameters:
      - name: monitor_id
        in: body
        type: string
        description: The Datadog monitor ID that fired.
      - name: monitor_name
        in: body
        type: string
        description: Human-readable name of the firing monitor.
      - name: host
        in: body
        type: string
        description: The affected host or service.
      - name: alert_url
        in: body
        type: string
        description: URL to the Datadog monitor event.
      - name: oncall_channel
        in: body
        type: string
        description: Microsoft Teams channel ID for on-call notifications.
      steps:
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'P1 Alert: {{monitor_name}} on {{host}}'
          urgency: '1'
          impact: '1'
          category: infrastructure
          description: 'Datadog monitor {{monitor_id}} fired for {{host}}. Dashboard: {{alert_url}}'
      - name: notify-oncall
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{oncall_channel}}'
          text: 'P1 Incident Opened: {{monitor_name}} | Host: {{host}} | ServiceNow: {{create-incident.number}} | Datadog: {{alert_url}}'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://3m.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

When Prometheus alerts on high CPU, scales the Azure Kubernetes Service cluster, creates a Datadog annotation, and posts a status update to Microsoft Teams.

naftiko: '0.5'
info:
  label: Infrastructure Scaling Automation
  description: When Prometheus alerts on high CPU, scales the Azure Kubernetes Service cluster, creates a Datadog annotation, and posts a status update to Microsoft Teams.
  tags:
  - infrastructure
  - autoscaling
  - prometheus
  - azure-kubernetes-service
  - datadog
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: infra-scaling
    port: 8080
    tools:
    - name: auto-scale-cluster
      description: Given a cluster name and target node count, scale the AKS cluster, annotate Datadog, and notify the team.
      inputParameters:
      - name: cluster_name
        in: body
        type: string
        description: The AKS cluster name.
      - name: target_node_count
        in: body
        type: string
        description: Desired number of nodes.
      - name: trigger_metric
        in: body
        type: string
        description: The Prometheus metric that triggered the scaling.
      steps:
      - name: scale-cluster
        type: call
        call: aks.scale-nodepool
        with:
          cluster_name: '{{cluster_name}}'
          node_count: '{{target_node_count}}'
      - name: annotate-datadog
        type: call
        call: datadog.create-event
        with:
          title: 'AKS Auto-Scale: {{cluster_name}}'
          text: 'Scaled to {{target_node_count}} nodes. Trigger: {{trigger_metric}}'
          alert_type: info
      - name: notify-team
        type: call
        call: msteams.send-message
        with:
          channel: platform-ops
          text: 'Auto-Scale Complete: {{cluster_name}} scaled to {{target_node_count}} nodes. Trigger: {{trigger_metric}}. Datadog event: {{annotate-datadog.id}}'
  consumes:
  - type: http
    namespace: aks
    baseUri: https://management.azure.com/subscriptions/$secrets.azure_subscription_id/resourceGroups
    authentication:
      type: bearer
      token: $secrets.azure_token
    resources:
    - name: nodepools
      path: /adidas-rg/providers/Microsoft.ContainerService/managedClusters/{{cluster_name}}/agentPools/default
      inputParameters:
      - name: cluster_name
        in: path
      operations:
      - name: scale-nodepool
        method: PUT
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: bearer
      token: $secrets.datadog_api_key
    inputParameters:
    - name: DD-APPLICATION-KEY
      in: header
      value: $secrets.datadog_app_key
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

Pulls online inventory from BigCommerce and warehouse stock from SAP S/4HANA, reconciles discrepancies, and logs mismatches in ServiceNow and a Google Sheet.

naftiko: '0.5'
info:
  label: Omnichannel Inventory Reconciliation
  description: Pulls online inventory from BigCommerce and warehouse stock from SAP S/4HANA, reconciles discrepancies, and logs mismatches in ServiceNow and a Google Sheet.
  tags:
  - supply-chain
  - inventory
  - bigcommerce
  - sap-s4hana
  - servicenow
  - google-sheets
capability:
  exposes:
  - type: mcp
    namespace: inventory-reconciliation
    port: 8080
    tools:
    - name: reconcile-inventory
      description: Given a product SKU, compare online and warehouse inventory and log any discrepancies.
      inputParameters:
      - name: sku
        in: body
        type: string
        description: The product SKU to reconcile.
      - name: warehouse_plant
        in: body
        type: string
        description: The SAP plant code for the warehouse.
      steps:
      - name: get-online-stock
        type: call
        call: bigcommerce.get-product-stock
        with:
          sku: '{{sku}}'
      - name: get-warehouse-stock
        type: call
        call: sap.get-material-stock
        with:
          material: '{{sku}}'
          plant: '{{warehouse_plant}}'
      - name: log-discrepancy
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Inventory mismatch: {{sku}} — Online: {{get-online-stock.quantity}} vs WH: {{get-warehouse-stock.quantity}}'
          category: inventory
          priority: '3'
          description: 'SKU {{sku}} at plant {{warehouse_plant}}. BigCommerce: {{get-online-stock.quantity}}, SAP: {{get-warehouse-stock.quantity}}.'
      - name: log-to-sheet
        type: call
        call: gsheets.append-row
        with:
          spreadsheet_id: $secrets.inventory_reconciliation_sheet
          range: Discrepancies!A1
          values: '{{sku}},{{warehouse_plant}},{{get-online-stock.quantity}},{{get-warehouse-stock.quantity}},{{log-discrepancy.number}}'
  consumes:
  - type: http
    namespace: bigcommerce
    baseUri: https://api.bigcommerce.com/stores/adidas/v3
    authentication:
      type: bearer
      token: $secrets.bigcommerce_token
    resources:
    - name: products
      path: /catalog/products
      inputParameters:
      - name: sku
        in: query
      operations:
      - name: get-product-stock
        method: GET
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: stock
      path: /A_MatlStkInAcctMod
      operations:
      - name: get-material-stock
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: gsheets
    baseUri: https://sheets.googleapis.com/v4/spreadsheets
    authentication:
      type: bearer
      token: $secrets.google_sheets_token
    resources:
    - name: values
      path: /{{spreadsheet_id}}/values/{{range}}:append
      inputParameters:
      - name: spreadsheet_id
        in: path
      - name: range
        in: path
      operations:
      - name: append-row
        method: POST

Retrieves Jira issue status for Adidas engineering teams.

naftiko: '0.5'
info:
  label: Jira Issue Status
  description: Retrieves Jira issue status for Adidas engineering teams.
  tags:
  - devops
  - jira
  - project-management
capability:
  exposes:
  - type: mcp
    namespace: engineering
    port: 8080
    tools:
    - name: get-issue
      description: Look up Jira issue at Adidas.
      inputParameters:
      - name: issue_key
        in: body
        type: string
        description: The issue_key to look up.
      call: jira.get-issue_key
      with:
        issue_key: '{{issue_key}}'
  consumes:
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira_issue_status
        method: GET

Retrieves Confluence page content for Adidas knowledge base.

naftiko: '0.5'
info:
  label: Confluence Page Retrieval
  description: Retrieves Confluence page content for Adidas knowledge base.
  tags:
  - collaboration
  - confluence
  - documentation
capability:
  exposes:
  - type: mcp
    namespace: knowledge
    port: 8080
    tools:
    - name: get-page
      description: Get page at Adidas.
      inputParameters:
      - name: page_id
        in: body
        type: string
        description: The page_id to look up.
      call: confluence.get-page_id
      with:
        page_id: '{{page_id}}'
  consumes:
  - type: http
    namespace: confluence
    baseUri: https://adidas.atlassian.net/wiki/rest/api
    authentication:
      type: basic
      username: $secrets.confluence_user
      password: $secrets.confluence_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: confluence_page_retrieval
        method: GET

Extracts customer behavior segments from Adobe Analytics, enriches with purchase history from SAP HANA, and pushes personalized recommendations to the BigCommerce storefront.

naftiko: '0.5'
info:
  label: Personalization Engine Data Sync
  description: Extracts customer behavior segments from Adobe Analytics, enriches with purchase history from SAP HANA, and pushes personalized recommendations to the BigCommerce storefront.
  tags:
  - personalization
  - adobe-analytics
  - sap-hana
  - bigcommerce
capability:
  exposes:
  - type: mcp
    namespace: personalization
    port: 8080
    tools:
    - name: sync-personalization
      description: Given a customer segment ID, pull behavior data and purchase history, then update storefront recommendations.
      inputParameters:
      - name: segment_id
        in: body
        type: string
        description: The Adobe Analytics segment ID.
      - name: report_suite_id
        in: body
        type: string
        description: The Adobe Analytics report suite.
      steps:
      - name: get-segment-data
        type: call
        call: adobe-analytics.get-segment-users
        with:
          segment_id: '{{segment_id}}'
          report_suite_id: '{{report_suite_id}}'
      - name: get-purchase-history
        type: call
        call: sap-hana.query-purchase-history
        with:
          segment_id: '{{segment_id}}'
      - name: update-recommendations
        type: call
        call: bigcommerce.update-customer-group
        with:
          segment_id: '{{segment_id}}'
          recommended_products: '{{get-purchase-history.top_products}}'
          behavioral_tags: '{{get-segment-data.interests}}'
  consumes:
  - type: http
    namespace: adobe-analytics
    baseUri: https://analytics.adobe.io/api/adidas
    authentication:
      type: bearer
      token: $secrets.adobe_analytics_token
    inputParameters:
    - name: x-api-key
      in: header
      value: $secrets.adobe_client_id
    resources:
    - name: segments
      path: /segments/{{segment_id}}/users
      inputParameters:
      - name: segment_id
        in: path
      operations:
      - name: get-segment-users
        method: GET
  - type: http
    namespace: sap-hana
    baseUri: https://adidas-hana.sap.com/sap/hana/xs/api
    authentication:
      type: basic
      username: $secrets.sap_hana_user
      password: $secrets.sap_hana_password
    resources:
    - name: purchase-history
      path: /analytics/purchases
      operations:
      - name: query-purchase-history
        method: POST
  - type: http
    namespace: bigcommerce
    baseUri: https://api.bigcommerce.com/stores/adidas/v3
    authentication:
      type: bearer
      token: $secrets.bigcommerce_token
    resources:
    - name: customer-groups
      path: /customers/groups
      operations:
      - name: update-customer-group
        method: PUT

Checks ServiceNow incident status for Adidas IT operations.

naftiko: '0.5'
info:
  label: ServiceNow Incident Status Check
  description: Checks ServiceNow incident status for Adidas IT operations.
  tags:
  - itsm
  - servicenow
  - incident-management
capability:
  exposes:
  - type: mcp
    namespace: itsm
    port: 8080
    tools:
    - name: get-incident
      description: Look up incident at Adidas.
      inputParameters:
      - name: incident_id
        in: body
        type: string
        description: The incident_id to look up.
      call: servicenow.get-incident_id
      with:
        incident_id: '{{incident_id}}'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow_incident_status_che
        method: GET

Drafts a support article from a resolved Zendesk ticket, publishes it to Notion, and shares the link in a Microsoft Teams support channel.

naftiko: '0.5'
info:
  label: Knowledge Base Article Publisher
  description: Drafts a support article from a resolved Zendesk ticket, publishes it to Notion, and shares the link in a Microsoft Teams support channel.
  tags:
  - knowledge-management
  - zendesk
  - notion
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: knowledge-base
    port: 8080
    tools:
    - name: publish-kb-article
      description: Given a resolved Zendesk ticket ID, extract the resolution, publish to Notion, and share in Teams.
      inputParameters:
      - name: ticket_id
        in: body
        type: string
        description: The Zendesk ticket ID with the resolution to publish.
      - name: category
        in: body
        type: string
        description: The knowledge base category (e.g. shipping, returns, product-info).
      steps:
      - name: get-ticket
        type: call
        call: zendesk.get-ticket
        with:
          ticket_id: '{{ticket_id}}'
      - name: create-article
        type: call
        call: notion.create-page
        with:
          parent_id: $secrets.kb_database_id
          title: '{{get-ticket.subject}}'
          properties_category: '{{category}}'
          content: '{{get-ticket.resolution_notes}}'
      - name: share-article
        type: call
        call: msteams.send-message
        with:
          channel: customer-support
          text: 'New KB Article: {{get-ticket.subject}} | Category: {{category}} | Link: {{create-article.url}} | Source: Ticket #{{ticket_id}}'
  consumes:
  - type: http
    namespace: zendesk
    baseUri: https://adidas.zendesk.com/api/v2
    authentication:
      type: bearer
      token: $secrets.zendesk_token
    resources:
    - name: tickets
      path: /tickets/{{ticket_id}}.json
      inputParameters:
      - name: ticket_id
        in: path
      operations:
      - name: get-ticket
        method: GET
  - type: http
    namespace: notion
    baseUri: https://api.notion.com/v1
    authentication:
      type: bearer
      token: $secrets.notion_token
    inputParameters:
    - name: Notion-Version
      in: header
      value: '2022-06-28'
    resources:
    - name: pages
      path: /pages
      operations:
      - name: create-page
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

When SAP detects a supplier delay, creates a ServiceNow incident, notifies the supply chain team in Microsoft Teams, and logs a risk entry in SAP S/4HANA.

naftiko: '0.5'
info:
  label: Supply Chain Disruption Alert
  description: When SAP detects a supplier delay, creates a ServiceNow incident, notifies the supply chain team in Microsoft Teams, and logs a risk entry in SAP S/4HANA.
  tags:
  - supply-chain
  - sap-s4hana
  - servicenow
  - microsoft-teams
  - risk-management
capability:
  exposes:
  - type: mcp
    namespace: supply-chain
    port: 8080
    tools:
    - name: handle-disruption
      description: Given a supplier ID and delay details, create incident, notify the team, and log a supply chain risk.
      inputParameters:
      - name: supplier_id
        in: body
        type: string
        description: The SAP supplier business partner ID.
      - name: delay_days
        in: body
        type: string
        description: Number of days the shipment is delayed.
      - name: affected_materials
        in: body
        type: string
        description: Comma-separated list of affected material numbers.
      steps:
      - name: get-supplier
        type: call
        call: sap.get-supplier
        with:
          supplier_id: '{{supplier_id}}'
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Supply chain delay: {{get-supplier.name}} — {{delay_days}} days'
          category: supply_chain
          priority: '2'
          description: 'Supplier {{get-supplier.name}} ({{supplier_id}}) delayed by {{delay_days}} days. Affected materials: {{affected_materials}}.'
      - name: notify-team
        type: call
        call: msteams.send-message
        with:
          channel: supply-chain-alerts
          text: 'Supplier Delay Alert: {{get-supplier.name}} | Delay: {{delay_days}} days | Materials: {{affected_materials}} | Incident: {{create-incident.number}}'
      - name: log-risk
        type: call
        call: sap.create-risk-entry
        with:
          supplier_id: '{{supplier_id}}'
          risk_type: DELIVERY_DELAY
          severity: HIGH
          description: '{{delay_days}} day delay affecting materials: {{affected_materials}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/API_BUSINESS_PARTNER
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: suppliers
      path: /A_Supplier('{{supplier_id}}')
      inputParameters:
      - name: supplier_id
        in: path
      operations:
      - name: get-supplier
        method: GET
    - name: risk-entries
      path: /A_SupplierRisk
      operations:
      - name: create-risk-entry
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

Analyzes sell-through rates in Snowflake, calculates optimal markdowns, updates pricing in SAP, refreshes dashboards, and notifies merchandising.

naftiko: '0.5'
info:
  label: Seasonal Markdown Optimization
  description: Analyzes sell-through rates in Snowflake, calculates optimal markdowns, updates pricing in SAP, refreshes dashboards, and notifies merchandising.
  tags:
  - merchandising
  - snowflake
  - sap
  - powerbi
  - slack
capability:
  exposes:
  - type: mcp
    namespace: merchandising
    port: 8080
    tools:
    - name: seasonal_markdown_optimization
      description: Orchestrate seasonal markdown optimization workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-snowflake
        type: call
        call: snowflake.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-sap
        type: call
        call: sap.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-slack
        type: call
        call: slack.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-servicenow
        type: call
        call: servicenow.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST

Retrieves Datadog monitor status for Adidas infrastructure.

naftiko: '0.5'
info:
  label: Datadog Monitor Status
  description: Retrieves Datadog monitor status for Adidas infrastructure.
  tags:
  - monitoring
  - datadog
  - alerting
capability:
  exposes:
  - type: mcp
    namespace: observability
    port: 8080
    tools:
    - name: get-monitor
      description: Check monitor at Adidas.
      inputParameters:
      - name: monitor_id
        in: body
        type: string
        description: The monitor_id to look up.
      call: datadog.get-monitor_id
      with:
        monitor_id: '{{monitor_id}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apiKey
      key: $secrets.datadog_api_key
      header: DD-API-KEY
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: datadog_monitor_status
        method: GET

Retrieves experiment results from Google Optimize and Adobe Analytics, consolidates them, and posts findings to a Notion knowledge base page.

naftiko: '0.5'
info:
  label: E-Commerce A/B Test Result Collector
  description: Retrieves experiment results from Google Optimize and Adobe Analytics, consolidates them, and posts findings to a Notion knowledge base page.
  tags:
  - experimentation
  - google-optimize
  - adobe-analytics
  - notion
capability:
  exposes:
  - type: mcp
    namespace: experimentation
    port: 8080
    tools:
    - name: collect-ab-results
      description: Given an experiment ID, collect results from Google Optimize and Adobe Analytics and write the summary to Notion.
      inputParameters:
      - name: experiment_id
        in: body
        type: string
        description: The Google Optimize experiment ID.
      - name: report_suite_id
        in: body
        type: string
        description: The Adobe Analytics report suite ID.
      - name: notion_page_id
        in: body
        type: string
        description: The Notion page ID where results will be appended.
      steps:
      - name: get-optimize-results
        type: call
        call: google-optimize.get-experiment
        with:
          experiment_id: '{{experiment_id}}'
      - name: get-adobe-segment
        type: call
        call: adobe-analytics.get-segment-report
        with:
          report_suite_id: '{{report_suite_id}}'
          experiment_id: '{{experiment_id}}'
      - name: write-to-notion
        type: call
        call: notion.append-block
        with:
          page_id: '{{notion_page_id}}'
          content: 'Experiment: {{experiment_id}} | Winner: {{get-optimize-results.winner_variant}} | Lift: {{get-optimize-results.improvement_pct}}% | Revenue Impact: {{get-adobe-segment.revenue_delta}} | Confidence: {{get-optimize-results.confidence}}%'
  consumes:
  - type: http
    namespace: google-optimize
    baseUri: https://www.googleapis.com/analytics/v3/management
    authentication:
      type: bearer
      token: $secrets.google_optimize_token
    resources:
    - name: experiments
      path: /accounts/adidas/webproperties/UA-XXXXX/profiles/YYYYY/experiments/{{experiment_id}}
      inputParameters:
      - name: experiment_id
        in: path
      operations:
      - name: get-experiment
        method: GET
  - type: http
    namespace: adobe-analytics
    baseUri: https://analytics.adobe.io/api/adidas/reports
    authentication:
      type: bearer
      token: $secrets.adobe_analytics_token
    inputParameters:
    - name: x-api-key
      in: header
      value: $secrets.adobe_client_id
    resources:
    - name: reports
      path: /ranked
      operations:
      - name: get-segment-report
        method: POST
  - type: http
    namespace: notion
    baseUri: https://api.notion.com/v1
    authentication:
      type: bearer
      token: $secrets.notion_token
    inputParameters:
    - name: Notion-Version
      in: header
      value: '2022-06-28'
    resources:
    - name: blocks
      path: /blocks/{{page_id}}/children
      inputParameters:
      - name: page_id
        in: path
      operations:
      - name: append-block
        method: PATCH

Retrieves QC results from SAP, runs statistical analysis in Snowflake, flags defective batches, creates Jira tasks, and notifies quality team.

naftiko: '0.5'
info:
  label: Product Quality Inspection Pipeline
  description: Retrieves QC results from SAP, runs statistical analysis in Snowflake, flags defective batches, creates Jira tasks, and notifies quality team.
  tags:
  - quality
  - sap
  - snowflake
  - jira
  - slack
capability:
  exposes:
  - type: mcp
    namespace: quality
    port: 8080
    tools:
    - name: product_quality_inspection_pipeline
      description: Orchestrate product quality inspection pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-jira
        type: call
        call: jira.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Queries Grafana dashboard data for Adidas monitoring.

naftiko: '0.5'
info:
  label: Grafana Dashboard Query
  description: Queries Grafana dashboard data for Adidas monitoring.
  tags:
  - monitoring
  - grafana
  - dashboards
capability:
  exposes:
  - type: mcp
    namespace: monitoring
    port: 8080
    tools:
    - name: get-dashboard
      description: Query dashboard at Adidas.
      inputParameters:
      - name: dashboard_uid
        in: body
        type: string
        description: The dashboard_uid to look up.
      call: grafana.get-dashboard_uid
      with:
        dashboard_uid: '{{dashboard_uid}}'
  consumes:
  - type: http
    namespace: grafana
    baseUri: https://adidas-grafana.com/api
    authentication:
      type: bearer
      token: $secrets.grafana_api_key
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: grafana_dashboard_query
        method: GET

Validates inventory in SAP, checks marketing assets in Adobe, confirms pricing in Salesforce, updates e-commerce catalog, and notifies launch team.

naftiko: '0.5'
info:
  label: Product Launch Readiness Orchestrator
  description: Validates inventory in SAP, checks marketing assets in Adobe, confirms pricing in Salesforce, updates e-commerce catalog, and notifies launch team.
  tags:
  - product-launch
  - sap
  - salesforce
  - slack
capability:
  exposes:
  - type: mcp
    namespace: product-launch
    port: 8080
    tools:
    - name: product_launch_readiness_orchestrator
      description: Orchestrate product launch readiness orchestrator workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-salesforce
        type: call
        call: salesforce.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-slack
        type: call
        call: slack.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-servicenow
        type: call
        call: servicenow.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST

When seasonal markdowns are triggered, updates product prices in BigCommerce, adjusts SAP pricing conditions, and sends a promotional email via Adobe Campaign.

naftiko: '0.5'
info:
  label: Seasonal Markdown Execution
  description: When seasonal markdowns are triggered, updates product prices in BigCommerce, adjusts SAP pricing conditions, and sends a promotional email via Adobe Campaign.
  tags:
  - retail
  - pricing
  - bigcommerce
  - sap-s4hana
  - adobe-campaign
capability:
  exposes:
  - type: mcp
    namespace: markdown
    port: 8080
    tools:
    - name: execute-markdown
      description: Given a product category, discount percentage, and effective date, apply markdowns across all channels.
      inputParameters:
      - name: category
        in: body
        type: string
        description: Product category to markdown.
      - name: discount_pct
        in: body
        type: string
        description: Discount percentage to apply.
      - name: effective_date
        in: body
        type: string
        description: Markdown effective date in YYYY-MM-DD format.
      steps:
      - name: update-ecommerce-prices
        type: call
        call: bigcommerce.batch-update-prices
        with:
          category: '{{category}}'
          discount_pct: '{{discount_pct}}'
          effective_date: '{{effective_date}}'
      - name: update-sap-conditions
        type: call
        call: sap.update-pricing-condition
        with:
          condition_type: ZK07
          category: '{{category}}'
          discount_pct: '{{discount_pct}}'
          valid_from: '{{effective_date}}'
      - name: send-promo-email
        type: call
        call: adobe-campaign.create-delivery
        with:
          template: seasonal_markdown_v1
          category: '{{category}}'
          discount_pct: '{{discount_pct}}'
          scheduled_date: '{{effective_date}}'
  consumes:
  - type: http
    namespace: bigcommerce
    baseUri: https://api.bigcommerce.com/stores/adidas/v3
    authentication:
      type: bearer
      token: $secrets.bigcommerce_token
    resources:
    - name: products
      path: /catalog/products
      operations:
      - name: batch-update-prices
        method: PUT
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/API_SLSPRICINGCONDITIONRECORD_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: conditions
      path: /A_SlsPrcgCndnRecdValidity
      operations:
      - name: update-pricing-condition
        method: POST
  - type: http
    namespace: adobe-campaign
    baseUri: https://mc.adobe.io/adidas/campaign
    authentication:
      type: bearer
      token: $secrets.adobe_campaign_token
    resources:
    - name: deliveries
      path: /deliveries
      operations:
      - name: create-delivery
        method: POST

When an order is placed on BigCommerce, checks SAP inventory, creates a shipment in SAP S/4HANA, and notifies the customer via Zendesk with tracking details.

naftiko: '0.5'
info:
  label: E-Commerce Order Fulfillment Tracker
  description: When an order is placed on BigCommerce, checks SAP inventory, creates a shipment in SAP S/4HANA, and notifies the customer via Zendesk with tracking details.
  tags:
  - ecommerce
  - fulfillment
  - bigcommerce
  - sap-s4hana
  - zendesk
capability:
  exposes:
  - type: mcp
    namespace: order-fulfillment
    port: 8080
    tools:
    - name: fulfill-order
      description: Given a BigCommerce order ID and customer email, verify inventory, create a shipment, and send tracking info to the customer.
      inputParameters:
      - name: order_id
        in: body
        type: string
        description: The BigCommerce order ID.
      - name: customer_email
        in: body
        type: string
        description: The customer email address for notification.
      steps:
      - name: get-order
        type: call
        call: bigcommerce.get-order
        with:
          order_id: '{{order_id}}'
      - name: check-inventory
        type: call
        call: sap.check-availability
        with:
          sku: '{{get-order.line_items[0].sku}}'
          quantity: '{{get-order.line_items[0].quantity}}'
      - name: create-shipment
        type: call
        call: sap.create-delivery
        with:
          order_reference: '{{order_id}}'
          sku: '{{get-order.line_items[0].sku}}'
          ship_to: '{{get-order.shipping_address}}'
      - name: notify-customer
        type: call
        call: zendesk.create-ticket
        with:
          requester_email: '{{customer_email}}'
          subject: Your Adidas order {{order_id}} has shipped!
          body: 'Tracking number: {{create-shipment.tracking_number}}. Estimated delivery: {{create-shipment.estimated_delivery}}.'
  consumes:
  - type: http
    namespace: bigcommerce
    baseUri: https://api.bigcommerce.com/stores/adidas/v2
    authentication:
      type: bearer
      token: $secrets.bigcommerce_token
    resources:
    - name: orders
      path: /orders/{{order_id}}
      inputParameters:
      - name: order_id
        in: path
      operations:
      - name: get-order
        method: GET
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/API_OUTBOUND_DELIVERY_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: availability
      path: /A_MaterialStock
      operations:
      - name: check-availability
        method: GET
    - name: deliveries
      path: /A_OutbDeliveryHeader
      operations:
      - name: create-delivery
        method: POST
  - type: http
    namespace: zendesk
    baseUri: https://adidas.zendesk.com/api/v2
    authentication:
      type: bearer
      token: $secrets.zendesk_token
    resources:
    - name: tickets
      path: /tickets.json
      operations:
      - name: create-ticket
        method: POST

Queries SAP S/4HANA for real-time stock levels of a given SKU across all regional warehouses. Used by merchandising and store operations teams.

naftiko: '0.5'
info:
  label: Product Inventory Lookup
  description: Queries SAP S/4HANA for real-time stock levels of a given SKU across all regional warehouses. Used by merchandising and store operations teams.
  tags:
  - retail
  - inventory
  - sap-s4hana
capability:
  exposes:
  - type: mcp
    namespace: inventory
    port: 8080
    tools:
    - name: get-sku-inventory
      description: Look up current inventory levels for a product SKU across all Adidas distribution centers.
      inputParameters:
      - name: sku
        in: body
        type: string
        description: The Adidas product SKU identifier.
      call: sap.get-inventory
      with:
        sku: '{{sku}}'
      outputParameters:
      - name: total_available
        type: string
        mapping: $.d.AvailableStock
      - name: warehouse_breakdown
        type: string
        mapping: $.d.PlantStockDetails
      - name: reserved_quantity
        type: string
        mapping: $.d.ReservedQuantity
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    inputParameters:
    - name: Accept
      in: header
      value: application/json
    - name: sap-client
      in: header
      value: '100'
    resources:
    - name: material-stock
      path: /A_MatlStkInAcctMod(Material='{{sku}}')
      inputParameters:
      - name: sku
        in: path
      operations:
      - name: get-inventory
        method: GET

Analyzes trend data in Snowflake, forecasts demand by category, creates collection plans in Jira, updates SAP materials, and notifies design team.

naftiko: '0.5'
info:
  label: Collection Planning Pipeline
  description: Analyzes trend data in Snowflake, forecasts demand by category, creates collection plans in Jira, updates SAP materials, and notifies design team.
  tags:
  - design
  - snowflake
  - jira
  - sap
  - slack
capability:
  exposes:
  - type: mcp
    namespace: design
    port: 8080
    tools:
    - name: collection_planning_pipeline
      description: Orchestrate collection planning pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-snowflake
        type: call
        call: snowflake.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-jira
        type: call
        call: jira.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-sap
        type: call
        call: sap.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira-op
        method: POST
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Runs a PromQL instant query against the Adidas Prometheus cluster and returns the current metric value.

naftiko: '0.5'
info:
  label: Prometheus Metric Query
  description: Runs a PromQL instant query against the Adidas Prometheus cluster and returns the current metric value.
  tags:
  - observability
  - prometheus
  - metrics
capability:
  exposes:
  - type: mcp
    namespace: metrics
    port: 8080
    tools:
    - name: query-metric
      description: Execute a PromQL instant query and return the current value for the specified metric expression.
      inputParameters:
      - name: promql
        in: body
        type: string
        description: The PromQL expression to evaluate.
      call: prometheus.instant-query
      with:
        promql: '{{promql}}'
      outputParameters:
      - name: value
        type: string
        mapping: $.data.result[0].value[1]
      - name: metric
        type: string
        mapping: $.data.result[0].metric
  consumes:
  - type: http
    namespace: prometheus
    baseUri: https://prometheus.adidas.internal/api/v1
    authentication:
      type: bearer
      token: $secrets.prometheus_token
    resources:
    - name: query
      path: /query
      inputParameters:
      - name: query
        in: query
        value: '{{promql}}'
      operations:
      - name: instant-query
        method: GET

Collects engagement metrics from social APIs, aggregates in Snowflake, updates HubSpot campaign records, refreshes dashboards, and notifies marketing.

naftiko: '0.5'
info:
  label: Social Media Campaign Tracker
  description: Collects engagement metrics from social APIs, aggregates in Snowflake, updates HubSpot campaign records, refreshes dashboards, and notifies marketing.
  tags:
  - marketing
  - hubspot
  - snowflake
  - powerbi
  - slack
capability:
  exposes:
  - type: mcp
    namespace: marketing
    port: 8080
    tools:
    - name: social_media_campaign_tracker
      description: Orchestrate social media campaign tracker workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-hubspot
        type: call
        call: hubspot.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-slack
        type: call
        call: slack.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-servicenow
        type: call
        call: servicenow.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: hubspot
    baseUri: https://api.hubapi.com
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: hubspot-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST

Exports customer segments from Snowflake, syncs to Salesforce Marketing Cloud, validates delivery in Datadog, and notifies marketing.

naftiko: '0.5'
info:
  label: Personalization Engine Sync Pipeline
  description: Exports customer segments from Snowflake, syncs to Salesforce Marketing Cloud, validates delivery in Datadog, and notifies marketing.
  tags:
  - marketing
  - snowflake
  - salesforce
  - datadog
  - slack
capability:
  exposes:
  - type: mcp
    namespace: marketing
    port: 8080
    tools:
    - name: personalization_engine_sync_pipeline
      description: Orchestrate personalization engine sync pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-snowflake
        type: call
        call: snowflake.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-salesforce
        type: call
        call: salesforce.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-datadog
        type: call
        call: datadog.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apiKey
      key: $secrets.datadog_api_key
      header: DD-API-KEY
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: datadog-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Validates shipment data from SAP against trade regulations, checks denied party lists, creates compliance records, and notifies trade compliance team.

naftiko: '0.5'
info:
  label: Cross-Border Trade Compliance
  description: Validates shipment data from SAP against trade regulations, checks denied party lists, creates compliance records, and notifies trade compliance team.
  tags:
  - trade-compliance
  - sap
  - servicenow
  - jira
  - slack
capability:
  exposes:
  - type: mcp
    namespace: trade-compliance
    port: 8080
    tools:
    - name: cross_border_trade_compliance
      description: Orchestrate cross-border trade compliance workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-servicenow
        type: call
        call: servicenow.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-jira
        type: call
        call: jira.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Deploys a trained model from Azure Machine Learning to Azure Kubernetes Service, registers the deployment in Datadog, and notifies the data science team in Teams.

naftiko: '0.5'
info:
  label: ML Model Deployment Pipeline
  description: Deploys a trained model from Azure Machine Learning to Azure Kubernetes Service, registers the deployment in Datadog, and notifies the data science team in Teams.
  tags:
  - machine-learning
  - azure-machine-learning
  - azure-kubernetes-service
  - datadog
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: ml-deployment
    port: 8080
    tools:
    - name: deploy-model
      description: Given a model name and version, deploy to AKS, register in Datadog, and notify the team.
      inputParameters:
      - name: model_name
        in: body
        type: string
        description: The Azure ML model name.
      - name: model_version
        in: body
        type: string
        description: The model version to deploy.
      - name: endpoint_name
        in: body
        type: string
        description: The AKS inference endpoint name.
      steps:
      - name: create-deployment
        type: call
        call: azure-ml.create-deployment
        with:
          model_name: '{{model_name}}'
          model_version: '{{model_version}}'
          endpoint_name: '{{endpoint_name}}'
      - name: register-monitor
        type: call
        call: datadog.create-monitor
        with:
          name: 'ML Model: {{model_name}} v{{model_version}}'
          type: metric alert
          query: avg(last_5m):avg:ml.inference.latency{model:{{model_name}}} > 500
      - name: notify-team
        type: call
        call: msteams.send-message
        with:
          channel: data-science
          text: 'Model Deployed: {{model_name}} v{{model_version}} to {{endpoint_name}} | Status: {{create-deployment.provisioning_state}} | Monitor: {{register-monitor.id}}'
  consumes:
  - type: http
    namespace: azure-ml
    baseUri: https://ml.azure.com/api/subscriptions/$secrets.azure_subscription_id/resourceGroups/adidas-ml-rg/providers/Microsoft.MachineLearningServices/workspaces/adidas-ml
    authentication:
      type: bearer
      token: $secrets.azure_token
    resources:
    - name: deployments
      path: /onlineEndpoints/{{endpoint_name}}/deployments
      inputParameters:
      - name: endpoint_name
        in: path
      operations:
      - name: create-deployment
        method: PUT
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: bearer
      token: $secrets.datadog_api_key
    inputParameters:
    - name: DD-APPLICATION-KEY
      in: header
      value: $secrets.datadog_app_key
    resources:
    - name: monitors
      path: /monitor
      operations:
      - name: create-monitor
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

When an Apache Spark job fails, logs the failure in Datadog, opens a ServiceNow incident, and notifies the data engineering team in Microsoft Teams.

naftiko: '0.5'
info:
  label: Data Pipeline Failure Handler
  description: When an Apache Spark job fails, logs the failure in Datadog, opens a ServiceNow incident, and notifies the data engineering team in Microsoft Teams.
  tags:
  - data-engineering
  - apache-spark
  - datadog
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: data-ops
    port: 8080
    tools:
    - name: handle-spark-failure
      description: Given a Spark application ID and error details, create observability event, incident, and team alert.
      inputParameters:
      - name: application_id
        in: body
        type: string
        description: The Spark application ID.
      - name: job_name
        in: body
        type: string
        description: The name of the failed Spark job.
      - name: error_message
        in: body
        type: string
        description: The error message from the failure.
      steps:
      - name: log-event
        type: call
        call: datadog.create-event
        with:
          title: 'Spark Job Failure: {{job_name}}'
          text: 'App: {{application_id}} | Error: {{error_message}}'
          alert_type: error
          tags: spark,job:{{job_name}}
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: '[Data Pipeline] Spark job failed: {{job_name}}'
          category: data_engineering
          priority: '2'
          description: 'Application: {{application_id}}

            Job: {{job_name}}

            Error: {{error_message}}'
      - name: alert-team
        type: call
        call: msteams.send-message
        with:
          channel: data-engineering-alerts
          text: 'Spark Failure: {{job_name}} | App: {{application_id}} | Error: {{error_message}} | Incident: {{create-incident.number}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: bearer
      token: $secrets.datadog_api_key
    inputParameters:
    - name: DD-APPLICATION-KEY
      in: header
      value: $secrets.datadog_app_key
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

Monitors order fulfillment times from SAP, checks against SLAs in Snowflake, creates escalations in ServiceNow, and notifies operations.

naftiko: '0.5'
info:
  label: Order Fulfillment SLA Monitor
  description: Monitors order fulfillment times from SAP, checks against SLAs in Snowflake, creates escalations in ServiceNow, and notifies operations.
  tags:
  - fulfillment
  - sap
  - snowflake
  - servicenow
  - slack
capability:
  exposes:
  - type: mcp
    namespace: fulfillment
    port: 8080
    tools:
    - name: order_fulfillment_sla_monitor
      description: Orchestrate order fulfillment sla monitor workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-servicenow
        type: call
        call: servicenow.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Identifies affected batches in SAP, traces distribution, notifies retailers via Salesforce, creates recall task force in ServiceNow, and alerts legal.

naftiko: '0.5'
info:
  label: Product Recall Management Pipeline
  description: Identifies affected batches in SAP, traces distribution, notifies retailers via Salesforce, creates recall task force in ServiceNow, and alerts legal.
  tags:
  - quality
  - sap
  - salesforce
  - servicenow
  - slack
capability:
  exposes:
  - type: mcp
    namespace: quality
    port: 8080
    tools:
    - name: product_recall_management_pipeline
      description: Orchestrate product recall management pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-salesforce
        type: call
        call: salesforce.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-servicenow
        type: call
        call: servicenow.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Runs a Terraform plan via GitHub Actions, detects drift, opens a ServiceNow change request, and alerts the infrastructure team in Teams.

naftiko: '0.5'
info:
  label: Terraform Drift Detection and Remediation
  description: Runs a Terraform plan via GitHub Actions, detects drift, opens a ServiceNow change request, and alerts the infrastructure team in Teams.
  tags:
  - infrastructure
  - terraform
  - github-actions
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: iac-drift
    port: 8080
    tools:
    - name: detect-and-remediate-drift
      description: Given a Terraform workspace, run a plan, detect drift, and open a change request if drift is found.
      inputParameters:
      - name: workspace
        in: body
        type: string
        description: The Terraform Cloud workspace name.
      - name: repository
        in: body
        type: string
        description: The GitHub repository containing the Terraform code.
      steps:
      - name: trigger-plan
        type: call
        call: github-actions.trigger-workflow
        with:
          repository: '{{repository}}'
          workflow_id: terraform-plan.yml
          ref: main
          inputs_workspace: '{{workspace}}'
      - name: open-change-request
        type: call
        call: servicenow.create-change-request
        with:
          short_description: 'Terraform drift detected: {{workspace}}'
          category: infrastructure
          description: 'Drift detected in workspace {{workspace}}. Plan run: {{trigger-plan.run_id}}. Repository: {{repository}}.'
          risk: moderate
      - name: notify-team
        type: call
        call: msteams.send-message
        with:
          channel: infra-ops
          text: 'Terraform Drift: {{workspace}} | Change Request: {{open-change-request.number}} | Plan: {{trigger-plan.run_id}} | Repo: {{repository}}'
  consumes:
  - type: http
    namespace: github-actions
    baseUri: https://api.github.com/repos
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: workflows
      path: /{{repository}}/actions/workflows/{{workflow_id}}/dispatches
      inputParameters:
      - name: repository
        in: path
      - name: workflow_id
        in: path
      operations:
      - name: trigger-workflow
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: change-requests
      path: /table/change_request
      operations:
      - name: create-change-request
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

Receives wholesale orders in Salesforce, validates credit in SAP, creates fulfillment orders, updates Snowflake analytics, and notifies sales.

naftiko: '0.5'
info:
  label: Wholesale Order Processing Pipeline
  description: Receives wholesale orders in Salesforce, validates credit in SAP, creates fulfillment orders, updates Snowflake analytics, and notifies sales.
  tags:
  - wholesale
  - salesforce
  - sap
  - snowflake
  - slack
capability:
  exposes:
  - type: mcp
    namespace: wholesale
    port: 8080
    tools:
    - name: wholesale_order_processing_pipeline
      description: Orchestrate wholesale order processing pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-salesforce
        type: call
        call: salesforce.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-sap
        type: call
        call: sap.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-snowflake
        type: call
        call: snowflake.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Monitors transactions from Stripe, runs fraud scoring in Snowflake, blocks suspicious orders, creates cases in ServiceNow, and alerts fraud team.

naftiko: '0.5'
info:
  label: E-Commerce Fraud Detection Pipeline
  description: Monitors transactions from Stripe, runs fraud scoring in Snowflake, blocks suspicious orders, creates cases in ServiceNow, and alerts fraud team.
  tags:
  - fraud
  - stripe
  - snowflake
  - servicenow
  - slack
capability:
  exposes:
  - type: mcp
    namespace: fraud
    port: 8080
    tools:
    - name: e_commerce_fraud_detection_pipeline
      description: Orchestrate e-commerce fraud detection pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-stripe
        type: call
        call: stripe.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-servicenow
        type: call
        call: servicenow.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: stripe
    baseUri: https://api.stripe.com/v1
    authentication:
      type: bearer
      token: $secrets.stripe_secret_key
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: stripe-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Searches the Adidas product catalog index in Elasticsearch by keyword and returns matching product names, prices, and availability.

naftiko: '0.5'
info:
  label: Elasticsearch Product Search
  description: Searches the Adidas product catalog index in Elasticsearch by keyword and returns matching product names, prices, and availability.
  tags:
  - search
  - elasticsearch
  - product-catalog
capability:
  exposes:
  - type: mcp
    namespace: product-search
    port: 8080
    tools:
    - name: search-products
      description: Search the product catalog by keyword and return matching products with prices and availability.
      inputParameters:
      - name: query
        in: body
        type: string
        description: Free-text search query for products.
      - name: limit
        in: body
        type: string
        description: Maximum number of results to return.
      call: elasticsearch.search
      with:
        query: '{{query}}'
        limit: '{{limit}}'
      outputParameters:
      - name: total_hits
        type: string
        mapping: $.hits.total.value
      - name: products
        type: string
        mapping: $.hits.hits
  consumes:
  - type: http
    namespace: elasticsearch
    baseUri: https://es.adidas.internal:9200
    authentication:
      type: basic
      username: $secrets.es_user
      password: $secrets.es_password
    resources:
    - name: product-index
      path: /products/_search
      operations:
      - name: search
        method: POST

When SonarQube detects a critical vulnerability, creates a GitHub issue, opens a ServiceNow security incident, and alerts the security team via Teams.

naftiko: '0.5'
info:
  label: Security Vulnerability Response
  description: When SonarQube detects a critical vulnerability, creates a GitHub issue, opens a ServiceNow security incident, and alerts the security team via Teams.
  tags:
  - security
  - sonarqube
  - github
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: security-response
    port: 8080
    tools:
    - name: handle-vulnerability
      description: Given a SonarQube project and vulnerability details, create tracking issue, security incident, and alert the team.
      inputParameters:
      - name: project_key
        in: body
        type: string
        description: The SonarQube project key.
      - name: vulnerability_id
        in: body
        type: string
        description: The SonarQube vulnerability issue key.
      - name: severity
        in: body
        type: string
        description: Vulnerability severity (CRITICAL, HIGH, MEDIUM, LOW).
      steps:
      - name: get-vulnerability
        type: call
        call: sonarqube.get-issue
        with:
          issue_key: '{{vulnerability_id}}'
      - name: create-gh-issue
        type: call
        call: github.create-issue
        with:
          repository: adidas/{{project_key}}
          title: '[Security] {{severity}}: {{get-vulnerability.message}}'
          body: 'SonarQube: {{vulnerability_id}}

            Severity: {{severity}}

            Component: {{get-vulnerability.component}}

            Line: {{get-vulnerability.line}}'
          labels: security,{{severity}}
      - name: create-security-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Security vulnerability: {{project_key}} — {{severity}}'
          category: security
          priority: '1'
          description: '{{get-vulnerability.message}}. GitHub: {{create-gh-issue.html_url}}'
      - name: alert-security
        type: call
        call: msteams.send-message
        with:
          channel: security-alerts
          text: 'Security Alert: {{severity}} vulnerability in {{project_key}} | {{get-vulnerability.message}} | GH: {{create-gh-issue.html_url}} | Incident: {{create-security-incident.number}}'
  consumes:
  - type: http
    namespace: sonarqube
    baseUri: https://sonarqube.adidas.internal/api
    authentication:
      type: bearer
      token: $secrets.sonarqube_token
    resources:
    - name: issues
      path: /issues/search
      inputParameters:
      - name: issues
        in: query
        value: '{{issue_key}}'
      operations:
      - name: get-issue
        method: GET
  - type: http
    namespace: github
    baseUri: https://api.github.com/repos
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: issues
      path: /{{repository}}/issues
      inputParameters:
      - name: repository
        in: path
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

Retrieves PagerDuty incident details for Adidas on-call teams.

naftiko: '0.5'
info:
  label: PagerDuty Incident Details
  description: Retrieves PagerDuty incident details for Adidas on-call teams.
  tags:
  - devops
  - pagerduty
  - on-call
capability:
  exposes:
  - type: mcp
    namespace: incident-mgmt
    port: 8080
    tools:
    - name: get-incident
      description: Look up incident at Adidas.
      inputParameters:
      - name: incident_id
        in: body
        type: string
        description: The incident_id to look up.
      call: pagerduty.get-incident_id
      with:
        incident_id: '{{incident_id}}'
  consumes:
  - type: http
    namespace: pagerduty
    baseUri: https://api.pagerduty.com
    authentication:
      type: bearer
      token: $secrets.pagerduty_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: pagerduty_incident_details
        method: GET

Calculates loyalty points from Stripe transactions, updates member profile in Salesforce, triggers reward notification, and syncs to analytics.

naftiko: '0.5'
info:
  label: Customer Loyalty Rewards Processor
  description: Calculates loyalty points from Stripe transactions, updates member profile in Salesforce, triggers reward notification, and syncs to analytics.
  tags:
  - loyalty
  - stripe
  - salesforce
  - snowflake
  - slack
capability:
  exposes:
  - type: mcp
    namespace: loyalty
    port: 8080
    tools:
    - name: customer_loyalty_rewards_processor
      description: Orchestrate customer loyalty rewards processor workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-stripe
        type: call
        call: stripe.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-salesforce
        type: call
        call: salesforce.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-snowflake
        type: call
        call: snowflake.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: stripe
    baseUri: https://api.stripe.com/v1
    authentication:
      type: bearer
      token: $secrets.stripe_secret_key
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: stripe-op
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Tracks sponsorship contracts in SAP, validates deliverables, updates Salesforce, creates renewal tasks in Jira, and notifies partnership team.

naftiko: '0.5'
info:
  label: Athlete Sponsorship Contract Pipeline
  description: Tracks sponsorship contracts in SAP, validates deliverables, updates Salesforce, creates renewal tasks in Jira, and notifies partnership team.
  tags:
  - sponsorship
  - sap
  - salesforce
  - jira
  - slack
capability:
  exposes:
  - type: mcp
    namespace: sponsorship
    port: 8080
    tools:
    - name: athlete_sponsorship_contract_pipeline
      description: Orchestrate athlete sponsorship contract pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-salesforce
        type: call
        call: salesforce.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-jira
        type: call
        call: jira.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

When Palo Alto Networks detects a threat, blocks the source IP via Cisco firewall, creates a ServiceNow security incident, and alerts the SOC team in Microsoft Teams.

naftiko: '0.5'
info:
  label: Network Incident Auto-Remediation
  description: When Palo Alto Networks detects a threat, blocks the source IP via Cisco firewall, creates a ServiceNow security incident, and alerts the SOC team in Microsoft Teams.
  tags:
  - security
  - network
  - palo-alto-networks
  - cisco
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: network-security
    port: 8080
    tools:
    - name: remediate-threat
      description: Given a threat event from Palo Alto, block the source IP, create a security incident, and alert the SOC.
      inputParameters:
      - name: threat_id
        in: body
        type: string
        description: The Palo Alto threat log ID.
      - name: source_ip
        in: body
        type: string
        description: The source IP address of the threat.
      - name: threat_type
        in: body
        type: string
        description: The threat classification.
      steps:
      - name: get-threat-details
        type: call
        call: paloalto.get-threat-log
        with:
          threat_id: '{{threat_id}}'
      - name: block-ip
        type: call
        call: cisco.add-acl-entry
        with:
          source_ip: '{{source_ip}}'
          action: deny
          description: 'Auto-blocked: {{threat_type}} — {{threat_id}}'
      - name: create-security-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Network threat: {{threat_type}} from {{source_ip}}'
          category: security
          priority: '1'
          description: 'Threat: {{get-threat-details.description}} | Source: {{source_ip}} | Auto-blocked via Cisco ACL. Palo Alto log: {{threat_id}}.'
      - name: alert-soc
        type: call
        call: msteams.send-message
        with:
          channel: soc-alerts
          text: 'Network Threat Remediated: {{threat_type}} from {{source_ip}} | Blocked: YES | Incident: {{create-security-incident.number}} | PA Log: {{threat_id}}'
  consumes:
  - type: http
    namespace: paloalto
    baseUri: https://panorama.adidas.com/api
    authentication:
      type: bearer
      token: $secrets.paloalto_api_key
    resources:
    - name: threat-logs
      path: /logs/threat/{{threat_id}}
      inputParameters:
      - name: threat_id
        in: path
      operations:
      - name: get-threat-log
        method: GET
  - type: http
    namespace: cisco
    baseUri: https://cisco-fw.adidas.internal/restconf/data
    authentication:
      type: basic
      username: $secrets.cisco_user
      password: $secrets.cisco_password
    resources:
    - name: acl
      path: /Cisco-IOS-XE-native:native/ip/access-list
      operations:
      - name: add-acl-entry
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

Monitors POS anomalies from SAP, cross-references with video analytics, creates investigation cases in ServiceNow, and alerts loss prevention.

naftiko: '0.5'
info:
  label: Retail Theft Prevention Pipeline
  description: Monitors POS anomalies from SAP, cross-references with video analytics, creates investigation cases in ServiceNow, and alerts loss prevention.
  tags:
  - loss-prevention
  - sap
  - servicenow
  - slack
capability:
  exposes:
  - type: mcp
    namespace: loss-prevention
    port: 8080
    tools:
    - name: retail_theft_prevention_pipeline
      description: Orchestrate retail theft prevention pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-servicenow
        type: call
        call: servicenow.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-slack
        type: call
        call: slack.create-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Exports a GitLab project's issues and pipelines, creates corresponding work items in Azure DevOps, and logs the migration progress in a Google Sheet.

naftiko: '0.5'
info:
  label: GitLab to Azure DevOps Migration Tracker
  description: Exports a GitLab project's issues and pipelines, creates corresponding work items in Azure DevOps, and logs the migration progress in a Google Sheet.
  tags:
  - devops
  - migration
  - gitlab
  - azure-devops
  - google-sheets
capability:
  exposes:
  - type: mcp
    namespace: devops-migration
    port: 8080
    tools:
    - name: migrate-project
      description: Given a GitLab project ID and Azure DevOps project, migrate issues and pipeline config and track progress.
      inputParameters:
      - name: gitlab_project_id
        in: body
        type: string
        description: The GitLab project ID.
      - name: azdo_project
        in: body
        type: string
        description: The Azure DevOps project name.
      - name: tracker_sheet_id
        in: body
        type: string
        description: Google Sheets ID for migration tracking.
      steps:
      - name: export-issues
        type: call
        call: gitlab.list-issues
        with:
          project_id: '{{gitlab_project_id}}'
      - name: create-work-items
        type: call
        call: azdo.create-work-item
        with:
          project: '{{azdo_project}}'
          type: User Story
          title: 'Migrated from GitLab: {{export-issues.title}}'
          description: '{{export-issues.description}}'
      - name: log-progress
        type: call
        call: gsheets.append-row
        with:
          spreadsheet_id: '{{tracker_sheet_id}}'
          range: Migration!A1
          values: '{{gitlab_project_id}},{{azdo_project}},{{export-issues.total_count}},{{create-work-items.count}},completed'
  consumes:
  - type: http
    namespace: gitlab
    baseUri: https://gitlab.adidas.com/api/v4
    authentication:
      type: bearer
      token: $secrets.gitlab_token
    resources:
    - name: issues
      path: /projects/{{project_id}}/issues
      inputParameters:
      - name: project_id
        in: path
      operations:
      - name: list-issues
        method: GET
  - type: http
    namespace: azdo
    baseUri: https://dev.azure.com/adidas
    authentication:
      type: basic
      username: ''
      password: $secrets.azdo_pat
    resources:
    - name: work-items
      path: /{{project}}/_apis/wit/workitems/$User Story
      inputParameters:
      - name: project
        in: path
      operations:
      - name: create-work-item
        method: POST
  - type: http
    namespace: gsheets
    baseUri: https://sheets.googleapis.com/v4/spreadsheets
    authentication:
      type: bearer
      token: $secrets.google_sheets_token
    resources:
    - name: values
      path: /{{spreadsheet_id}}/values/{{range}}:append
      inputParameters:
      - name: spreadsheet_id
        in: path
      - name: range
        in: path
      operations:
      - name: append-row
        method: POST

Collects engagement metrics from Instagram, Facebook, Twitter, and YouTube for a given campaign hashtag and posts a consolidated summary to Microsoft Teams.

naftiko: '0.5'
info:
  label: Social Media Engagement Aggregator
  description: Collects engagement metrics from Instagram, Facebook, Twitter, and YouTube for a given campaign hashtag and posts a consolidated summary to Microsoft Teams.
  tags:
  - marketing
  - social-media
  - instagram
  - facebook
  - twitter
  - youtube
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: social-analytics
    port: 8080
    tools:
    - name: aggregate-engagement
      description: Given a campaign hashtag, collect engagement metrics from all social channels and post a summary to Teams.
      inputParameters:
      - name: hashtag
        in: body
        type: string
        description: 'The campaign hashtag to track (without #).'
      - name: date_range
        in: body
        type: string
        description: Date range in YYYY-MM-DD/YYYY-MM-DD format.
      steps:
      - name: get-instagram-metrics
        type: call
        call: instagram.get-hashtag-metrics
        with:
          hashtag: '{{hashtag}}'
          date_range: '{{date_range}}'
      - name: get-facebook-metrics
        type: call
        call: facebook.get-page-insights
        with:
          hashtag: '{{hashtag}}'
          date_range: '{{date_range}}'
      - name: get-twitter-metrics
        type: call
        call: twitter.get-tweet-metrics
        with:
          hashtag: '{{hashtag}}'
          date_range: '{{date_range}}'
      - name: get-youtube-metrics
        type: call
        call: youtube.get-video-metrics
        with:
          hashtag: '{{hashtag}}'
          date_range: '{{date_range}}'
      - name: post-summary
        type: call
        call: msteams.send-message
        with:
          channel: marketing-analytics
          text: 'Campaign #{{hashtag}} Engagement Summary | IG: {{get-instagram-metrics.total_engagement}} | FB: {{get-facebook-metrics.total_engagement}} | Twitter: {{get-twitter-metrics.total_engagement}} | YT: {{get-youtube-metrics.total_views}}'
  consumes:
  - type: http
    namespace: instagram
    baseUri: https://graph.facebook.com/v18.0
    authentication:
      type: bearer
      token: $secrets.instagram_token
    resources:
    - name: hashtag-search
      path: /ig_hashtag_search
      operations:
      - name: get-hashtag-metrics
        method: GET
  - type: http
    namespace: facebook
    baseUri: https://graph.facebook.com/v18.0
    authentication:
      type: bearer
      token: $secrets.facebook_page_token
    resources:
    - name: insights
      path: /{{page_id}}/insights
      operations:
      - name: get-page-insights
        method: GET
  - type: http
    namespace: twitter
    baseUri: https://api.twitter.com/2
    authentication:
      type: bearer
      token: $secrets.twitter_bearer_token
    resources:
    - name: tweets
      path: /tweets/search/recent
      operations:
      - name: get-tweet-metrics
        method: GET
  - type: http
    namespace: youtube
    baseUri: https://www.googleapis.com/youtube/v3
    authentication:
      type: bearer
      token: $secrets.youtube_api_key
    resources:
    - name: search
      path: /search
      operations:
      - name: get-video-metrics
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

Validates product labels against regulatory databases, checks SAP material master data, creates compliance records, and notifies regulatory team.

naftiko: '0.5'
info:
  label: Compliance Labeling Verification
  description: Validates product labels against regulatory databases, checks SAP material master data, creates compliance records, and notifies regulatory team.
  tags:
  - compliance
  - sap
  - servicenow
  - jira
  - slack
capability:
  exposes:
  - type: mcp
    namespace: compliance
    port: 8080
    tools:
    - name: compliance_labeling_verification
      description: Orchestrate compliance labeling verification workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-servicenow
        type: call
        call: servicenow.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-jira
        type: call
        call: jira.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Fetches open problems from Dynatrace for a given management zone and returns problem titles, severity levels, and impacted entities.

naftiko: '0.5'
info:
  label: Dynatrace Problem Query
  description: Fetches open problems from Dynatrace for a given management zone and returns problem titles, severity levels, and impacted entities.
  tags:
  - observability
  - dynatrace
  - incident-management
capability:
  exposes:
  - type: mcp
    namespace: apm
    port: 8080
    tools:
    - name: get-open-problems
      description: Query Dynatrace for open problems in a management zone, returning severity and impacted entities.
      inputParameters:
      - name: management_zone
        in: body
        type: string
        description: The Dynatrace management zone name.
      call: dynatrace.list-problems
      with:
        management_zone: '{{management_zone}}'
      outputParameters:
      - name: total_count
        type: string
        mapping: $.totalCount
      - name: problems
        type: string
        mapping: $.problems
  consumes:
  - type: http
    namespace: dynatrace
    baseUri: https://adidas.live.dynatrace.com/api/v2
    authentication:
      type: bearer
      token: $secrets.dynatrace_token
    resources:
    - name: problems
      path: /problems
      inputParameters:
      - name: problemSelector
        in: query
        value: managementZoneIds({{management_zone}}),status(OPEN)
      operations:
      - name: list-problems
        method: GET

Runs a top-N sales query against SAP HANA for a given product category and region, returning aggregated revenue and units sold.

naftiko: '0.5'
info:
  label: SAP HANA Sales Cube Query
  description: Runs a top-N sales query against SAP HANA for a given product category and region, returning aggregated revenue and units sold.
  tags:
  - analytics
  - sap-hana
  - sales
capability:
  exposes:
  - type: mcp
    namespace: sales-analytics
    port: 8080
    tools:
    - name: query-sales-cube
      description: Query SAP HANA sales analytics cube for revenue and units sold by product category and region.
      inputParameters:
      - name: category
        in: body
        type: string
        description: Product category (e.g. footwear, apparel, accessories).
      - name: region
        in: body
        type: string
        description: Sales region code (e.g. EMEA, NAM, APAC).
      call: sap-hana.run-query
      with:
        category: '{{category}}'
        region: '{{region}}'
      outputParameters:
      - name: total_revenue
        type: string
        mapping: $.results[0].REVENUE
      - name: units_sold
        type: string
        mapping: $.results[0].UNITS
  consumes:
  - type: http
    namespace: sap-hana
    baseUri: https://adidas-hana.sap.com/sap/hana/xs/api
    authentication:
      type: basic
      username: $secrets.sap_hana_user
      password: $secrets.sap_hana_password
    resources:
    - name: sales-cube
      path: /analytics/sales
      operations:
      - name: run-query
        method: POST

Retrieves Okta user profile for Adidas identity management.

naftiko: '0.5'
info:
  label: Okta User Profile Lookup
  description: Retrieves Okta user profile for Adidas identity management.
  tags:
  - security
  - okta
  - identity
capability:
  exposes:
  - type: mcp
    namespace: identity
    port: 8080
    tools:
    - name: get-user
      description: Look up user at Adidas.
      inputParameters:
      - name: user_email
        in: body
        type: string
        description: The user_email to look up.
      call: okta.get-user_email
      with:
        user_email: '{{user_email}}'
  consumes:
  - type: http
    namespace: okta
    baseUri: https://adidas.okta.com/api/v1
    authentication:
      type: apiKey
      key: $secrets.okta_api_token
      header: Authorization
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: okta_user_profile_lookup
        method: GET

Collects carbon footprint data from SAP, aggregates in Snowflake, generates ESG reports in Power BI, and publishes to sustainability team.

naftiko: '0.5'
info:
  label: Sustainability Metrics Collection Pipeline
  description: Collects carbon footprint data from SAP, aggregates in Snowflake, generates ESG reports in Power BI, and publishes to sustainability team.
  tags:
  - sustainability
  - sap
  - snowflake
  - powerbi
  - slack
capability:
  exposes:
  - type: mcp
    namespace: sustainability
    port: 8080
    tools:
    - name: sustainability_metrics_collector
      description: Orchestrate sustainability metrics collection pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-slack
        type: call
        call: slack.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-servicenow
        type: call
        call: servicenow.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST

Retrieves a Salesforce lead record and returns scoring details, source channel, and status. Used by sales development reps to prioritize outreach.

naftiko: '0.5'
info:
  label: Salesforce Lead Qualification
  description: Retrieves a Salesforce lead record and returns scoring details, source channel, and status. Used by sales development reps to prioritize outreach.
  tags:
  - sales
  - salesforce
  - lead-management
capability:
  exposes:
  - type: mcp
    namespace: sales
    port: 8080
    tools:
    - name: get-lead-details
      description: Look up a Salesforce lead by ID and return qualification score, status, and source.
      inputParameters:
      - name: lead_id
        in: body
        type: string
        description: The Salesforce lead record ID.
      call: salesforce.get-lead
      with:
        lead_id: '{{lead_id}}'
      outputParameters:
      - name: lead_score
        type: string
        mapping: $.Lead_Score__c
      - name: status
        type: string
        mapping: $.Status
      - name: source
        type: string
        mapping: $.LeadSource
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: leads
      path: /sobjects/Lead/{{lead_id}}
      inputParameters:
      - name: lead_id
        in: path
      operations:
      - name: get-lead
        method: GET

Extracts return data from SAP, analyzes patterns in Snowflake, identifies quality issues, creates Jira tickets, and notifies product team.

naftiko: '0.5'
info:
  label: Product Return Analysis Pipeline
  description: Extracts return data from SAP, analyzes patterns in Snowflake, identifies quality issues, creates Jira tickets, and notifies product team.
  tags:
  - returns
  - sap
  - snowflake
  - jira
  - slack
capability:
  exposes:
  - type: mcp
    namespace: returns
    port: 8080
    tools:
    - name: product_return_analysis_pipeline
      description: Orchestrate product return analysis pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-jira
        type: call
        call: jira.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Retrieves a BigCommerce order by ID and returns order status, total, shipping address, and line items.

naftiko: '0.5'
info:
  label: BigCommerce Order Lookup
  description: Retrieves a BigCommerce order by ID and returns order status, total, shipping address, and line items.
  tags:
  - ecommerce
  - bigcommerce
  - order-management
capability:
  exposes:
  - type: mcp
    namespace: ecommerce
    port: 8080
    tools:
    - name: get-order
      description: Look up a BigCommerce order by ID and return its status, total, and shipping details.
      inputParameters:
      - name: order_id
        in: body
        type: string
        description: The BigCommerce order ID.
      call: bigcommerce.get-order
      with:
        order_id: '{{order_id}}'
      outputParameters:
      - name: status
        type: string
        mapping: $.status
      - name: total
        type: string
        mapping: $.total_inc_tax
      - name: shipping_address
        type: string
        mapping: $.shipping_addresses
  consumes:
  - type: http
    namespace: bigcommerce
    baseUri: https://api.bigcommerce.com/stores/adidas/v2
    authentication:
      type: bearer
      token: $secrets.bigcommerce_token
    inputParameters:
    - name: X-Auth-Token
      in: header
      value: $secrets.bigcommerce_auth_token
    resources:
    - name: orders
      path: /orders/{{order_id}}
      inputParameters:
      - name: order_id
        in: path
      operations:
      - name: get-order
        method: GET

When OpenTelemetry detects high-latency traces, extracts span details, creates a Dynatrace problem annotation, and opens a ServiceNow incident with trace context.

naftiko: '0.5'
info:
  label: OpenTelemetry Trace to Incident
  description: When OpenTelemetry detects high-latency traces, extracts span details, creates a Dynatrace problem annotation, and opens a ServiceNow incident with trace context.
  tags:
  - observability
  - opentelemetry
  - dynatrace
  - servicenow
capability:
  exposes:
  - type: mcp
    namespace: trace-incident
    port: 8080
    tools:
    - name: escalate-trace
      description: Given an OpenTelemetry trace ID, extract details, annotate in Dynatrace, and create an incident.
      inputParameters:
      - name: trace_id
        in: body
        type: string
        description: The OpenTelemetry trace ID.
      - name: service_name
        in: body
        type: string
        description: The affected service name.
      - name: latency_ms
        in: body
        type: string
        description: The observed latency in milliseconds.
      steps:
      - name: get-trace
        type: call
        call: otel.get-trace
        with:
          trace_id: '{{trace_id}}'
      - name: annotate-dynatrace
        type: call
        call: dynatrace.create-event
        with:
          entity_id: '{{service_name}}'
          event_type: CUSTOM_ANNOTATION
          description: 'High latency trace: {{trace_id}} — {{latency_ms}}ms'
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'High latency: {{service_name}} — {{latency_ms}}ms'
          category: performance
          priority: '2'
          description: 'Trace ID: {{trace_id}} | Service: {{service_name}} | Latency: {{latency_ms}}ms | Root span: {{get-trace.root_span_name}} | Dynatrace event: {{annotate-dynatrace.id}}'
  consumes:
  - type: http
    namespace: otel
    baseUri: https://otel-collector.adidas.internal/api/v1
    authentication:
      type: bearer
      token: $secrets.otel_token
    resources:
    - name: traces
      path: /traces/{{trace_id}}
      inputParameters:
      - name: trace_id
        in: path
      operations:
      - name: get-trace
        method: GET
  - type: http
    namespace: dynatrace
    baseUri: https://adidas.live.dynatrace.com/api/v2
    authentication:
      type: bearer
      token: $secrets.dynatrace_token
    resources:
    - name: events
      path: /events/ingest
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST

Tracks product stages in SAP PLM, syncs to Snowflake for analytics, creates phase-gate tasks in Jira, and notifies product management.

naftiko: '0.5'
info:
  label: Product Lifecycle Management Pipeline
  description: Tracks product stages in SAP PLM, syncs to Snowflake for analytics, creates phase-gate tasks in Jira, and notifies product management.
  tags:
  - plm
  - sap
  - snowflake
  - jira
  - slack
capability:
  exposes:
  - type: mcp
    namespace: plm
    port: 8080
    tools:
    - name: product_lifecycle_management_pipeline
      description: Orchestrate product lifecycle management pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-jira
        type: call
        call: jira.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Pulls vendor records from Oracle E-Business Suite, cross-references compliance data in SAP, and generates an audit report in SharePoint with findings logged to ServiceNow.

naftiko: '0.5'
info:
  label: Vendor Compliance Audit
  description: Pulls vendor records from Oracle E-Business Suite, cross-references compliance data in SAP, and generates an audit report in SharePoint with findings logged to ServiceNow.
  tags:
  - compliance
  - oracle-e-business-suite
  - sap-s4hana
  - sharepoint
  - servicenow
capability:
  exposes:
  - type: mcp
    namespace: vendor-compliance
    port: 8080
    tools:
    - name: run-vendor-audit
      description: Given a vendor ID, pull records from Oracle and SAP, then generate an audit report and log findings.
      inputParameters:
      - name: vendor_id
        in: body
        type: string
        description: The vendor identifier.
      - name: audit_type
        in: body
        type: string
        description: Type of audit (sustainability, labor, quality).
      steps:
      - name: get-oracle-vendor
        type: call
        call: oracle.get-vendor
        with:
          vendor_id: '{{vendor_id}}'
      - name: get-sap-compliance
        type: call
        call: sap.get-vendor-compliance
        with:
          vendor_id: '{{vendor_id}}'
          audit_type: '{{audit_type}}'
      - name: create-report
        type: call
        call: sharepoint.create-file
        with:
          site_id: compliance_audits
          folder_path: Vendors/{{get-oracle-vendor.vendor_name}}
          file_name: audit_{{audit_type}}_report.docx
          content: 'Vendor: {{get-oracle-vendor.vendor_name}} | Type: {{audit_type}} | Score: {{get-sap-compliance.score}} | Findings: {{get-sap-compliance.findings_count}}'
      - name: log-findings
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Vendor audit: {{get-oracle-vendor.vendor_name}} — {{audit_type}}'
          category: compliance
          description: 'Score: {{get-sap-compliance.score}}. Findings: {{get-sap-compliance.findings_count}}. Report: {{create-report.url}}'
  consumes:
  - type: http
    namespace: oracle
    baseUri: https://oracle-ebs.adidas.com/webservices/rest/v1
    authentication:
      type: basic
      username: $secrets.oracle_user
      password: $secrets.oracle_password
    resources:
    - name: vendors
      path: /vendors/{{vendor_id}}
      inputParameters:
      - name: vendor_id
        in: path
      operations:
      - name: get-vendor
        method: GET
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/API_BUSINESS_PARTNER
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: compliance
      path: /A_Supplier('{{vendor_id}}')/to_ComplianceData
      inputParameters:
      - name: vendor_id
        in: path
      operations:
      - name: get-vendor-compliance
        method: GET
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: drive-items
      path: /{{site_id}}/drive/root:/{{folder_path}}/{{file_name}}:/content
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      - name: file_name
        in: path
      operations:
      - name: create-file
        method: PUT
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST

Tracks program participation from Workday, calculates engagement in Snowflake, updates Power BI reports, and notifies HR team.

naftiko: '0.5'
info:
  label: Employee Wellness Program Pipeline
  description: Tracks program participation from Workday, calculates engagement in Snowflake, updates Power BI reports, and notifies HR team.
  tags:
  - hr
  - workday
  - snowflake
  - powerbi
  - slack
capability:
  exposes:
  - type: mcp
    namespace: hr
    port: 8080
    tools:
    - name: employee_wellness_program_pipeline
      description: Orchestrate employee wellness program pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-workday
        type: call
        call: workday.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-slack
        type: call
        call: slack.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-servicenow
        type: call
        call: servicenow.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd5-impl-services1.workday.com/ccx/api/v1/adidas
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: workday-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST

Sends a message to a Slack channel for Adidas notifications.

naftiko: '0.5'
info:
  label: Slack Channel Post
  description: Sends a message to a Slack channel for Adidas notifications.
  tags:
  - collaboration
  - slack
  - messaging
capability:
  exposes:
  - type: mcp
    namespace: messaging
    port: 8080
    tools:
    - name: send-message
      description: Post to Slack at Adidas.
      inputParameters:
      - name: channel
        in: body
        type: string
        description: The channel to look up.
      call: slack.get-channel
      with:
        channel: '{{channel}}'
  consumes:
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack_channel_post
        method: GET

Looks up a ServiceNow incident by number and returns its state, priority, assigned group, and resolution notes.

naftiko: '0.5'
info:
  label: ServiceNow Incident Status
  description: Looks up a ServiceNow incident by number and returns its state, priority, assigned group, and resolution notes.
  tags:
  - itsm
  - servicenow
  - incident-management
capability:
  exposes:
  - type: mcp
    namespace: itsm
    port: 8080
    tools:
    - name: get-incident
      description: Retrieve a ServiceNow incident record by number including state, priority, and assignment.
      inputParameters:
      - name: incident_number
        in: body
        type: string
        description: The ServiceNow incident number (e.g. INC0012345).
      call: servicenow.get-incident
      with:
        incident_number: '{{incident_number}}'
      outputParameters:
      - name: state
        type: string
        mapping: $.result[0].state
      - name: priority
        type: string
        mapping: $.result[0].priority
      - name: assigned_group
        type: string
        mapping: $.result[0].assignment_group.display_value
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      inputParameters:
      - name: sysparm_query
        in: query
        value: number={{incident_number}}
      - name: incident_number
        in: path
      operations:
      - name: get-incident
        method: GET

Triggers Power BI dataset refresh for Adidas reporting.

naftiko: '0.5'
info:
  label: Power BI Refresh Trigger
  description: Triggers Power BI dataset refresh for Adidas reporting.
  tags:
  - analytics
  - power-bi
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: analytics
    port: 8080
    tools:
    - name: trigger-refresh
      description: Trigger refresh at Adidas.
      inputParameters:
      - name: dataset_id
        in: body
        type: string
        description: The dataset_id to look up.
      call: powerbi.get-dataset_id
      with:
        dataset_id: '{{dataset_id}}'
  consumes:
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: power_bi_refresh_trigger
        method: GET

When a SAP S/4HANA purchase order exceeds a spend threshold, routes for manager approval via PeopleSoft and notifies the requestor in Microsoft Teams with approval status.

naftiko: '0.5'
info:
  label: SAP Purchase Order Approval Pipeline
  description: When a SAP S/4HANA purchase order exceeds a spend threshold, routes for manager approval via PeopleSoft and notifies the requestor in Microsoft Teams with approval status.
  tags:
  - procurement
  - sap-s4hana
  - peoplesoft
  - microsoft-teams
  - approval
capability:
  exposes:
  - type: mcp
    namespace: po-approval
    port: 8080
    tools:
    - name: route-po-approval
      description: Given a PO number and requestor ID, check the amount, route for approval, and notify both parties.
      inputParameters:
      - name: po_number
        in: body
        type: string
        description: The SAP purchase order number.
      - name: requestor_id
        in: body
        type: string
        description: The PeopleSoft employee ID of the requestor.
      - name: spend_amount
        in: body
        type: string
        description: The total PO amount.
      steps:
      - name: get-po
        type: call
        call: sap.get-purchase-order
        with:
          po_number: '{{po_number}}'
      - name: get-approver
        type: call
        call: peoplesoft.get-manager
        with:
          employee_id: '{{requestor_id}}'
      - name: notify-approver
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{get-approver.manager_email}}'
          text: 'PO Approval Required: PO {{po_number}} for {{spend_amount}} from {{get-po.vendor_name}}. Please review and approve.'
      - name: notify-requestor
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{get-approver.employee_email}}'
          text: Your PO {{po_number}} ({{spend_amount}}) has been routed to {{get-approver.manager_name}} for approval.
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/MM_PUR_PO_MAINT_V2_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: purchase-orders
      path: /A_PurchaseOrder('{{po_number}}')
      inputParameters:
      - name: po_number
        in: path
      operations:
      - name: get-purchase-order
        method: GET
  - type: http
    namespace: peoplesoft
    baseUri: https://peoplesoft.adidas.com/psftapi/v1
    authentication:
      type: basic
      username: $secrets.peoplesoft_user
      password: $secrets.peoplesoft_password
    resources:
    - name: employees
      path: /employees/{{employee_id}}/manager
      inputParameters:
      - name: employee_id
        in: path
      operations:
      - name: get-manager
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves a HubSpot CRM contact by email address and returns lifecycle stage, last activity date, and deal associations.

naftiko: '0.5'
info:
  label: HubSpot Contact Lookup
  description: Retrieves a HubSpot CRM contact by email address and returns lifecycle stage, last activity date, and deal associations.
  tags:
  - crm
  - hubspot
  - contacts
capability:
  exposes:
  - type: mcp
    namespace: crm
    port: 8080
    tools:
    - name: get-contact-by-email
      description: Look up a HubSpot contact by email and return lifecycle stage, last activity, and associated deals.
      inputParameters:
      - name: email
        in: body
        type: string
        description: The contact email address.
      call: hubspot.get-contact
      with:
        email: '{{email}}'
      outputParameters:
      - name: lifecycle_stage
        type: string
        mapping: $.properties.lifecyclestage
      - name: last_activity
        type: string
        mapping: $.properties.notes_last_updated
      - name: deal_count
        type: string
        mapping: $.properties.num_associated_deals
  consumes:
  - type: http
    namespace: hubspot
    baseUri: https://api.hubapi.com/crm/v3
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: contacts
      path: /objects/contacts/{{email}}
      inputParameters:
      - name: email
        in: path
      - name: idProperty
        in: query
        value: email
      operations:
      - name: get-contact
        method: GET

Forecasts volume from Snowflake, optimizes shifts in Workday, syncs schedules to SAP, updates Grafana dashboards, and notifies warehouse managers.

naftiko: '0.5'
info:
  label: Warehouse Labor Scheduling Pipeline
  description: Forecasts volume from Snowflake, optimizes shifts in Workday, syncs schedules to SAP, updates Grafana dashboards, and notifies warehouse managers.
  tags:
  - logistics
  - snowflake
  - workday
  - sap
  - grafana
capability:
  exposes:
  - type: mcp
    namespace: logistics
    port: 8080
    tools:
    - name: warehouse_labor_scheduling_pipeline
      description: Orchestrate warehouse labor scheduling pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-snowflake
        type: call
        call: snowflake.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-workday
        type: call
        call: workday.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-sap
        type: call
        call: sap.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-grafana
        type: call
        call: grafana.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: workday
    baseUri: https://wd5-impl-services1.workday.com/ccx/api/v1/adidas
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: workday-op
        method: POST
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: grafana
    baseUri: https://adidas-grafana.com/api
    authentication:
      type: bearer
      token: $secrets.grafana_api_key
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: grafana-op
        method: POST

Analyzes market data in Snowflake, evaluates regulatory requirements, creates business case in Confluence-equivalent, and notifies strategy team.

naftiko: '0.5'
info:
  label: New Market Entry Assessment
  description: Analyzes market data in Snowflake, evaluates regulatory requirements, creates business case in Confluence-equivalent, and notifies strategy team.
  tags:
  - strategy
  - snowflake
  - salesforce
  - jira
  - slack
capability:
  exposes:
  - type: mcp
    namespace: strategy
    port: 8080
    tools:
    - name: new_market_entry_assessment
      description: Orchestrate new market entry assessment workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-snowflake
        type: call
        call: snowflake.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-salesforce
        type: call
        call: salesforce.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-jira
        type: call
        call: jira.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Orchestrates creative asset production by uploading a design brief to Box, triggering an Adobe Creative Cloud workflow, and publishing the final asset to SharePoint and Notion.

naftiko: '0.5'
info:
  label: Content Asset Production Pipeline
  description: Orchestrates creative asset production by uploading a design brief to Box, triggering an Adobe Creative Cloud workflow, and publishing the final asset to SharePoint and Notion.
  tags:
  - creative
  - content-production
  - box
  - adobe-creative-cloud
  - sharepoint
  - notion
capability:
  exposes:
  - type: mcp
    namespace: content-production
    port: 8080
    tools:
    - name: produce-asset
      description: Given an asset brief, upload to Box, trigger creative workflow, and publish to SharePoint and Notion.
      inputParameters:
      - name: brief_title
        in: body
        type: string
        description: Title of the creative brief.
      - name: campaign_name
        in: body
        type: string
        description: The marketing campaign name.
      - name: asset_type
        in: body
        type: string
        description: Type of asset (banner, video, social, email).
      steps:
      - name: upload-brief
        type: call
        call: box.upload-file
        with:
          folder_id: $secrets.creative_briefs_folder
          file_name: '{{brief_title}}_brief.pdf'
          campaign: '{{campaign_name}}'
      - name: trigger-creative
        type: call
        call: adobe-cc.start-workflow
        with:
          workflow_template: '{{asset_type}}_production'
          brief_url: '{{upload-brief.shared_link}}'
          campaign: '{{campaign_name}}'
      - name: publish-sharepoint
        type: call
        call: sharepoint.upload-file
        with:
          site_id: marketing_assets
          folder_path: Campaigns/{{campaign_name}}/{{asset_type}}
          file_url: '{{trigger-creative.output_url}}'
      - name: log-in-notion
        type: call
        call: notion.create-page
        with:
          parent_id: $secrets.creative_tracker_db
          title: '{{brief_title}}'
          properties_campaign: '{{campaign_name}}'
          properties_type: '{{asset_type}}'
          properties_sharepoint_url: '{{publish-sharepoint.url}}'
  consumes:
  - type: http
    namespace: box
    baseUri: https://api.box.com/2.0
    authentication:
      type: bearer
      token: $secrets.box_token
    resources:
    - name: files
      path: /files/content
      operations:
      - name: upload-file
        method: POST
  - type: http
    namespace: adobe-cc
    baseUri: https://cc-api.adobe.io/v1
    authentication:
      type: bearer
      token: $secrets.adobe_cc_token
    resources:
    - name: workflows
      path: /workflows
      operations:
      - name: start-workflow
        method: POST
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: drive-items
      path: /{{site_id}}/drive/root:/{{folder_path}}
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      operations:
      - name: upload-file
        method: PUT
  - type: http
    namespace: notion
    baseUri: https://api.notion.com/v1
    authentication:
      type: bearer
      token: $secrets.notion_token
    inputParameters:
    - name: Notion-Version
      in: header
      value: '2022-06-28'
    resources:
    - name: pages
      path: /pages
      operations:
      - name: create-page
        method: POST

Queries Microsoft Power Automate for failed flow runs, creates ServiceNow incidents for each failure, and posts a summary to Microsoft Teams.

naftiko: '0.5'
info:
  label: Power Automate Workflow Status Reporter
  description: Queries Microsoft Power Automate for failed flow runs, creates ServiceNow incidents for each failure, and posts a summary to Microsoft Teams.
  tags:
  - automation
  - microsoft-power-automate
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: rpa-ops
    port: 8080
    tools:
    - name: report-failed-flows
      description: Given a date range, find all failed Power Automate flows, create incidents, and summarize in Teams.
      inputParameters:
      - name: date_from
        in: body
        type: string
        description: Start date for the search in YYYY-MM-DD format.
      - name: date_to
        in: body
        type: string
        description: End date for the search in YYYY-MM-DD format.
      steps:
      - name: get-failed-runs
        type: call
        call: power-automate.list-failed-runs
        with:
          date_from: '{{date_from}}'
          date_to: '{{date_to}}'
      - name: create-incidents
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Power Automate failure: {{get-failed-runs.flow_name}}'
          category: automation
          priority: '3'
          description: 'Flow: {{get-failed-runs.flow_name}} | Run ID: {{get-failed-runs.run_id}} | Error: {{get-failed-runs.error_message}}'
      - name: post-summary
        type: call
        call: msteams.send-message
        with:
          channel: automation-ops
          text: 'Power Automate Failure Summary ({{date_from}} to {{date_to}}): {{get-failed-runs.total_failures}} failed runs | Incident: {{create-incidents.number}}'
  consumes:
  - type: http
    namespace: power-automate
    baseUri: https://api.flow.microsoft.com/providers/Microsoft.ProcessSimple
    authentication:
      type: bearer
      token: $secrets.power_automate_token
    resources:
    - name: flow-runs
      path: /environments/$secrets.pa_environment_id/flows
      operations:
      - name: list-failed-runs
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

Collects vendor delivery data from SAP, calculates scores in Snowflake, updates Salesforce vendor records, and notifies procurement.

naftiko: '0.5'
info:
  label: Vendor Performance Scorecard Pipeline
  description: Collects vendor delivery data from SAP, calculates scores in Snowflake, updates Salesforce vendor records, and notifies procurement.
  tags:
  - procurement
  - sap
  - snowflake
  - salesforce
  - slack
capability:
  exposes:
  - type: mcp
    namespace: procurement
    port: 8080
    tools:
    - name: vendor_performance_scorecard_pipeline
      description: Orchestrate vendor performance scorecard pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-salesforce
        type: call
        call: salesforce.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Retrieves a Zendesk support ticket by ID including status, priority, assignee, and customer satisfaction rating. Used by customer service managers.

naftiko: '0.5'
info:
  label: Zendesk Ticket Lookup
  description: Retrieves a Zendesk support ticket by ID including status, priority, assignee, and customer satisfaction rating. Used by customer service managers.
  tags:
  - customer-service
  - zendesk
  - support
capability:
  exposes:
  - type: mcp
    namespace: support
    port: 8080
    tools:
    - name: get-ticket
      description: Look up a Zendesk support ticket and return its status, priority, assignee, and satisfaction rating.
      inputParameters:
      - name: ticket_id
        in: body
        type: string
        description: The Zendesk ticket ID.
      call: zendesk.get-ticket
      with:
        ticket_id: '{{ticket_id}}'
      outputParameters:
      - name: status
        type: string
        mapping: $.ticket.status
      - name: priority
        type: string
        mapping: $.ticket.priority
      - name: assignee
        type: string
        mapping: $.ticket.assignee_id
      - name: satisfaction_rating
        type: string
        mapping: $.ticket.satisfaction_rating.score
  consumes:
  - type: http
    namespace: zendesk
    baseUri: https://adidas.zendesk.com/api/v2
    authentication:
      type: bearer
      token: $secrets.zendesk_token
    resources:
    - name: tickets
      path: /tickets/{{ticket_id}}.json
      inputParameters:
      - name: ticket_id
        in: path
      operations:
      - name: get-ticket
        method: GET

Retrieves a Stripe payment intent by ID and returns amount, status, currency, and last four digits of the card used. Used by finance operations.

naftiko: '0.5'
info:
  label: Stripe Payment Lookup
  description: Retrieves a Stripe payment intent by ID and returns amount, status, currency, and last four digits of the card used. Used by finance operations.
  tags:
  - finance
  - stripe
  - payments
capability:
  exposes:
  - type: mcp
    namespace: payments
    port: 8080
    tools:
    - name: get-payment
      description: Look up a Stripe payment intent by ID and return its amount, status, and payment method details.
      inputParameters:
      - name: payment_intent_id
        in: body
        type: string
        description: The Stripe payment intent ID (e.g. pi_xxx).
      call: stripe.get-payment-intent
      with:
        payment_intent_id: '{{payment_intent_id}}'
      outputParameters:
      - name: amount
        type: string
        mapping: $.amount
      - name: currency
        type: string
        mapping: $.currency
      - name: status
        type: string
        mapping: $.status
      - name: card_last4
        type: string
        mapping: $.payment_method.card.last4
  consumes:
  - type: http
    namespace: stripe
    baseUri: https://api.stripe.com/v1
    authentication:
      type: bearer
      token: $secrets.stripe_secret_key
    resources:
    - name: payment-intents
      path: /payment_intents/{{payment_intent_id}}
      inputParameters:
      - name: payment_intent_id
        in: path
      operations:
      - name: get-payment-intent
        method: GET

Collects influencer metrics from social APIs, calculates ROI in Snowflake, updates HubSpot campaigns, and notifies the brand team.

naftiko: '0.5'
info:
  label: Influencer Campaign ROI Calculator
  description: Collects influencer metrics from social APIs, calculates ROI in Snowflake, updates HubSpot campaigns, and notifies the brand team.
  tags:
  - marketing
  - hubspot
  - snowflake
  - powerbi
  - slack
capability:
  exposes:
  - type: mcp
    namespace: marketing
    port: 8080
    tools:
    - name: influencer_campaign_roi_calculator
      description: Orchestrate influencer campaign roi calculator workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-hubspot
        type: call
        call: hubspot.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-slack
        type: call
        call: slack.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-servicenow
        type: call
        call: servicenow.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: hubspot
    baseUri: https://api.hubapi.com
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: hubspot-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST

Retrieves Salesforce account details for Adidas sales teams.

naftiko: '0.5'
info:
  label: Salesforce Account Info
  description: Retrieves Salesforce account details for Adidas sales teams.
  tags:
  - crm
  - salesforce
  - accounts
capability:
  exposes:
  - type: mcp
    namespace: crm
    port: 8080
    tools:
    - name: get-account
      description: Look up account at Adidas.
      inputParameters:
      - name: account_id
        in: body
        type: string
        description: The account_id to look up.
      call: salesforce.get-account_id
      with:
        account_id: '{{account_id}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce_account_info
        method: GET

Pulls campaign spend from Adobe Campaign, payment data from Stripe, and reconciles against the budget in SAP BW, then updates a Microsoft Excel tracker on SharePoint.

naftiko: '0.5'
info:
  label: Marketing Budget Tracker Sync
  description: Pulls campaign spend from Adobe Campaign, payment data from Stripe, and reconciles against the budget in SAP BW, then updates a Microsoft Excel tracker on SharePoint.
  tags:
  - finance
  - marketing
  - adobe-campaign
  - stripe
  - sap-bw
  - microsoft-excel
  - sharepoint
capability:
  exposes:
  - type: mcp
    namespace: budget-tracking
    port: 8080
    tools:
    - name: sync-marketing-budget
      description: Given a campaign ID and fiscal period, pull spend data from all channels and reconcile against budget.
      inputParameters:
      - name: campaign_id
        in: body
        type: string
        description: The marketing campaign identifier.
      - name: fiscal_period
        in: body
        type: string
        description: The fiscal period (e.g. 2026-Q1).
      steps:
      - name: get-campaign-spend
        type: call
        call: adobe-campaign.get-delivery-stats
        with:
          campaign_id: '{{campaign_id}}'
      - name: get-payment-totals
        type: call
        call: stripe.get-balance-transactions
        with:
          campaign_reference: '{{campaign_id}}'
          period: '{{fiscal_period}}'
      - name: get-budget
        type: call
        call: sap-bw.get-budget-allocation
        with:
          cost_center: marketing
          period: '{{fiscal_period}}'
      - name: update-excel
        type: call
        call: sharepoint.update-excel-range
        with:
          site_id: finance_reports
          workbook_path: Budgets/Marketing_{{fiscal_period}}.xlsx
          range: Summary!A2
          values: '{{campaign_id}},{{get-campaign-spend.total_cost}},{{get-payment-totals.net_amount}},{{get-budget.allocated}},{{get-budget.remaining}}'
  consumes:
  - type: http
    namespace: adobe-campaign
    baseUri: https://mc.adobe.io/adidas/campaign
    authentication:
      type: bearer
      token: $secrets.adobe_campaign_token
    resources:
    - name: deliveries
      path: /deliveries/{{campaign_id}}/stats
      inputParameters:
      - name: campaign_id
        in: path
      operations:
      - name: get-delivery-stats
        method: GET
  - type: http
    namespace: stripe
    baseUri: https://api.stripe.com/v1
    authentication:
      type: bearer
      token: $secrets.stripe_secret_key
    resources:
    - name: balance-transactions
      path: /balance_transactions
      operations:
      - name: get-balance-transactions
        method: GET
  - type: http
    namespace: sap-bw
    baseUri: https://adidas-bw.sap.com/sap/bw/odata/v1
    authentication:
      type: basic
      username: $secrets.sap_bw_user
      password: $secrets.sap_bw_password
    resources:
    - name: budgets
      path: /ZBUDGET_ALLOCATION
      operations:
      - name: get-budget-allocation
        method: GET
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0/sites
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: excel
      path: /{{site_id}}/drive/root:/{{workbook_path}}:/workbook/worksheets/{{range}}
      inputParameters:
      - name: site_id
        in: path
      - name: workbook_path
        in: path
      - name: range
        in: path
      operations:
      - name: update-excel-range
        method: PATCH

Retrieves page-level performance metrics from Adobe Analytics for a specified report suite and page path.

naftiko: '0.5'
info:
  label: Adobe Analytics Page Performance
  description: Retrieves page-level performance metrics from Adobe Analytics for a specified report suite and page path.
  tags:
  - analytics
  - adobe-analytics
  - ecommerce
capability:
  exposes:
  - type: mcp
    namespace: digital-analytics
    port: 8080
    tools:
    - name: get-page-performance
      description: Query Adobe Analytics for page views, bounce rate, and average time on page for a given URL path.
      inputParameters:
      - name: report_suite_id
        in: body
        type: string
        description: The Adobe Analytics report suite ID.
      - name: page_path
        in: body
        type: string
        description: The URL path to analyze.
      call: adobe-analytics.get-report
      with:
        report_suite_id: '{{report_suite_id}}'
        page_path: '{{page_path}}'
      outputParameters:
      - name: page_views
        type: string
        mapping: $.rows[0].data[0]
      - name: bounce_rate
        type: string
        mapping: $.rows[0].data[1]
      - name: avg_time_on_page
        type: string
        mapping: $.rows[0].data[2]
  consumes:
  - type: http
    namespace: adobe-analytics
    baseUri: https://analytics.adobe.io/api/adidas/reports
    authentication:
      type: bearer
      token: $secrets.adobe_analytics_token
    inputParameters:
    - name: x-api-key
      in: header
      value: $secrets.adobe_client_id
    resources:
    - name: reports
      path: /ranked
      operations:
      - name: get-report
        method: POST

On a GitHub Actions pipeline failure, creates a Datadog event marker, opens a ServiceNow incident, and alerts the engineering team in Microsoft Teams.

naftiko: '0.5'
info:
  label: CI/CD Pipeline Failure Handler
  description: On a GitHub Actions pipeline failure, creates a Datadog event marker, opens a ServiceNow incident, and alerts the engineering team in Microsoft Teams.
  tags:
  - devops
  - github-actions
  - datadog
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: devops
    port: 8080
    tools:
    - name: handle-pipeline-failure
      description: Given a pipeline run ID, repo, and branch, create observability marker, open incident, and alert the team.
      inputParameters:
      - name: run_id
        in: body
        type: string
        description: The GitHub Actions workflow run ID.
      - name: repository
        in: body
        type: string
        description: The GitHub repository (org/repo format).
      - name: branch
        in: body
        type: string
        description: The branch that failed.
      - name: failed_job
        in: body
        type: string
        description: Name of the failed job.
      steps:
      - name: create-dd-event
        type: call
        call: datadog.create-event
        with:
          title: 'Pipeline Failure: {{repository}} / {{branch}}'
          text: 'Run ID: {{run_id}} | Job: {{failed_job}}'
          alert_type: error
          tags: repo:{{repository}},branch:{{branch}}
      - name: open-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: '[CI Failure] {{repository}} / {{branch}} — {{failed_job}}'
          category: software
          priority: '3'
          description: 'GitHub Actions run {{run_id}} failed on {{branch}} in {{repository}}. Job: {{failed_job}}.'
      - name: alert-team
        type: call
        call: msteams.send-message
        with:
          channel: engineering-alerts
          text: 'Pipeline Failure: {{repository}} | Branch: {{branch}} | Job: {{failed_job}} | Incident: {{open-incident.number}} | Run: https://github.com/{{repository}}/actions/runs/{{run_id}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: bearer
      token: $secrets.datadog_api_key
    inputParameters:
    - name: DD-APPLICATION-KEY
      in: header
      value: $secrets.datadog_app_key
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

When SAP S/4HANA detects inventory below safety stock, generates a purchase requisition, notifies the procurement team in Teams, and logs it in a Google Sheet tracker.

naftiko: '0.5'
info:
  label: Warehouse Replenishment Orchestrator
  description: When SAP S/4HANA detects inventory below safety stock, generates a purchase requisition, notifies the procurement team in Teams, and logs it in a Google Sheet tracker.
  tags:
  - supply-chain
  - replenishment
  - sap-s4hana
  - microsoft-teams
  - google-sheets
capability:
  exposes:
  - type: mcp
    namespace: replenishment
    port: 8080
    tools:
    - name: trigger-replenishment
      description: Given a material number and plant, create a purchase requisition, notify procurement, and log the event.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number.
      - name: plant
        in: body
        type: string
        description: The SAP plant code.
      - name: current_stock
        in: body
        type: string
        description: Current on-hand quantity.
      - name: reorder_quantity
        in: body
        type: string
        description: Quantity to reorder.
      steps:
      - name: create-pr
        type: call
        call: sap.create-purchase-requisition
        with:
          material: '{{material_number}}'
          plant: '{{plant}}'
          quantity: '{{reorder_quantity}}'
          requisition_type: NB
      - name: notify-procurement
        type: call
        call: msteams.send-message
        with:
          channel: procurement-alerts
          text: 'Replenishment Alert: Material {{material_number}} at plant {{plant}} is below safety stock ({{current_stock}} on hand). PR {{create-pr.requisition_number}} created for {{reorder_quantity}} units.'
      - name: log-event
        type: call
        call: gsheets.append-row
        with:
          spreadsheet_id: $secrets.replenishment_tracker_sheet
          range: Log!A1
          values: '{{material_number}},{{plant}},{{current_stock}},{{reorder_quantity}},{{create-pr.requisition_number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/API_PURCHASEREQ_PROCESS_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: requisitions
      path: /A_PurchaseReqnHeader
      operations:
      - name: create-purchase-requisition
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST
  - type: http
    namespace: gsheets
    baseUri: https://sheets.googleapis.com/v4/spreadsheets
    authentication:
      type: bearer
      token: $secrets.google_sheets_token
    resources:
    - name: values
      path: /{{spreadsheet_id}}/values/{{range}}:append
      inputParameters:
      - name: spreadsheet_id
        in: path
      - name: range
        in: path
      operations:
      - name: append-row
        method: POST

Retrieves promo plan from Salesforce, validates margins in Snowflake, updates SAP pricing, syncs to e-commerce, and notifies merchandising.

naftiko: '0.5'
info:
  label: Promotional Pricing Orchestrator
  description: Retrieves promo plan from Salesforce, validates margins in Snowflake, updates SAP pricing, syncs to e-commerce, and notifies merchandising.
  tags:
  - pricing
  - salesforce
  - snowflake
  - sap
  - slack
capability:
  exposes:
  - type: mcp
    namespace: pricing
    port: 8080
    tools:
    - name: promotional_pricing_orchestrator
      description: Orchestrate promotional pricing orchestrator workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-salesforce
        type: call
        call: salesforce.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-sap
        type: call
        call: sap.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Monitors checkout funnel in Datadog, analyzes drop-off in Snowflake, runs A/B test analysis, creates Jira improvements, and notifies product team.

naftiko: '0.5'
info:
  label: E-Commerce Checkout Optimization
  description: Monitors checkout funnel in Datadog, analyzes drop-off in Snowflake, runs A/B test analysis, creates Jira improvements, and notifies product team.
  tags:
  - e-commerce
  - datadog
  - snowflake
  - jira
  - slack
capability:
  exposes:
  - type: mcp
    namespace: e-commerce
    port: 8080
    tools:
    - name: e_commerce_checkout_optimization
      description: Orchestrate e-commerce checkout optimization workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-datadog
        type: call
        call: datadog.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-jira
        type: call
        call: jira.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apiKey
      key: $secrets.datadog_api_key
      header: DD-API-KEY
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: datadog-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Monitors warehouse KPIs from SAP, analyzes bottlenecks in Snowflake, creates improvement tasks in Jira, updates Grafana dashboards, and alerts ops.

naftiko: '0.5'
info:
  label: Warehouse Operations Optimization
  description: Monitors warehouse KPIs from SAP, analyzes bottlenecks in Snowflake, creates improvement tasks in Jira, updates Grafana dashboards, and alerts ops.
  tags:
  - logistics
  - sap
  - snowflake
  - jira
  - grafana
capability:
  exposes:
  - type: mcp
    namespace: logistics
    port: 8080
    tools:
    - name: warehouse_operations_optimization
      description: Orchestrate warehouse operations optimization workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-jira
        type: call
        call: jira.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-grafana
        type: call
        call: grafana.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira-op
        method: POST
  - type: http
    namespace: grafana
    baseUri: https://adidas-grafana.com/api
    authentication:
      type: bearer
      token: $secrets.grafana_api_key
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: grafana-op
        method: POST

Searches Splunk indexes for log entries at Adidas.

naftiko: '0.5'
info:
  label: Splunk Log Search
  description: Searches Splunk indexes for log entries at Adidas.
  tags:
  - devops
  - splunk
  - logging
capability:
  exposes:
  - type: mcp
    namespace: logging
    port: 8080
    tools:
    - name: search-logs
      description: Search Splunk logs for Adidas.
      inputParameters:
      - name: query
        in: body
        type: string
        description: The query to look up.
      call: splunk.get-query
      with:
        query: '{{query}}'
  consumes:
  - type: http
    namespace: splunk
    baseUri: https://adidas-splunk.com/services
    authentication:
      type: bearer
      token: $secrets.splunk_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: splunk_log_search
        method: GET

On a new product launch, creates an Adobe Campaign email blast, posts to Instagram and Facebook, updates the BigCommerce storefront, and sends an internal Teams notification.

naftiko: '0.5'
info:
  label: New Product Launch Campaign Orchestrator
  description: On a new product launch, creates an Adobe Campaign email blast, posts to Instagram and Facebook, updates the BigCommerce storefront, and sends an internal Teams notification.
  tags:
  - marketing
  - product-launch
  - adobe-campaign
  - instagram
  - facebook
  - bigcommerce
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: product-launch
    port: 8080
    tools:
    - name: orchestrate-launch
      description: Given a product ID, campaign name, and launch date, coordinate the full product launch across marketing channels and the e-commerce storefront.
      inputParameters:
      - name: product_id
        in: body
        type: string
        description: The Adidas product ID for the new launch.
      - name: campaign_name
        in: body
        type: string
        description: The name of the marketing campaign.
      - name: launch_date
        in: body
        type: string
        description: The scheduled launch date in YYYY-MM-DD format.
      steps:
      - name: create-email-campaign
        type: call
        call: adobe-campaign.create-delivery
        with:
          campaign_name: '{{campaign_name}}'
          template: product_launch_v2
          scheduled_date: '{{launch_date}}'
          product_id: '{{product_id}}'
      - name: post-instagram
        type: call
        call: instagram.create-media
        with:
          caption: 'The wait is over. {{campaign_name}} drops {{launch_date}}. Link in bio. #adidas #newdrop'
          product_id: '{{product_id}}'
      - name: post-facebook
        type: call
        call: facebook.create-post
        with:
          message: Introducing {{campaign_name}} - available {{launch_date}} on adidas.com and in stores.
          product_id: '{{product_id}}'
      - name: update-storefront
        type: call
        call: bigcommerce.update-product-visibility
        with:
          product_id: '{{product_id}}'
          is_visible: 'true'
          availability_date: '{{launch_date}}'
      - name: notify-team
        type: call
        call: msteams.send-message
        with:
          channel: product-launches
          text: 'Product launch orchestrated: {{campaign_name}} | Product: {{product_id}} | Email: {{create-email-campaign.delivery_id}} | IG: {{post-instagram.media_id}} | FB: {{post-facebook.post_id}} | Store: live on {{launch_date}}'
  consumes:
  - type: http
    namespace: adobe-campaign
    baseUri: https://mc.adobe.io/adidas/campaign
    authentication:
      type: bearer
      token: $secrets.adobe_campaign_token
    inputParameters:
    - name: x-api-key
      in: header
      value: $secrets.adobe_client_id
    resources:
    - name: deliveries
      path: /deliveries
      operations:
      - name: create-delivery
        method: POST
  - type: http
    namespace: instagram
    baseUri: https://graph.facebook.com/v18.0
    authentication:
      type: bearer
      token: $secrets.instagram_token
    resources:
    - name: media
      path: /{{ig_user_id}}/media
      operations:
      - name: create-media
        method: POST
  - type: http
    namespace: facebook
    baseUri: https://graph.facebook.com/v18.0
    authentication:
      type: bearer
      token: $secrets.facebook_page_token
    resources:
    - name: posts
      path: /{{page_id}}/feed
      operations:
      - name: create-post
        method: POST
  - type: http
    namespace: bigcommerce
    baseUri: https://api.bigcommerce.com/stores/adidas/v3
    authentication:
      type: bearer
      token: $secrets.bigcommerce_token
    resources:
    - name: products
      path: /catalog/products/{{product_id}}
      inputParameters:
      - name: product_id
        in: path
      operations:
      - name: update-product-visibility
        method: PUT
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

Provisions store in SAP, creates Salesforce location record, sets up ServiceNow IT support, assigns staff in Workday, and notifies retail operations.

naftiko: '0.5'
info:
  label: Store Opening Orchestrator
  description: Provisions store in SAP, creates Salesforce location record, sets up ServiceNow IT support, assigns staff in Workday, and notifies retail operations.
  tags:
  - retail
  - sap
  - salesforce
  - servicenow
  - workday
capability:
  exposes:
  - type: mcp
    namespace: retail
    port: 8080
    tools:
    - name: store_opening_orchestrator
      description: Orchestrate store opening orchestrator workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-salesforce
        type: call
        call: salesforce.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-servicenow
        type: call
        call: servicenow.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-workday
        type: call
        call: workday.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST
  - type: http
    namespace: workday
    baseUri: https://wd5-impl-services1.workday.com/ccx/api/v1/adidas
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: workday-op
        method: POST

Searches Elasticsearch indexes for Adidas.

naftiko: '0.5'
info:
  label: Elasticsearch Log Query
  description: Searches Elasticsearch indexes for Adidas.
  tags:
  - data
  - elasticsearch
  - search
capability:
  exposes:
  - type: mcp
    namespace: search
    port: 8080
    tools:
    - name: search-logs
      description: Search ES logs at Adidas.
      inputParameters:
      - name: query
        in: body
        type: string
        description: The query to look up.
      call: elasticsearch.get-query
      with:
        query: '{{query}}'
  consumes:
  - type: http
    namespace: elasticsearch
    baseUri: https://adidas-es.com:9200
    authentication:
      type: bearer
      token: $secrets.elasticsearch_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: elasticsearch_log_query
        method: GET

Detects high-priority Zendesk tickets, enriches with customer data from Salesforce, creates escalation in ServiceNow, and notifies management.

naftiko: '0.5'
info:
  label: Customer Service Escalation Pipeline
  description: Detects high-priority Zendesk tickets, enriches with customer data from Salesforce, creates escalation in ServiceNow, and notifies management.
  tags:
  - customer-service
  - zendesk
  - salesforce
  - servicenow
  - slack
capability:
  exposes:
  - type: mcp
    namespace: customer-service
    port: 8080
    tools:
    - name: customer_service_escalation_pipeline
      description: Orchestrate customer service escalation pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-zendesk
        type: call
        call: zendesk.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-salesforce
        type: call
        call: salesforce.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-servicenow
        type: call
        call: servicenow.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: zendesk
    baseUri: https://adidas.zendesk.com/api/v2
    authentication:
      type: bearer
      token: $secrets.zendesk_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: zendesk-op
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Collects carbon footprint data from SAP, energy usage from Oracle Cloud, and supply chain metrics from SAP BW, then publishes a sustainability dashboard to Google Sheets and notifies leadership in Teams.

naftiko: '0.5'
info:
  label: Sustainability Reporting Pipeline
  description: Collects carbon footprint data from SAP, energy usage from Oracle Cloud, and supply chain metrics from SAP BW, then publishes a sustainability dashboard to Google Sheets and notifies leadership in Teams.
  tags:
  - sustainability
  - sap-s4hana
  - oracle-cloud
  - sap-bw
  - google-sheets
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: sustainability
    port: 8080
    tools:
    - name: generate-sustainability-report
      description: Given a fiscal period, collect sustainability metrics from all sources and publish a consolidated report.
      inputParameters:
      - name: fiscal_period
        in: body
        type: string
        description: The fiscal period (e.g. 2026-Q1).
      - name: spreadsheet_id
        in: body
        type: string
        description: Google Sheets ID for the sustainability dashboard.
      steps:
      - name: get-carbon-data
        type: call
        call: sap.get-carbon-footprint
        with:
          period: '{{fiscal_period}}'
      - name: get-energy-usage
        type: call
        call: oracle-cloud.get-energy-metrics
        with:
          period: '{{fiscal_period}}'
      - name: get-supply-chain-metrics
        type: call
        call: sap-bw.get-sustainability-kpis
        with:
          period: '{{fiscal_period}}'
      - name: update-dashboard
        type: call
        call: gsheets.update-range
        with:
          spreadsheet_id: '{{spreadsheet_id}}'
          range: Dashboard!A2
          values: '{{fiscal_period}},{{get-carbon-data.total_co2_tons}},{{get-energy-usage.kwh_total}},{{get-supply-chain-metrics.recycled_materials_pct}},{{get-supply-chain-metrics.sustainable_suppliers_pct}}'
      - name: notify-leadership
        type: call
        call: msteams.send-message
        with:
          channel: sustainability-leadership
          text: 'Sustainability Report: {{fiscal_period}} | CO2: {{get-carbon-data.total_co2_tons}} tons | Energy: {{get-energy-usage.kwh_total}} kWh | Recycled Materials: {{get-supply-chain-metrics.recycled_materials_pct}}% | Sustainable Suppliers: {{get-supply-chain-metrics.sustainable_suppliers_pct}}%'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/API_SUSTAINABILITY_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: carbon
      path: /A_CarbonFootprint
      operations:
      - name: get-carbon-footprint
        method: GET
  - type: http
    namespace: oracle-cloud
    baseUri: https://cloud.oracle.com/api/v1
    authentication:
      type: bearer
      token: $secrets.oracle_cloud_token
    resources:
    - name: energy
      path: /sustainability/energy
      operations:
      - name: get-energy-metrics
        method: GET
  - type: http
    namespace: sap-bw
    baseUri: https://adidas-bw.sap.com/sap/bw/odata/v1
    authentication:
      type: basic
      username: $secrets.sap_bw_user
      password: $secrets.sap_bw_password
    resources:
    - name: sustainability
      path: /ZSUSTAINABILITY_KPI
      operations:
      - name: get-sustainability-kpis
        method: GET
  - type: http
    namespace: gsheets
    baseUri: https://sheets.googleapis.com/v4/spreadsheets
    authentication:
      type: bearer
      token: $secrets.google_sheets_token
    resources:
    - name: values
      path: /{{spreadsheet_id}}/values/{{range}}
      inputParameters:
      - name: spreadsheet_id
        in: path
      - name: range
        in: path
      operations:
      - name: update-range
        method: PUT
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

When a Salesforce opportunity is marked as Closed Won, creates a sales order in SAP S/4HANA, updates the Salesforce record with the SAP order number, and notifies the fulfillment team in Teams.

naftiko: '0.5'
info:
  label: Salesforce to SAP Order Sync
  description: When a Salesforce opportunity is marked as Closed Won, creates a sales order in SAP S/4HANA, updates the Salesforce record with the SAP order number, and notifies the fulfillment team in Teams.
  tags:
  - sales
  - salesforce
  - sap-s4hana
  - microsoft-teams
  - order-management
capability:
  exposes:
  - type: mcp
    namespace: order-sync
    port: 8080
    tools:
    - name: sync-won-opportunity
      description: Given a Salesforce opportunity ID, create a SAP sales order, update SF with the order number, and notify fulfillment.
      inputParameters:
      - name: opportunity_id
        in: body
        type: string
        description: The Salesforce opportunity ID.
      steps:
      - name: get-opportunity
        type: call
        call: salesforce.get-opportunity
        with:
          opportunity_id: '{{opportunity_id}}'
      - name: create-sales-order
        type: call
        call: sap.create-sales-order
        with:
          customer_id: '{{get-opportunity.account_sap_id}}'
          amount: '{{get-opportunity.amount}}'
          products: '{{get-opportunity.line_items}}'
          delivery_date: '{{get-opportunity.close_date}}'
      - name: update-salesforce
        type: call
        call: salesforce.update-opportunity
        with:
          opportunity_id: '{{opportunity_id}}'
          sap_order_number: '{{create-sales-order.order_number}}'
      - name: notify-fulfillment
        type: call
        call: msteams.send-message
        with:
          channel: fulfillment-ops
          text: 'New Sales Order: SAP {{create-sales-order.order_number}} from SF Opportunity {{opportunity_id}} | Customer: {{get-opportunity.account_name}} | Amount: {{get-opportunity.amount}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: opportunities
      path: /sobjects/Opportunity/{{opportunity_id}}
      inputParameters:
      - name: opportunity_id
        in: path
      operations:
      - name: get-opportunity
        method: GET
      - name: update-opportunity
        method: PATCH
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/API_SALES_ORDER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: sales-orders
      path: /A_SalesOrder
      operations:
      - name: create-sales-order
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

Collects POS data from SAP, aggregates in Snowflake, refreshes Power BI dashboards, identifies underperformers, and notifies retail ops.

naftiko: '0.5'
info:
  label: Retail Store Performance Pipeline
  description: Collects POS data from SAP, aggregates in Snowflake, refreshes Power BI dashboards, identifies underperformers, and notifies retail ops.
  tags:
  - retail
  - sap
  - snowflake
  - powerbi
  - slack
capability:
  exposes:
  - type: mcp
    namespace: retail
    port: 8080
    tools:
    - name: retail_store_performance_pipeline
      description: Orchestrate retail store performance pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-slack
        type: call
        call: slack.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-servicenow
        type: call
        call: servicenow.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST

Executes SQL queries against Adidas Snowflake warehouse.

naftiko: '0.5'
info:
  label: Snowflake Query Executor
  description: Executes SQL queries against Adidas Snowflake warehouse.
  tags:
  - data
  - snowflake
  - analytics
capability:
  exposes:
  - type: mcp
    namespace: analytics
    port: 8080
    tools:
    - name: run-query
      description: Run query at Adidas.
      inputParameters:
      - name: sql_query
        in: body
        type: string
        description: The sql_query to look up.
      call: snowflake.get-sql_query
      with:
        sql_query: '{{sql_query}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake_query_executor
        method: GET

When a new employee joins a department, assigns the relevant Pluralsight learning path, creates a Microsoft Planner task for completion tracking, and notifies the manager in Teams.

naftiko: '0.5'
info:
  label: Pluralsight Learning Path Assignment
  description: When a new employee joins a department, assigns the relevant Pluralsight learning path, creates a Microsoft Planner task for completion tracking, and notifies the manager in Teams.
  tags:
  - learning
  - pluralsight
  - microsoft-planner
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: learning
    port: 8080
    tools:
    - name: assign-learning-path
      description: Given an employee email and department, assign the Pluralsight path, create a tracking task, and notify the manager.
      inputParameters:
      - name: employee_email
        in: body
        type: string
        description: The new employee email.
      - name: department
        in: body
        type: string
        description: The department the employee is joining.
      - name: manager_email
        in: body
        type: string
        description: The manager email for notification.
      steps:
      - name: assign-path
        type: call
        call: pluralsight.assign-channel
        with:
          user_email: '{{employee_email}}'
          channel_name: '{{department}}_onboarding'
      - name: create-task
        type: call
        call: planner.create-task
        with:
          plan_id: $secrets.learning_plan_id
          title: 'Complete Pluralsight path: {{department}}_onboarding'
          assigned_to: '{{employee_email}}'
          due_date: +30d
      - name: notify-manager
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{manager_email}}'
          text: 'Learning path assigned to {{employee_email}}: {{department}}_onboarding | Due in 30 days | Task: {{create-task.id}}'
  consumes:
  - type: http
    namespace: pluralsight
    baseUri: https://api.pluralsight.com/api/v1
    authentication:
      type: bearer
      token: $secrets.pluralsight_token
    resources:
    - name: channels
      path: /channels/assign
      operations:
      - name: assign-channel
        method: POST
  - type: http
    namespace: planner
    baseUri: https://graph.microsoft.com/v1.0/planner
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: tasks
      path: /tasks
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Creates a Salesforce campaign for a sponsored event, uploads the sponsorship agreement to Google Drive, schedules social media posts on Instagram and Twitter, and sets up a Planner task for follow-up.

naftiko: '0.5'
info:
  label: Event Sponsorship Tracker
  description: Creates a Salesforce campaign for a sponsored event, uploads the sponsorship agreement to Google Drive, schedules social media posts on Instagram and Twitter, and sets up a Planner task for follow-up.
  tags:
  - marketing
  - events
  - salesforce
  - google-drive
  - instagram
  - twitter
  - microsoft-planner
capability:
  exposes:
  - type: mcp
    namespace: event-sponsorship
    port: 8080
    tools:
    - name: setup-sponsorship
      description: Given event details and sponsorship terms, create campaign, store agreement, schedule social posts, and track follow-up.
      inputParameters:
      - name: event_name
        in: body
        type: string
        description: Name of the sponsored event.
      - name: event_date
        in: body
        type: string
        description: Event date in YYYY-MM-DD format.
      - name: sponsorship_amount
        in: body
        type: string
        description: Sponsorship investment amount.
      - name: sport_category
        in: body
        type: string
        description: Sport category for the event.
      steps:
      - name: create-campaign
        type: call
        call: salesforce.create-campaign
        with:
          name: 'Sponsorship: {{event_name}}'
          type: Event
          start_date: '{{event_date}}'
          budgeted_cost: '{{sponsorship_amount}}'
      - name: upload-agreement
        type: call
        call: gdrive.upload-file
        with:
          folder_id: $secrets.sponsorships_folder
          file_name: '{{event_name}}_agreement.pdf'
      - name: schedule-instagram
        type: call
        call: instagram.create-media
        with:
          caption: 'We''re proud to sponsor {{event_name}}! See you there. #adidas #{{sport_category}}'
          scheduled_date: '{{event_date}}'
      - name: schedule-twitter
        type: call
        call: twitter.create-tweet
        with:
          text: 'Adidas is the official sponsor of {{event_name}}. Game on. #adidas #{{sport_category}}'
      - name: create-followup-task
        type: call
        call: planner.create-task
        with:
          plan_id: $secrets.events_plan_id
          title: 'Post-event report: {{event_name}}'
          due_date: +7d
          description: 'Campaign: {{create-campaign.id}} | Agreement: {{upload-agreement.url}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: campaigns
      path: /sobjects/Campaign
      operations:
      - name: create-campaign
        method: POST
  - type: http
    namespace: gdrive
    baseUri: https://www.googleapis.com/upload/drive/v3
    authentication:
      type: bearer
      token: $secrets.google_drive_token
    resources:
    - name: files
      path: /files
      operations:
      - name: upload-file
        method: POST
  - type: http
    namespace: instagram
    baseUri: https://graph.facebook.com/v18.0
    authentication:
      type: bearer
      token: $secrets.instagram_token
    resources:
    - name: media
      path: /{{ig_user_id}}/media
      operations:
      - name: create-media
        method: POST
  - type: http
    namespace: twitter
    baseUri: https://api.twitter.com/2
    authentication:
      type: bearer
      token: $secrets.twitter_bearer_token
    resources:
    - name: tweets
      path: /tweets
      operations:
      - name: create-tweet
        method: POST
  - type: http
    namespace: planner
    baseUri: https://graph.microsoft.com/v1.0/planner
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: tasks
      path: /tasks
      operations:
      - name: create-task
        method: POST

Tracks touchpoints from Salesforce, web analytics from Datadog, purchase data from Stripe, aggregates in Snowflake, and notifies CX team.

naftiko: '0.5'
info:
  label: Customer Journey Analytics Pipeline
  description: Tracks touchpoints from Salesforce, web analytics from Datadog, purchase data from Stripe, aggregates in Snowflake, and notifies CX team.
  tags:
  - customer-experience
  - salesforce
  - datadog
  - snowflake
  - slack
capability:
  exposes:
  - type: mcp
    namespace: customer-experience
    port: 8080
    tools:
    - name: customer_journey_analytics_pipeline
      description: Orchestrate customer journey analytics pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-salesforce
        type: call
        call: salesforce.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-datadog
        type: call
        call: datadog.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-snowflake
        type: call
        call: snowflake.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apiKey
      key: $secrets.datadog_api_key
      header: DD-API-KEY
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: datadog-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Syncs inventory between SAP warehouse, Salesforce Commerce Cloud, and store POS systems, logs discrepancies in ServiceNow, and alerts supply chain.

naftiko: '0.5'
info:
  label: Omnichannel Inventory Sync Pipeline
  description: Syncs inventory between SAP warehouse, Salesforce Commerce Cloud, and store POS systems, logs discrepancies in ServiceNow, and alerts supply chain.
  tags:
  - inventory
  - sap
  - salesforce
  - servicenow
  - slack
capability:
  exposes:
  - type: mcp
    namespace: inventory
    port: 8080
    tools:
    - name: omnichannel_inventory_sync_pipeline
      description: Orchestrate omnichannel inventory sync pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-sap
        type: call
        call: sap.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-salesforce
        type: call
        call: salesforce.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-servicenow
        type: call
        call: servicenow.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: salesforce-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Collects social media mentions, runs sentiment analysis in Snowflake, updates HubSpot brand health metrics, and notifies communications team.

naftiko: '0.5'
info:
  label: Brand Sentiment Analyzer
  description: Collects social media mentions, runs sentiment analysis in Snowflake, updates HubSpot brand health metrics, and notifies communications team.
  tags:
  - brand
  - snowflake
  - hubspot
  - powerbi
  - slack
capability:
  exposes:
  - type: mcp
    namespace: brand
    port: 8080
    tools:
    - name: brand_sentiment_analyzer
      description: Orchestrate brand sentiment analyzer workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-snowflake
        type: call
        call: snowflake.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-hubspot
        type: call
        call: hubspot.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-slack
        type: call
        call: slack.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-servicenow
        type: call
        call: servicenow.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: hubspot
    baseUri: https://api.hubapi.com
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: hubspot-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST

Pulls sales data from Snowflake, runs ML models for demand prediction, updates SAP MRP, generates reports in Power BI, and notifies planners.

naftiko: '0.5'
info:
  label: Supply Chain Demand Forecasting
  description: Pulls sales data from Snowflake, runs ML models for demand prediction, updates SAP MRP, generates reports in Power BI, and notifies planners.
  tags:
  - supply-chain
  - snowflake
  - sap
  - powerbi
  - slack
capability:
  exposes:
  - type: mcp
    namespace: supply-chain
    port: 8080
    tools:
    - name: supply_chain_demand_forecasting
      description: Orchestrate supply chain demand forecasting workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-snowflake
        type: call
        call: snowflake.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-sap
        type: call
        call: sap.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-slack
        type: call
        call: slack.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-servicenow
        type: call
        call: servicenow.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: sap
    baseUri: https://adidas-sap.com/api/v1
    authentication:
      type: bearer
      token: $secrets.sap_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: sap-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST

Receives a customer inquiry via WhatsApp, looks up the order in BigCommerce, fetches tracking from SAP, and replies with the order status through WhatsApp.

naftiko: '0.5'
info:
  label: WhatsApp Customer Order Status Bot
  description: Receives a customer inquiry via WhatsApp, looks up the order in BigCommerce, fetches tracking from SAP, and replies with the order status through WhatsApp.
  tags:
  - customer-service
  - whatsapp
  - bigcommerce
  - sap-s4hana
capability:
  exposes:
  - type: mcp
    namespace: whatsapp-bot
    port: 8080
    tools:
    - name: handle-order-inquiry
      description: Given a WhatsApp message with an order number, look up status and reply with tracking info.
      inputParameters:
      - name: phone_number
        in: body
        type: string
        description: The customer WhatsApp phone number.
      - name: order_id
        in: body
        type: string
        description: The order ID from the customer message.
      steps:
      - name: get-order
        type: call
        call: bigcommerce.get-order
        with:
          order_id: '{{order_id}}'
      - name: get-tracking
        type: call
        call: sap.get-delivery-tracking
        with:
          order_reference: '{{order_id}}'
      - name: reply-whatsapp
        type: call
        call: whatsapp.send-message
        with:
          to: '{{phone_number}}'
          text: 'Hi! Your order #{{order_id}} is {{get-order.status}}. Tracking: {{get-tracking.tracking_number}}. Estimated delivery: {{get-tracking.estimated_delivery}}.'
  consumes:
  - type: http
    namespace: bigcommerce
    baseUri: https://api.bigcommerce.com/stores/adidas/v2
    authentication:
      type: bearer
      token: $secrets.bigcommerce_token
    resources:
    - name: orders
      path: /orders/{{order_id}}
      inputParameters:
      - name: order_id
        in: path
      operations:
      - name: get-order
        method: GET
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/API_OUTBOUND_DELIVERY_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: deliveries
      path: /A_OutbDeliveryHeader
      operations:
      - name: get-delivery-tracking
        method: GET
  - type: http
    namespace: whatsapp
    baseUri: https://graph.facebook.com/v18.0/$secrets.whatsapp_phone_id
    authentication:
      type: bearer
      token: $secrets.whatsapp_token
    resources:
    - name: messages
      path: /messages
      operations:
      - name: send-message
        method: POST

Retrieves GitHub repository metadata for Adidas.

naftiko: '0.5'
info:
  label: GitHub Repository Lookup
  description: Retrieves GitHub repository metadata for Adidas.
  tags:
  - devops
  - github
  - source-control
capability:
  exposes:
  - type: mcp
    namespace: engineering
    port: 8080
    tools:
    - name: get-repo
      description: Look up repo at Adidas.
      inputParameters:
      - name: repo_name
        in: body
        type: string
        description: The repo_name to look up.
      call: github.get-repo_name
      with:
        repo_name: '{{repo_name}}'
  consumes:
  - type: http
    namespace: github
    baseUri: https://api.github.com
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: github_repository_lookup
        method: GET

Pulls store sales data from Teradata, KPI metrics from SAP BW, and customer foot traffic from Google Analytics, then consolidates into a Google Sheet for regional managers.

naftiko: '0.5'
info:
  label: Retail Store Performance Dashboard Sync
  description: Pulls store sales data from Teradata, KPI metrics from SAP BW, and customer foot traffic from Google Analytics, then consolidates into a Google Sheet for regional managers.
  tags:
  - retail
  - analytics
  - teradata
  - sap-bw
  - google-analytics
  - google-sheets
capability:
  exposes:
  - type: mcp
    namespace: retail-reporting
    port: 8080
    tools:
    - name: sync-store-dashboard
      description: Given a store ID and date range, collect sales, KPIs, and traffic data and write to a Google Sheet.
      inputParameters:
      - name: store_id
        in: body
        type: string
        description: The Adidas retail store identifier.
      - name: date_range
        in: body
        type: string
        description: Date range in YYYY-MM-DD/YYYY-MM-DD format.
      - name: spreadsheet_id
        in: body
        type: string
        description: The Google Sheets spreadsheet ID for output.
      steps:
      - name: get-sales
        type: call
        call: teradata.query-store-sales
        with:
          store_id: '{{store_id}}'
          date_range: '{{date_range}}'
      - name: get-kpis
        type: call
        call: sap-bw.get-store-kpis
        with:
          store_id: '{{store_id}}'
          date_range: '{{date_range}}'
      - name: get-traffic
        type: call
        call: ga.get-store-traffic
        with:
          store_id: '{{store_id}}'
          date_range: '{{date_range}}'
      - name: write-to-sheet
        type: call
        call: gsheets.update-range
        with:
          spreadsheet_id: '{{spreadsheet_id}}'
          range: Dashboard!A1
          values: 'Store: {{store_id}} | Revenue: {{get-sales.total_revenue}} | Transactions: {{get-sales.transactions}} | Conversion: {{get-kpis.conversion_rate}} | Foot Traffic: {{get-traffic.sessions}}'
  consumes:
  - type: http
    namespace: teradata
    baseUri: https://teradata.adidas.internal/api/v1
    authentication:
      type: basic
      username: $secrets.teradata_user
      password: $secrets.teradata_password
    resources:
    - name: queries
      path: /queries
      operations:
      - name: query-store-sales
        method: POST
  - type: http
    namespace: sap-bw
    baseUri: https://adidas-bw.sap.com/sap/bw/odata/v1
    authentication:
      type: basic
      username: $secrets.sap_bw_user
      password: $secrets.sap_bw_password
    resources:
    - name: store-kpis
      path: /ZRETAIL_STORE_KPI
      operations:
      - name: get-store-kpis
        method: GET
  - type: http
    namespace: ga
    baseUri: https://analyticsdata.googleapis.com/v1beta
    authentication:
      type: bearer
      token: $secrets.google_analytics_token
    resources:
    - name: reports
      path: /properties/{{property_id}}:runReport
      operations:
      - name: get-store-traffic
        method: POST
  - type: http
    namespace: gsheets
    baseUri: https://sheets.googleapis.com/v4/spreadsheets
    authentication:
      type: bearer
      token: $secrets.google_sheets_token
    resources:
    - name: values
      path: /{{spreadsheet_id}}/values/{{range}}
      inputParameters:
      - name: spreadsheet_id
        in: path
      - name: range
        in: path
      operations:
      - name: update-range
        method: PUT

Creates a Salesforce opportunity for an athlete endorsement, stores the contract in Box, updates the deal in Microsoft Planner, and notifies the brand team in Teams.

naftiko: '0.5'
info:
  label: Athlete Endorsement Deal Tracker
  description: Creates a Salesforce opportunity for an athlete endorsement, stores the contract in Box, updates the deal in Microsoft Planner, and notifies the brand team in Teams.
  tags:
  - partnerships
  - salesforce
  - box
  - microsoft-planner
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: endorsements
    port: 8080
    tools:
    - name: create-endorsement-deal
      description: Given athlete details and deal terms, create tracking records across Salesforce, Box, Planner, and Teams.
      inputParameters:
      - name: athlete_name
        in: body
        type: string
        description: Name of the athlete.
      - name: deal_value
        in: body
        type: string
        description: Total deal value.
      - name: sport_category
        in: body
        type: string
        description: Sport category (e.g. running, football, basketball).
      - name: contract_duration
        in: body
        type: string
        description: Contract duration in months.
      steps:
      - name: create-opportunity
        type: call
        call: salesforce.create-opportunity
        with:
          name: 'Endorsement: {{athlete_name}} — {{sport_category}}'
          amount: '{{deal_value}}'
          stage: Negotiation
          description: '{{contract_duration}} month endorsement deal with {{athlete_name}} for {{sport_category}}.'
      - name: create-contract-folder
        type: call
        call: box.create-folder
        with:
          parent_folder_id: $secrets.endorsements_folder
          name: '{{athlete_name}}_{{sport_category}}'
      - name: create-planner-task
        type: call
        call: planner.create-task
        with:
          plan_id: $secrets.endorsements_plan_id
          title: 'Review: {{athlete_name}} endorsement — {{deal_value}}'
          due_date: +14d
          description: 'SF Opportunity: {{create-opportunity.id}} | Box: {{create-contract-folder.url}}'
      - name: notify-brand-team
        type: call
        call: msteams.send-message
        with:
          channel: brand-partnerships
          text: 'New Endorsement Deal: {{athlete_name}} ({{sport_category}}) | Value: {{deal_value}} | Duration: {{contract_duration}}mo | SF: {{create-opportunity.id}} | Task: {{create-planner-task.id}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: opportunities
      path: /sobjects/Opportunity
      operations:
      - name: create-opportunity
        method: POST
  - type: http
    namespace: box
    baseUri: https://api.box.com/2.0
    authentication:
      type: bearer
      token: $secrets.box_token
    resources:
    - name: folders
      path: /folders
      operations:
      - name: create-folder
        method: POST
  - type: http
    namespace: planner
    baseUri: https://graph.microsoft.com/v1.0/planner
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: tasks
      path: /tasks
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{team_id}}/channels/{{channel_id}}/messages
      operations:
      - name: send-message
        method: POST

When a return request arrives in Zendesk, looks up the order in BigCommerce, initiates a refund via Stripe, updates the SAP inventory, and resolves the Zendesk ticket.

naftiko: '0.5'
info:
  label: Customer Return Processing
  description: When a return request arrives in Zendesk, looks up the order in BigCommerce, initiates a refund via Stripe, updates the SAP inventory, and resolves the Zendesk ticket.
  tags:
  - customer-service
  - returns
  - zendesk
  - bigcommerce
  - stripe
  - sap-s4hana
capability:
  exposes:
  - type: mcp
    namespace: returns
    port: 8080
    tools:
    - name: process-return
      description: Given a Zendesk ticket ID and order ID, process the full return including refund and inventory adjustment.
      inputParameters:
      - name: ticket_id
        in: body
        type: string
        description: The Zendesk ticket ID for the return request.
      - name: order_id
        in: body
        type: string
        description: The BigCommerce order ID.
      - name: reason
        in: body
        type: string
        description: Return reason code.
      steps:
      - name: get-order
        type: call
        call: bigcommerce.get-order
        with:
          order_id: '{{order_id}}'
      - name: process-refund
        type: call
        call: stripe.create-refund
        with:
          payment_intent_id: '{{get-order.payment_reference}}'
          amount: '{{get-order.total_inc_tax}}'
          reason: '{{reason}}'
      - name: update-inventory
        type: call
        call: sap.post-goods-receipt
        with:
          sku: '{{get-order.line_items[0].sku}}'
          quantity: '{{get-order.line_items[0].quantity}}'
          movement_type: RETURN
      - name: resolve-ticket
        type: call
        call: zendesk.update-ticket
        with:
          ticket_id: '{{ticket_id}}'
          status: solved
          comment: 'Return processed. Refund: {{process-refund.id}} ({{process-refund.amount}}). Inventory updated.'
  consumes:
  - type: http
    namespace: bigcommerce
    baseUri: https://api.bigcommerce.com/stores/adidas/v2
    authentication:
      type: bearer
      token: $secrets.bigcommerce_token
    resources:
    - name: orders
      path: /orders/{{order_id}}
      inputParameters:
      - name: order_id
        in: path
      operations:
      - name: get-order
        method: GET
  - type: http
    namespace: stripe
    baseUri: https://api.stripe.com/v1
    authentication:
      type: bearer
      token: $secrets.stripe_secret_key
    resources:
    - name: refunds
      path: /refunds
      operations:
      - name: create-refund
        method: POST
  - type: http
    namespace: sap
    baseUri: https://adidas-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_DOCUMENT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: material-documents
      path: /A_MaterialDocumentHeader
      operations:
      - name: post-goods-receipt
        method: POST
  - type: http
    namespace: zendesk
    baseUri: https://adidas.zendesk.com/api/v2
    authentication:
      type: bearer
      token: $secrets.zendesk_token
    resources:
    - name: tickets
      path: /tickets/{{ticket_id}}.json
      inputParameters:
      - name: ticket_id
        in: path
      operations:
      - name: update-ticket
        method: PUT

When a Zendesk ticket is resolved, sends a Google Forms satisfaction survey link, collects the response, and updates the Salesforce contact record with the CSAT score.

naftiko: '0.5'
info:
  label: Customer Feedback Loop
  description: When a Zendesk ticket is resolved, sends a Google Forms satisfaction survey link, collects the response, and updates the Salesforce contact record with the CSAT score.
  tags:
  - customer-service
  - feedback
  - zendesk
  - google-forms
  - salesforce
capability:
  exposes:
  - type: mcp
    namespace: customer-feedback
    port: 8080
    tools:
    - name: trigger-feedback-survey
      description: Given a resolved Zendesk ticket, send a satisfaction survey and route the score back to Salesforce.
      inputParameters:
      - name: ticket_id
        in: body
        type: string
        description: The resolved Zendesk ticket ID.
      - name: customer_email
        in: body
        type: string
        description: The customer email address.
      - name: salesforce_contact_id
        in: body
        type: string
        description: The Salesforce contact ID.
      steps:
      - name: get-ticket
        type: call
        call: zendesk.get-ticket
        with:
          ticket_id: '{{ticket_id}}'
      - name: send-survey
        type: call
        call: google-forms.send-form
        with:
          form_id: $secrets.csat_form_id
          recipient_email: '{{customer_email}}'
          ticket_reference: '{{ticket_id}}'
      - name: update-salesforce
        type: call
        call: salesforce.update-contact
        with:
          contact_id: '{{salesforce_contact_id}}'
          last_survey_sent: '{{ticket_id}}'
          survey_type: CSAT
  consumes:
  - type: http
    namespace: zendesk
    baseUri: https://adidas.zendesk.com/api/v2
    authentication:
      type: bearer
      token: $secrets.zendesk_token
    resources:
    - name: tickets
      path: /tickets/{{ticket_id}}.json
      inputParameters:
      - name: ticket_id
        in: path
      operations:
      - name: get-ticket
        method: GET
  - type: http
    namespace: google-forms
    baseUri: https://forms.googleapis.com/v1
    authentication:
      type: bearer
      token: $secrets.google_forms_token
    resources:
    - name: forms
      path: /forms/{{form_id}}/responses
      inputParameters:
      - name: form_id
        in: path
      operations:
      - name: send-form
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: contacts
      path: /sobjects/Contact/{{contact_id}}
      inputParameters:
      - name: contact_id
        in: path
      operations:
      - name: update-contact
        method: PATCH

Monitors equipment telemetry in Datadog, predicts maintenance needs in Snowflake, creates work orders in ServiceNow, and notifies facility team.

naftiko: '0.5'
info:
  label: Warehouse Equipment Maintenance Pipeline
  description: Monitors equipment telemetry in Datadog, predicts maintenance needs in Snowflake, creates work orders in ServiceNow, and notifies facility team.
  tags:
  - maintenance
  - datadog
  - snowflake
  - servicenow
  - slack
capability:
  exposes:
  - type: mcp
    namespace: maintenance
    port: 8080
    tools:
    - name: warehouse_equipment_maintenance_pipeline
      description: Orchestrate warehouse equipment maintenance pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-datadog
        type: call
        call: datadog.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-servicenow
        type: call
        call: servicenow.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apiKey
      key: $secrets.datadog_api_key
      header: DD-API-KEY
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: datadog-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://adidas.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: servicenow-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Looks up a potential influencer on LinkedIn and ZoomInfo, creates a Salesforce opportunity, drafts an outreach email in Adobe Campaign, and tracks the engagement in HubSpot.

naftiko: '0.5'
info:
  label: Influencer Collaboration Workflow
  description: Looks up a potential influencer on LinkedIn and ZoomInfo, creates a Salesforce opportunity, drafts an outreach email in Adobe Campaign, and tracks the engagement in HubSpot.
  tags:
  - marketing
  - influencer
  - linkedin
  - zoominfo
  - salesforce
  - adobe-campaign
  - hubspot
capability:
  exposes:
  - type: mcp
    namespace: influencer-marketing
    port: 8080
    tools:
    - name: initiate-collaboration
      description: Given an influencer name and social handle, research them, create a sales opportunity, and start outreach.
      inputParameters:
      - name: influencer_name
        in: body
        type: string
        description: Full name of the influencer.
      - name: social_handle
        in: body
        type: string
        description: Primary social media handle.
      - name: campaign_name
        in: body
        type: string
        description: The marketing campaign for this collaboration.
      steps:
      - name: lookup-linkedin
        type: call
        call: linkedin.search-person
        with:
          name: '{{influencer_name}}'
      - name: enrich-contact
        type: call
        call: zoominfo.enrich-person
        with:
          name: '{{influencer_name}}'
          social_handle: '{{social_handle}}'
      - name: create-opportunity
        type: call
        call: salesforce.create-opportunity
        with:
          name: 'Influencer Collab: {{influencer_name}} — {{campaign_name}}'
          stage: Prospecting
          description: 'LinkedIn: {{lookup-linkedin.profile_url}} | Followers: {{enrich-contact.follower_count}} | Engagement Rate: {{enrich-contact.engagement_rate}}'
      - name: create-outreach
        type: call
        call: adobe-campaign.create-delivery
        with:
          template: influencer_outreach_v1
          recipient_email: '{{enrich-contact.email}}'
          campaign_name: '{{campaign_name}}'
      - name: create-hubspot-contact
        type: call
        call: hubspot.create-contact
        with:
          email: '{{enrich-contact.email}}'
          firstname: '{{influencer_name}}'
          company: Influencer
          lifecyclestage: lead
  consumes:
  - type: http
    namespace: linkedin
    baseUri: https://api.linkedin.com/v2
    authentication:
      type: bearer
      token: $secrets.linkedin_token
    resources:
    - name: people
      path: /people
      operations:
      - name: search-person
        method: GET
  - type: http
    namespace: zoominfo
    baseUri: https://api.zoominfo.com
    authentication:
      type: bearer
      token: $secrets.zoominfo_token
    resources:
    - name: enrich
      path: /enrich/person
      operations:
      - name: enrich-person
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://adidas.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: opportunities
      path: /sobjects/Opportunity
      operations:
      - name: create-opportunity
        method: POST
  - type: http
    namespace: adobe-campaign
    baseUri: https://mc.adobe.io/adidas/campaign
    authentication:
      type: bearer
      token: $secrets.adobe_campaign_token
    resources:
    - name: deliveries
      path: /deliveries
      operations:
      - name: create-delivery
        method: POST
  - type: http
    namespace: hubspot
    baseUri: https://api.hubapi.com/crm/v3
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: contacts
      path: /objects/contacts
      operations:
      - name: create-contact
        method: POST

Pulls a summary report from Google Analytics for a specified campaign, returning sessions, conversion rate, and revenue attribution.

naftiko: '0.5'
info:
  label: Google Analytics Campaign Report
  description: Pulls a summary report from Google Analytics for a specified campaign, returning sessions, conversion rate, and revenue attribution.
  tags:
  - marketing
  - google-analytics
  - campaign
capability:
  exposes:
  - type: mcp
    namespace: marketing-analytics
    port: 8080
    tools:
    - name: get-campaign-report
      description: Retrieve a Google Analytics campaign performance summary including sessions, conversions, and revenue.
      inputParameters:
      - name: campaign_id
        in: body
        type: string
        description: The Google Analytics campaign ID.
      - name: date_range
        in: body
        type: string
        description: Date range in YYYY-MM-DD/YYYY-MM-DD format.
      call: ga.get-report
      with:
        campaign_id: '{{campaign_id}}'
        date_range: '{{date_range}}'
      outputParameters:
      - name: sessions
        type: string
        mapping: $.rows[0].metricValues[0].value
      - name: conversion_rate
        type: string
        mapping: $.rows[0].metricValues[1].value
      - name: revenue
        type: string
        mapping: $.rows[0].metricValues[2].value
  consumes:
  - type: http
    namespace: ga
    baseUri: https://analyticsdata.googleapis.com/v1beta
    authentication:
      type: bearer
      token: $secrets.google_analytics_token
    resources:
    - name: reports
      path: /properties/{{campaign_id}}:runReport
      inputParameters:
      - name: campaign_id
        in: path
      operations:
      - name: get-report
        method: POST

Monitors product listings across e-commerce channels, tracks pricing and availability, logs discrepancies, and alerts the digital commerce team.

naftiko: '0.5'
info:
  label: Digital Shelf Monitoring Pipeline
  description: Monitors product listings across e-commerce channels, tracks pricing and availability, logs discrepancies, and alerts the digital commerce team.
  tags:
  - e-commerce
  - datadog
  - snowflake
  - jira
  - slack
capability:
  exposes:
  - type: mcp
    namespace: e-commerce
    port: 8080
    tools:
    - name: digital_shelf_monitoring_pipeline
      description: Orchestrate digital shelf monitoring pipeline workflow.
      inputParameters:
      - name: resource_id
        in: body
        type: string
        description: Primary resource identifier.
      steps:
      - name: get-datadog
        type: call
        call: datadog.get-resource
        with:
          resource_id: '{{resource_id}}'
      - name: process-snowflake
        type: call
        call: snowflake.process-resource
        with:
          resource_id: '{{resource_id}}'
      - name: create-jira
        type: call
        call: jira.create-resource
        with:
          resource_id: '{{resource_id}}'
      - name: notify-slack
        type: call
        call: slack.notify-resource
        with:
          resource_id: '{{resource_id}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apiKey
      key: $secrets.datadog_api_key
      header: DD-API-KEY
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: datadog-op
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://adidas.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: snowflake-op
        method: POST
  - type: http
    namespace: jira
    baseUri: https://adidas.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: jira-op
        method: POST
  - type: http
    namespace: slack
    baseUri: https://slack.com/api
    authentication:
      type: bearer
      token: $secrets.slack_bot_token
    resources:
    - name: resources
      path: /resources/{{resource_id}}
      operations:
      - name: slack-op
        method: POST

Queries the Teradata data warehouse for store-level sales performance by location and date range.

naftiko: '0.5'
info:
  label: Teradata Retail Analytics Query
  description: Queries the Teradata data warehouse for store-level sales performance by location and date range.
  tags:
  - analytics
  - teradata
  - retail
capability:
  exposes:
  - type: mcp
    namespace: retail-analytics
    port: 8080
    tools:
    - name: query-store-sales
      description: Run a store-level sales query in Teradata by store ID and date range.
      inputParameters:
      - name: store_id
        in: body
        type: string
        description: The Adidas retail store identifier.
      - name: start_date
        in: body
        type: string
        description: Start date in YYYY-MM-DD format.
      - name: end_date
        in: body
        type: string
        description: End date in YYYY-MM-DD format.
      call: teradata.run-query
      with:
        store_id: '{{store_id}}'
        start_date: '{{start_date}}'
        end_date: '{{end_date}}'
      outputParameters:
      - name: total_revenue
        type: string
        mapping: $.results[0].TOTAL_REVENUE
      - name: transactions
        type: string
        mapping: $.results[0].TRANSACTION_COUNT
      - name: avg_basket_size
        type: string
        mapping: $.results[0].AVG_BASKET
  consumes:
  - type: http
    namespace: teradata
    baseUri: https://teradata.adidas.internal/api/v1
    authentication:
      type: basic
      username: $secrets.teradata_user
      password: $secrets.teradata_password
    resources:
    - name: queries
      path: /queries
      operations:
      - name: run-query
        method: POST

Integrates point-of-sale data by pulling retail POS data from Circana, updating Salesforce retail accounts, and refreshing the Power BI sales analytics dashboard.

naftiko: '0.5'
info:
  label: Point of Sale Data Integration
  description: Integrates point-of-sale data by pulling retail POS data from Circana, updating Salesforce retail accounts, and refreshing the Power BI sales analytics dashboard.
  tags:
  - distribution
  - marketing
  - salesforce
  - power-bi
capability:
  exposes:
  - type: mcp
    namespace: pos-integration
    port: 8080
    tools:
    - name: integrate-pos-data
      description: 'Integrate POS data: pull Circana data, update Salesforce accounts, and refresh Power BI dashboard.'
      inputParameters:
      - name: retailer_id
        in: body
        type: string
        description: The Circana retailer ID.
      - name: sf_account_id
        in: body
        type: string
        description: The Salesforce retail account ID.
      - name: dataset_id
        in: body
        type: string
        description: The Power BI sales dataset ID.
      steps:
      - name: get-pos-data
        type: call
        call: circana.get-retailer-pos
        with:
          retailer_id: '{{retailer_id}}'
      - name: update-sf-account
        type: call
        call: salesforce.update-account
        with:
          account_id: '{{sf_account_id}}'
          weekly_volume: '{{get-pos-data.weekly_volume}}'
          market_share: '{{get-pos-data.market_share}}'
      - name: refresh-dashboard
        type: call
        call: powerbi.trigger-refresh
        with:
          dataset_id: '{{dataset_id}}'
  consumes:
  - type: http
    namespace: circana
    baseUri: https://api.circana.com/v2
    authentication:
      type: bearer
      token: $secrets.circana_token
    resources:
    - name: pos
      path: /pos/retailer/{{retailer_id}}
      inputParameters:
      - name: retailer_id
        in: path
      operations:
      - name: get-retailer-pos
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: accounts
      path: /sobjects/Account/{{account_id}}
      inputParameters:
      - name: account_id
        in: path
      operations:
      - name: update-account
        method: PATCH
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets/{{dataset_id}}/refreshes
      inputParameters:
      - name: dataset_id
        in: path
      operations:
      - name: trigger-refresh
        method: POST

Retrieves a SAP billing document by number, returning billing type, payer, net value, and billing date.

naftiko: '0.5'
info:
  label: SAP Billing Document Lookup
  description: Retrieves a SAP billing document by number, returning billing type, payer, net value, and billing date.
  tags:
  - finance
  - sap
  - billing
capability:
  exposes:
  - type: mcp
    namespace: billing
    port: 8080
    tools:
    - name: get-billing-document
      description: Look up a SAP billing document. Returns billing type, payer, net value, and billing date.
      inputParameters:
      - name: billing_document
        in: body
        type: string
        description: The SAP billing document number.
      call: sap.get-billing-doc
      with:
        billing_document: '{{billing_document}}'
      outputParameters:
      - name: billing_type
        type: string
        mapping: $.d.BillingDocumentType
      - name: payer
        type: string
        mapping: $.d.PayerParty
      - name: net_value
        type: string
        mapping: $.d.TotalNetAmount
      - name: billing_date
        type: string
        mapping: $.d.BillingDocumentDate
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_BILLING_DOCUMENT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: billing-documents
      path: /A_BillingDocument('{{billing_document}}')
      inputParameters:
      - name: billing_document
        in: path
      operations:
      - name: get-billing-doc
        method: GET

Monitors brand sentiment by pulling social listening data from HubSpot, cross-referencing with Adobe Analytics web traffic, and alerting brand management via Microsoft Teams.

naftiko: '0.5'
info:
  label: Social Media Sentiment Alert
  description: Monitors brand sentiment by pulling social listening data from HubSpot, cross-referencing with Adobe Analytics web traffic, and alerting brand management via Microsoft Teams.
  tags:
  - marketing
  - brand-management
  - hubspot
  - adobe-analytics
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: brand-monitoring
    port: 8080
    tools:
    - name: check-brand-sentiment
      description: 'Orchestrate brand sentiment check: pull HubSpot social data, cross-reference Adobe Analytics, and alert brand team.'
      inputParameters:
      - name: brand_name
        in: body
        type: string
        description: The brand to monitor, e.g. Coca-Cola, Sprite.
      - name: date_range
        in: body
        type: string
        description: Date range in YYYY-MM-DD:YYYY-MM-DD format.
      steps:
      - name: get-social-sentiment
        type: call
        call: hubspot.get-social-mentions
        with:
          brand: '{{brand_name}}'
          date_range: '{{date_range}}'
      - name: get-web-traffic
        type: call
        call: adobe.get-brand-traffic
        with:
          brand_segment: '{{brand_name}}'
          date_range: '{{date_range}}'
      - name: alert-brand-team
        type: call
        call: msteams.send-message
        with:
          channel_id: brand-{{brand_name}}
          text: 'Brand Sentiment Report for {{brand_name}}: Social mentions: {{get-social-sentiment.mention_count}}. Sentiment score: {{get-social-sentiment.sentiment_score}}. Web traffic: {{get-web-traffic.page_views}} page views.'
  consumes:
  - type: http
    namespace: hubspot
    baseUri: https://api.hubapi.com/crm/v3
    authentication:
      type: bearer
      token: $secrets.hubspot_token
    resources:
    - name: social-mentions
      path: /objects/social_mentions/search
      operations:
      - name: get-social-mentions
        method: POST
  - type: http
    namespace: adobe
    baseUri: https://analytics.adobe.io/api/cocacola
    authentication:
      type: bearer
      token: $secrets.adobe_analytics_token
    resources:
    - name: reports
      path: /reports
      operations:
      - name: get-brand-traffic
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves a vendor invoice from SAP, verifies it against the corresponding purchase order and goods receipt, and posts a match result back to SAP for payment approval.

naftiko: '0.5'
info:
  label: Invoice Processing and Three-Way Match
  description: Retrieves a vendor invoice from SAP, verifies it against the corresponding purchase order and goods receipt, and posts a match result back to SAP for payment approval.
  tags:
  - finance
  - procurement
  - sap
  - invoice-processing
capability:
  exposes:
  - type: mcp
    namespace: finance-ops
    port: 8080
    tools:
    - name: process-invoice-match
      description: Given an invoice number, retrieve the invoice and linked PO from SAP S/4HANA, validate quantity and price, and update the invoice match status. Use for accounts payable automation and three-way match workflows.
      inputParameters:
      - name: invoice_number
        in: body
        type: string
        description: The SAP vendor invoice number (MIRO-style document number).
      steps:
      - name: get-invoice
        type: call
        call: sap-fi.get-invoice
        with:
          invoice_number: '{{invoice_number}}'
      - name: get-po
        type: call
        call: sap-mm.get-po
        with:
          po_number: '{{get-invoice.po_number}}'
      - name: post-match-result
        type: call
        call: sap-fi.update-invoice-status
        with:
          invoice_number: '{{invoice_number}}'
          match_status: Matched
  consumes:
  - type: http
    namespace: sap-fi
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_SUPPLIER_INVOICE_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: invoices
      path: /A_SupplierInvoice('{{invoice_number}}')
      inputParameters:
      - name: invoice_number
        in: path
      operations:
      - name: get-invoice
        method: GET
      - name: update-invoice-status
        method: PATCH
  - type: http
    namespace: sap-mm
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/MM_PUR_PO_MAINT_V2_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: purchase-orders
      path: /A_PurchaseOrder('{{po_number}}')
      inputParameters:
      - name: po_number
        in: path
      operations:
      - name: get-po
        method: GET

Retrieves the status of a SAP production order including planned quantity, confirmed quantity, and system status for manufacturing tracking.

naftiko: '0.5'
info:
  label: SAP Production Order Status
  description: Retrieves the status of a SAP production order including planned quantity, confirmed quantity, and system status for manufacturing tracking.
  tags:
  - manufacturing
  - sap
  - production
capability:
  exposes:
  - type: mcp
    namespace: manufacturing
    port: 8080
    tools:
    - name: get-production-order
      description: Look up a SAP production order by order number. Returns order type, status, planned quantity, and confirmed quantity.
      inputParameters:
      - name: order_number
        in: body
        type: string
        description: The SAP production order number, e.g. 1000001234.
      call: sap.get-production-order
      with:
        order_number: '{{order_number}}'
      outputParameters:
      - name: order_type
        type: string
        mapping: $.d.ManufacturingOrderType
      - name: status
        type: string
        mapping: $.d.MfgOrderPlannedTotalQty
      - name: planned_qty
        type: string
        mapping: $.d.MfgOrderPlannedTotalQty
      - name: confirmed_qty
        type: string
        mapping: $.d.MfgOrderConfirmedYieldQty
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PRODUCTION_ORDER_2_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: production-orders
      path: /A_ProductionOrder_2('{{order_number}}')
      inputParameters:
      - name: order_number
        in: path
      operations:
      - name: get-production-order
        method: GET

Retrieves a SAP outbound delivery document by delivery number, returning ship-to party, planned goods issue date, and delivery status.

naftiko: '0.5'
info:
  label: SAP Delivery Document Lookup
  description: Retrieves a SAP outbound delivery document by delivery number, returning ship-to party, planned goods issue date, and delivery status.
  tags:
  - distribution
  - sap
  - logistics
capability:
  exposes:
  - type: mcp
    namespace: logistics
    port: 8080
    tools:
    - name: get-delivery-document
      description: Look up a SAP outbound delivery by delivery number. Returns ship-to party, goods issue date, and overall status.
      inputParameters:
      - name: delivery_number
        in: body
        type: string
        description: The SAP delivery document number, e.g. 8000012345.
      call: sap.get-delivery
      with:
        delivery_number: '{{delivery_number}}'
      outputParameters:
      - name: ship_to_party
        type: string
        mapping: $.d.ShipToParty
      - name: planned_goods_issue_date
        type: string
        mapping: $.d.PlannedGoodsIssueDate
      - name: delivery_status
        type: string
        mapping: $.d.OverallSDProcessStatus
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_OUTBOUND_DELIVERY_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: deliveries
      path: /A_OutbDeliveryHeader('{{delivery_number}}')
      inputParameters:
      - name: delivery_number
        in: path
      operations:
      - name: get-delivery
        method: GET

Syncs email campaign results from MailChimp to Salesforce campaign records and posts a performance summary to Microsoft Teams.

naftiko: '0.5'
info:
  label: MailChimp Email Campaign Results Sync
  description: Syncs email campaign results from MailChimp to Salesforce campaign records and posts a performance summary to Microsoft Teams.
  tags:
  - marketing
  - mailchimp
  - salesforce
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: email-marketing
    port: 8080
    tools:
    - name: sync-email-campaign-results
      description: Sync MailChimp campaign results to Salesforce and post performance summary to Teams.
      inputParameters:
      - name: mailchimp_campaign_id
        in: body
        type: string
        description: The MailChimp campaign ID.
      - name: sf_campaign_id
        in: body
        type: string
        description: The Salesforce campaign ID.
      steps:
      - name: get-campaign-report
        type: call
        call: mailchimp.get-campaign-report
        with:
          campaign_id: '{{mailchimp_campaign_id}}'
      - name: update-sf-campaign
        type: call
        call: salesforce.update-campaign
        with:
          campaign_id: '{{sf_campaign_id}}'
          emails_sent: '{{get-campaign-report.emails_sent}}'
          open_rate: '{{get-campaign-report.open_rate}}'
          click_rate: '{{get-campaign-report.click_rate}}'
      - name: post-summary
        type: call
        call: msteams.send-message
        with:
          channel_id: marketing-campaigns
          text: 'Email Campaign Report: {{get-campaign-report.campaign_title}}. Sent: {{get-campaign-report.emails_sent}}. Open rate: {{get-campaign-report.open_rate}}%. Click rate: {{get-campaign-report.click_rate}}%.'
  consumes:
  - type: http
    namespace: mailchimp
    baseUri: https://us1.api.mailchimp.com/3.0
    authentication:
      type: basic
      username: anystring
      password: $secrets.mailchimp_api_key
    resources:
    - name: campaign-reports
      path: /reports/{{campaign_id}}
      inputParameters:
      - name: campaign_id
        in: path
      operations:
      - name: get-campaign-report
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: campaigns
      path: /sobjects/Campaign/{{campaign_id}}
      inputParameters:
      - name: campaign_id
        in: path
      operations:
      - name: update-campaign
        method: PATCH
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Converts a customer complaint from Zendesk into a quality case by creating a SAP quality notification, linking to the Salesforce account, and notifying the quality team via Microsoft Teams.

naftiko: '0.5'
info:
  label: Customer Complaint to Quality Case
  description: Converts a customer complaint from Zendesk into a quality case by creating a SAP quality notification, linking to the Salesforce account, and notifying the quality team via Microsoft Teams.
  tags:
  - customer-service
  - quality
  - zendesk
  - sap
  - salesforce
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: quality-feedback
    port: 8080
    tools:
    - name: convert-complaint-to-quality-case
      description: Convert Zendesk complaint to SAP quality case, link Salesforce account, and notify quality team.
      inputParameters:
      - name: ticket_id
        in: body
        type: string
        description: The Zendesk ticket ID.
      - name: account_id
        in: body
        type: string
        description: The Salesforce account ID.
      steps:
      - name: get-complaint
        type: call
        call: zendesk.get-ticket
        with:
          ticket_id: '{{ticket_id}}'
      - name: create-quality-notification
        type: call
        call: sap.create-quality-notification
        with:
          notification_type: customer_complaint
          description: '{{get-complaint.subject}}: {{get-complaint.description}}'
          material: '{{get-complaint.product_sku}}'
      - name: update-sf-account
        type: call
        call: salesforce.create-case
        with:
          account_id: '{{account_id}}'
          subject: 'Quality case: {{get-complaint.subject}}'
          sap_notification: '{{create-quality-notification.notification_number}}'
      - name: notify-quality
        type: call
        call: msteams.send-message
        with:
          channel_id: quality-cases
          text: 'New quality case from customer complaint. Zendesk: #{{ticket_id}}. SAP notification: {{create-quality-notification.notification_number}}. Salesforce case: {{update-sf-account.case_number}}'
  consumes:
  - type: http
    namespace: zendesk
    baseUri: https://cocacola.zendesk.com/api/v2
    authentication:
      type: bearer
      token: $secrets.zendesk_token
    resources:
    - name: tickets
      path: /tickets/{{ticket_id}}
      inputParameters:
      - name: ticket_id
        in: path
      operations:
      - name: get-ticket
        method: GET
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_QUALITYNOTIFICATION_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: notifications
      path: /A_QualityNotification
      operations:
      - name: create-quality-notification
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: cases
      path: /sobjects/Case
      operations:
      - name: create-case
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves SLO compliance status from Datadog for all production services and publishes a weekly reliability digest to the SRE Microsoft Teams channel.

naftiko: '0.5'
info:
  label: Datadog SLO Compliance Report
  description: Retrieves SLO compliance status from Datadog for all production services and publishes a weekly reliability digest to the SRE Microsoft Teams channel.
  tags:
  - observability
  - datadog
  - slo
  - reporting
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: slo-reporting
    port: 8080
    tools:
    - name: digest-slo-compliance
      description: Fetch all SLO status summaries from Datadog and post a weekly compliance report to the SRE Teams channel. Use for reliability governance and SLO review meetings.
      steps:
      - name: get-slos
        type: call
        call: datadog.list-slos
      - name: post-report
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_sre_channel_id
          text: 'Weekly SLO Report: {{get-slos.total_count}} SLOs tracked across Coca-Cola production services.'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: slos
      path: /slo
      operations:
      - name: list-slos
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Fetches open Dependabot security alerts for a GitHub repository, creates ServiceNow security incidents for critical findings, and notifies the security team via Teams.

naftiko: '0.5'
info:
  label: GitHub Security Vulnerability Scan Triage
  description: Fetches open Dependabot security alerts for a GitHub repository, creates ServiceNow security incidents for critical findings, and notifies the security team via Teams.
  tags:
  - security
  - github
  - servicenow
  - devops
  - vulnerability-management
capability:
  exposes:
  - type: mcp
    namespace: security-ops
    port: 8080
    tools:
    - name: triage-security-alerts
      description: Retrieve open Dependabot security alerts for a GitHub repository, create ServiceNow security incidents for critical severity alerts, and notify the security team via Teams.
      inputParameters:
      - name: repo
        in: body
        type: string
        description: The repository in owner/repo format to scan for security alerts.
      steps:
      - name: get-alerts
        type: call
        call: github.list-dependabot-alerts
        with:
          owner: coca-cola
          repo: '{{repo}}'
          severity: critical
      - name: create-security-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: Critical Dependabot alerts in {{repo}}
          category: security
          urgency: '1'
      - name: notify-security-team
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_security_channel_id
          text: 'Security Alert: {{get-alerts.total_count}} critical vulnerabilities in {{repo}}. Incident: {{create-security-incident.number}}'
  consumes:
  - type: http
    namespace: github
    baseUri: https://api.github.com
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: dependabot-alerts
      path: /repos/{{owner}}/{{repo}}/dependabot/alerts
      inputParameters:
      - name: owner
        in: path
      - name: repo
        in: path
      - name: severity
        in: query
      operations:
      - name: list-dependabot-alerts
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

When a Salesforce survey response scores below a detractor threshold, automatically creates a service case and assigns it to the customer success team.

naftiko: '0.5'
info:
  label: Salesforce Customer NPS Case Creation
  description: When a Salesforce survey response scores below a detractor threshold, automatically creates a service case and assigns it to the customer success team.
  tags:
  - sales
  - customer-success
  - salesforce
  - nps
capability:
  exposes:
  - type: mcp
    namespace: customer-success
    port: 8080
    tools:
    - name: handle-nps-detractor
      description: Given a Salesforce contact ID and NPS score below 7, create a service case and assign it to the customer success team for follow-up. Use for automated detractor response workflows.
      inputParameters:
      - name: contact_id
        in: body
        type: string
        description: The Salesforce Contact ID of the NPS survey respondent.
      - name: nps_score
        in: body
        type: integer
        description: The NPS score (0–10) from the survey response.
      - name: feedback
        in: body
        type: string
        description: Verbatim feedback provided by the respondent.
      steps:
      - name: get-contact
        type: call
        call: salesforce-contact.get-contact
        with:
          contact_id: '{{contact_id}}'
      - name: create-case
        type: call
        call: salesforce-cases.create-case
        with:
          subject: 'NPS Detractor Follow-up: {{get-contact.name}} (Score: {{nps_score}})'
          description: '{{feedback}}'
          contactId: '{{contact_id}}'
          origin: NPS Survey
          priority: High
  consumes:
  - type: http
    namespace: salesforce-contact
    baseUri: https://cocacola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: contact
      path: /sobjects/Contact/{{contact_id}}
      inputParameters:
      - name: contact_id
        in: path
      operations:
      - name: get-contact
        method: GET
  - type: http
    namespace: salesforce-cases
    baseUri: https://cocacola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: cases
      path: /sobjects/Case
      operations:
      - name: create-case
        method: POST

Converts demand forecasts into production plans by pulling forecast data from Salesforce, creating planned orders in SAP, and updating the Power BI demand planning dashboard.

naftiko: '0.5'
info:
  label: Demand Forecast to Production Plan
  description: Converts demand forecasts into production plans by pulling forecast data from Salesforce, creating planned orders in SAP, and updating the Power BI demand planning dashboard.
  tags:
  - supply-chain
  - manufacturing
  - salesforce
  - sap
  - power-bi
capability:
  exposes:
  - type: mcp
    namespace: demand-planning
    port: 8080
    tools:
    - name: convert-forecast-to-plan
      description: 'Convert demand forecast to production plan: pull Salesforce forecast, create SAP planned orders, refresh dashboard.'
      inputParameters:
      - name: forecast_id
        in: body
        type: string
        description: The Salesforce demand forecast record ID.
      - name: plant_code
        in: body
        type: string
        description: The target manufacturing plant code.
      - name: dataset_id
        in: body
        type: string
        description: The Power BI demand planning dataset ID.
      steps:
      - name: get-forecast
        type: call
        call: salesforce.get-forecast
        with:
          forecast_id: '{{forecast_id}}'
      - name: create-planned-orders
        type: call
        call: sap.create-planned-order
        with:
          material_number: '{{get-forecast.material}}'
          plant: '{{plant_code}}'
          planned_quantity: '{{get-forecast.quantity}}'
          planned_date: '{{get-forecast.delivery_date}}'
      - name: refresh-dashboard
        type: call
        call: powerbi.trigger-refresh
        with:
          dataset_id: '{{dataset_id}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: forecasts
      path: /sobjects/Demand_Forecast__c/{{forecast_id}}
      inputParameters:
      - name: forecast_id
        in: path
      operations:
      - name: get-forecast
        method: GET
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PLANNED_ORDER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: planned-orders
      path: /A_PlannedOrder
      operations:
      - name: create-planned-order
        method: POST
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets/{{dataset_id}}/refreshes
      inputParameters:
      - name: dataset_id
        in: path
      operations:
      - name: trigger-refresh
        method: POST

Pulls current active headcount and salary band data from Workday and returns a structured summary grouped by cost center for finance planning.

naftiko: '0.5'
info:
  label: Headcount Snapshot by Cost Center
  description: Pulls current active headcount and salary band data from Workday and returns a structured summary grouped by cost center for finance planning.
  tags:
  - hr
  - finance
  - reporting
  - workday
capability:
  exposes:
  - type: mcp
    namespace: hr-reporting
    port: 8080
    tools:
    - name: get-headcount-snapshot
      description: Returns active headcount grouped by cost center and employment type from Workday. Use for headcount planning, finance forecasting, or budget review.
      call: workday.list-workers
      outputParameters:
      - name: workers
        type: array
        mapping: $.data
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers-list
      path: /coca-cola/workers
      operations:
      - name: list-workers
        method: GET

Detects packaging material shortages by checking SAP inventory levels, identifies affected production orders, and escalates to supply chain and manufacturing teams via Microsoft Teams.

naftiko: '0.5'
info:
  label: Packaging Material Shortage Alert
  description: Detects packaging material shortages by checking SAP inventory levels, identifies affected production orders, and escalates to supply chain and manufacturing teams via Microsoft Teams.
  tags:
  - manufacturing
  - supply-chain
  - sap
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: supply-chain-alert
    port: 8080
    tools:
    - name: alert-packaging-shortage
      description: 'Orchestrate packaging shortage response: check SAP inventory, identify affected orders, and notify supply chain team.'
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number for the packaging material.
      - name: plant_code
        in: body
        type: string
        description: The manufacturing plant code.
      steps:
      - name: check-stock
        type: call
        call: sap.get-material-stock
        with:
          material_number: '{{material_number}}'
          plant: '{{plant_code}}'
      - name: get-affected-orders
        type: call
        call: sap.get-dependent-orders
        with:
          material_number: '{{material_number}}'
          plant: '{{plant_code}}'
      - name: notify-supply-chain
        type: call
        call: msteams.send-message
        with:
          channel_id: supply-chain-alerts
          text: 'PACKAGING SHORTAGE: Material {{material_number}} at plant {{plant_code}}. Available stock: {{check-stock.available_stock}} {{check-stock.unit}}. Affected production orders: {{get-affected-orders.count}}. Immediate procurement action required.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: material-stock
      path: /A_MatlStkInAcctMod(Material='{{material_number}}',Plant='{{plant}}')
      inputParameters:
      - name: material_number
        in: path
      - name: plant
        in: path
      operations:
      - name: get-material-stock
        method: GET
    - name: dependent-orders
      path: /A_ProductionOrder?$filter=Material eq '{{material_number}}' and Plant eq '{{plant}}'
      inputParameters:
      - name: material_number
        in: query
      - name: plant
        in: query
      operations:
      - name: get-dependent-orders
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Optimizes vending machine refills by pulling telemetry data, checking regional inventory in SAP, and creating route-optimized refill tasks in ServiceNow.

naftiko: '0.5'
info:
  label: Vending Machine Refill Optimization
  description: Optimizes vending machine refills by pulling telemetry data, checking regional inventory in SAP, and creating route-optimized refill tasks in ServiceNow.
  tags:
  - distribution
  - supply-chain
  - sap
  - servicenow
capability:
  exposes:
  - type: mcp
    namespace: vending-ops
    port: 8080
    tools:
    - name: optimize-refill-routes
      description: 'Optimize vending refills: pull machine telemetry, check SAP inventory, and create ServiceNow refill tasks.'
      inputParameters:
      - name: region_code
        in: body
        type: string
        description: The regional distribution code.
      - name: threshold_percent
        in: body
        type: string
        description: The stock threshold percentage to trigger refill.
      steps:
      - name: get-machine-telemetry
        type: call
        call: sap.get-vending-telemetry
        with:
          region: '{{region_code}}'
          threshold: '{{threshold_percent}}'
      - name: check-regional-inventory
        type: call
        call: sap.get-regional-stock
        with:
          region: '{{region_code}}'
      - name: create-refill-tasks
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Vending refill route: Region {{region_code}}'
          description: 'Machines below {{threshold_percent}}%: {{get-machine-telemetry.low_stock_count}}. Regional inventory: {{check-regional-inventory.available_cases}} cases available.'
          category: vending_refill
          assignment_group: Distribution_{{region_code}}
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_VENDING_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: telemetry
      path: /VendingMachineStatus?$filter=Region eq '{{region}}' and StockLevel lt {{threshold}}
      inputParameters:
      - name: region
        in: query
      - name: threshold
        in: query
      operations:
      - name: get-vending-telemetry
        method: GET
    - name: regional-stock
      path: /RegionalInventory('{{region}}')
      inputParameters:
      - name: region
        in: path
      operations:
      - name: get-regional-stock
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/sc_task
      operations:
      - name: create-task
        method: POST

When a quality issue is detected, places a batch on hold in SAP, creates a quality case in ServiceNow, and notifies the quality assurance and distribution teams via Microsoft Teams.

naftiko: '0.5'
info:
  label: Quality Hold and Recall Orchestrator
  description: When a quality issue is detected, places a batch on hold in SAP, creates a quality case in ServiceNow, and notifies the quality assurance and distribution teams via Microsoft Teams.
  tags:
  - manufacturing
  - quality
  - sap
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: quality-ops
    port: 8080
    tools:
    - name: initiate-quality-hold
      description: 'Orchestrate a quality hold: place batch on hold in SAP, create ServiceNow case, and notify QA and distribution teams.'
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number.
      - name: batch_number
        in: body
        type: string
        description: The batch number to place on hold.
      - name: reason
        in: body
        type: string
        description: The reason for the quality hold.
      steps:
      - name: get-batch-info
        type: call
        call: sap.get-batch
        with:
          material_number: '{{material_number}}'
          batch_number: '{{batch_number}}'
      - name: place-batch-hold
        type: call
        call: sap.update-batch-status
        with:
          material_number: '{{material_number}}'
          batch_number: '{{batch_number}}'
          status: RESTRICTED
      - name: create-quality-case
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Quality hold: Material {{material_number}} Batch {{batch_number}}'
          description: '{{reason}}'
          category: quality_hold
          urgency: '1'
          assignment_group: Quality_Assurance
      - name: notify-teams
        type: call
        call: msteams.send-message
        with:
          channel_id: quality-alerts
          text: 'QUALITY HOLD: Material {{material_number}}, Batch {{batch_number}} placed on hold. Reason: {{reason}}. Production date: {{get-batch-info.production_date}}. ServiceNow case: {{create-quality-case.number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_BATCH_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: batches
      path: /A_Batch(Material='{{material_number}}',Batch='{{batch_number}}')
      inputParameters:
      - name: material_number
        in: path
      - name: batch_number
        in: path
      operations:
      - name: get-batch
        method: GET
      - name: update-batch-status
        method: PATCH
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Orchestrates the monthly financial close by checking SAP period-end status, validating Oracle Cloud journal balances, refreshing the Power BI finance dashboard, and notifying the finance team.

naftiko: '0.5'
info:
  label: Monthly Financial Close Orchestrator
  description: Orchestrates the monthly financial close by checking SAP period-end status, validating Oracle Cloud journal balances, refreshing the Power BI finance dashboard, and notifying the finance team.
  tags:
  - finance
  - sap
  - oracle-cloud
  - power-bi
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: finance-close
    port: 8080
    tools:
    - name: run-monthly-close
      description: 'Orchestrate monthly financial close: check SAP period status, validate Oracle journals, refresh dashboard, and notify finance.'
      inputParameters:
      - name: fiscal_period
        in: body
        type: string
        description: The fiscal period, e.g. 2026-03.
      - name: company_code
        in: body
        type: string
        description: The SAP company code.
      - name: dataset_id
        in: body
        type: string
        description: The Power BI finance dataset ID.
      steps:
      - name: check-period-status
        type: call
        call: sap.get-period-close-status
        with:
          company_code: '{{company_code}}'
          period: '{{fiscal_period}}'
      - name: validate-journals
        type: call
        call: oracle.get-journal-balance
        with:
          period: '{{fiscal_period}}'
      - name: refresh-finance-dashboard
        type: call
        call: powerbi.trigger-refresh
        with:
          dataset_id: '{{dataset_id}}'
      - name: notify-finance
        type: call
        call: msteams.send-message
        with:
          channel_id: finance-close
          text: 'Monthly close for {{fiscal_period}}: SAP period status: {{check-period-status.status}}. Oracle journal balance: {{validate-journals.balance_status}}. Dashboard refreshed.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_FINANCIALPERIODCLOSE_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: period-close
      path: /A_FinancialPeriodClose(CompanyCode='{{company_code}}',Period='{{period}}')
      inputParameters:
      - name: company_code
        in: path
      - name: period
        in: path
      operations:
      - name: get-period-close-status
        method: GET
  - type: http
    namespace: oracle
    baseUri: https://coca-cola.oraclecloud.com/fscmRestApi/resources/v1
    authentication:
      type: basic
      username: $secrets.oracle_user
      password: $secrets.oracle_password
    resources:
    - name: journal-balances
      path: /journalBalances?q=Period={{period}}
      inputParameters:
      - name: period
        in: query
      operations:
      - name: get-journal-balance
        method: GET
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets/{{dataset_id}}/refreshes
      inputParameters:
      - name: dataset_id
        in: path
      operations:
      - name: trigger-refresh
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Reconciles vendor payments by pulling invoice data from SAP, matching against Oracle Cloud payment records, and logging discrepancies in ServiceNow.

naftiko: '0.5'
info:
  label: Vendor Payment Reconciliation
  description: Reconciles vendor payments by pulling invoice data from SAP, matching against Oracle Cloud payment records, and logging discrepancies in ServiceNow.
  tags:
  - finance
  - sap
  - oracle-cloud
  - servicenow
  - procurement
capability:
  exposes:
  - type: mcp
    namespace: finance-ops
    port: 8080
    tools:
    - name: reconcile-vendor-payment
      description: Orchestrate vendor payment reconciliation across SAP invoices, Oracle Cloud payments, and ServiceNow for discrepancy tracking.
      inputParameters:
      - name: vendor_id
        in: body
        type: string
        description: The SAP vendor ID.
      - name: invoice_number
        in: body
        type: string
        description: The SAP invoice document number.
      steps:
      - name: get-sap-invoice
        type: call
        call: sap.get-invoice
        with:
          invoice_number: '{{invoice_number}}'
      - name: get-oracle-payment
        type: call
        call: oracle.get-payment
        with:
          vendor_id: '{{vendor_id}}'
          invoice_reference: '{{invoice_number}}'
      - name: log-discrepancy
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Payment reconciliation: Vendor {{vendor_id}} Invoice {{invoice_number}}'
          description: 'SAP amount: {{get-sap-invoice.total_amount}}. Oracle payment: {{get-oracle-payment.payment_amount}}.'
          category: finance_reconciliation
          assignment_group: Accounts_Payable
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_SUPPLIERINVOICE_PROCESS_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: invoices
      path: /A_SupplierInvoice('{{invoice_number}}')
      inputParameters:
      - name: invoice_number
        in: path
      operations:
      - name: get-invoice
        method: GET
  - type: http
    namespace: oracle
    baseUri: https://coca-cola.oraclecloud.com/fscmRestApi/resources/v1
    authentication:
      type: basic
      username: $secrets.oracle_user
      password: $secrets.oracle_password
    resources:
    - name: payments
      path: /payments?q=VendorId={{vendor_id}};InvoiceNumber={{invoice_reference}}
      inputParameters:
      - name: vendor_id
        in: query
      - name: invoice_reference
        in: query
      operations:
      - name: get-payment
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST

Fetches open pull requests from a GitHub repository and posts a daily review-pending summary to the engineering Teams channel to prompt timely code reviews.

naftiko: '0.5'
info:
  label: GitHub Pull Request Code Review Summary
  description: Fetches open pull requests from a GitHub repository and posts a daily review-pending summary to the engineering Teams channel to prompt timely code reviews.
  tags:
  - devops
  - github
  - code-review
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: devops-review
    port: 8080
    tools:
    - name: digest-pending-prs
      description: List all open pull requests for a GitHub repository and post a summary of review-pending PRs to the designated Teams channel. Use for daily PR queue digest automation.
      inputParameters:
      - name: repo
        in: body
        type: string
        description: The repository in owner/repo format.
      steps:
      - name: list-prs
        type: call
        call: github.list-pull-requests
        with:
          owner: coca-cola
          repo: '{{repo}}'
          state: open
      - name: post-digest
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_engineering_channel_id
          text: 'PR Review Digest for {{repo}}: {{list-prs.total_count}} open PRs awaiting review.'
  consumes:
  - type: http
    namespace: github
    baseUri: https://api.github.com
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: pull-requests
      path: /repos/{{owner}}/{{repo}}/pulls
      inputParameters:
      - name: owner
        in: path
      - name: repo
        in: path
      - name: state
        in: query
      operations:
      - name: list-pull-requests
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Validates new product launch readiness by checking SAP material master setup, Salesforce product catalog entry, and Adobe Analytics tracking configuration.

naftiko: '0.5'
info:
  label: New Product Launch Readiness Check
  description: Validates new product launch readiness by checking SAP material master setup, Salesforce product catalog entry, and Adobe Analytics tracking configuration.
  tags:
  - brand-management
  - manufacturing
  - sap
  - salesforce
  - adobe-analytics
capability:
  exposes:
  - type: mcp
    namespace: product-launch
    port: 8080
    tools:
    - name: check-launch-readiness
      description: Validate new product launch readiness across SAP material master, Salesforce catalog, and Adobe Analytics tracking.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number for the new product.
      - name: product_id
        in: body
        type: string
        description: The Salesforce product record ID.
      steps:
      - name: check-material-master
        type: call
        call: sap.get-material-master
        with:
          material_number: '{{material_number}}'
      - name: check-sf-product
        type: call
        call: salesforce.get-product
        with:
          product_id: '{{product_id}}'
      - name: check-analytics-tracking
        type: call
        call: adobe.get-tracking-config
        with:
          product_code: '{{material_number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PRODUCT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: materials
      path: /A_Product('{{material_number}}')
      inputParameters:
      - name: material_number
        in: path
      operations:
      - name: get-material-master
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: products
      path: /sobjects/Product2/{{product_id}}
      inputParameters:
      - name: product_id
        in: path
      operations:
      - name: get-product
        method: GET
  - type: http
    namespace: adobe
    baseUri: https://analytics.adobe.io/api/cocacola
    authentication:
      type: bearer
      token: $secrets.adobe_analytics_token
    resources:
    - name: tracking-config
      path: /tracking/product/{{product_code}}
      inputParameters:
      - name: product_code
        in: path
      operations:
      - name: get-tracking-config
        method: GET

Monitors plant water usage compliance by pulling consumption data from SAP, comparing against permitted limits, and alerting environmental compliance via Microsoft Teams and ServiceNow.

naftiko: '0.5'
info:
  label: Water Usage Compliance Monitor
  description: Monitors plant water usage compliance by pulling consumption data from SAP, comparing against permitted limits, and alerting environmental compliance via Microsoft Teams and ServiceNow.
  tags:
  - manufacturing
  - sap
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: environmental
    port: 8080
    tools:
    - name: monitor-water-compliance
      description: 'Monitor water usage compliance: pull SAP data, compare limits, and alert compliance team.'
      inputParameters:
      - name: plant_code
        in: body
        type: string
        description: The plant code.
      - name: period
        in: body
        type: string
        description: The monitoring period.
      steps:
      - name: get-water-usage
        type: call
        call: sap.get-plant-water-usage
        with:
          plant: '{{plant_code}}'
          period: '{{period}}'
      - name: create-compliance-record
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Water usage compliance: Plant {{plant_code}} - {{period}}'
          description: 'Usage: {{get-water-usage.total_liters}} liters. Permit limit: {{get-water-usage.permit_limit}} liters. Utilization: {{get-water-usage.utilization_percent}}%.'
          category: environmental_compliance
          assignment_group: Environmental_Compliance
      - name: alert-team
        type: call
        call: msteams.send-message
        with:
          channel_id: environmental
          text: 'Water Usage Report: Plant {{plant_code}} ({{period}}). Usage: {{get-water-usage.total_liters}}L. Permit: {{get-water-usage.permit_limit}}L. Utilization: {{get-water-usage.utilization_percent}}%.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PLANT_METRICS_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: water
      path: /PlantWaterUsage(Plant='{{plant}}',Period='{{period}}')
      inputParameters:
      - name: plant
        in: path
      - name: period
        in: path
      operations:
      - name: get-plant-water-usage
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/sc_task
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves an employee profile from Workday by worker ID, returning name, department, job title, and manager information.

naftiko: '0.5'
info:
  label: Workday Employee Profile Lookup
  description: Retrieves an employee profile from Workday by worker ID, returning name, department, job title, and manager information.
  tags:
  - hr
  - workday
  - employee-data
capability:
  exposes:
  - type: mcp
    namespace: hr
    port: 8080
    tools:
    - name: get-employee-profile
      description: Look up a Coca-Cola employee profile in Workday by worker ID. Returns full name, department, job title, and manager.
      inputParameters:
      - name: worker_id
        in: body
        type: string
        description: The Workday worker ID, e.g. WD-00456.
      call: workday.get-worker
      with:
        worker_id: '{{worker_id}}'
      outputParameters:
      - name: full_name
        type: string
        mapping: $.worker.descriptor
      - name: department
        type: string
        mapping: $.worker.primaryPosition.department
      - name: job_title
        type: string
        mapping: $.worker.primaryPosition.jobTitle
      - name: manager
        type: string
        mapping: $.worker.primaryPosition.manager.descriptor
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /coca-cola/workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET

Pulls trade promotion results from Salesforce, enriches with point-of-sale data from Circana, and updates the Power BI retail analytics dashboard.

naftiko: '0.5'
info:
  label: Retail Promotion Performance Sync
  description: Pulls trade promotion results from Salesforce, enriches with point-of-sale data from Circana, and updates the Power BI retail analytics dashboard.
  tags:
  - marketing
  - salesforce
  - brand-management
  - power-bi
  - distribution
capability:
  exposes:
  - type: mcp
    namespace: trade-marketing
    port: 8080
    tools:
    - name: sync-promotion-performance
      description: 'Orchestrate retail promotion performance sync: pull Salesforce promotion data, enrich with Circana POS data, and refresh Power BI dashboard.'
      inputParameters:
      - name: promotion_id
        in: body
        type: string
        description: The Salesforce promotion record ID.
      - name: dataset_id
        in: body
        type: string
        description: The Power BI retail analytics dataset ID.
      steps:
      - name: get-promotion
        type: call
        call: salesforce.get-promotion
        with:
          promotion_id: '{{promotion_id}}'
      - name: get-pos-data
        type: call
        call: circana.get-pos-lift
        with:
          brand: '{{get-promotion.brand}}'
          start_date: '{{get-promotion.start_date}}'
          end_date: '{{get-promotion.end_date}}'
      - name: refresh-dashboard
        type: call
        call: powerbi.trigger-refresh
        with:
          dataset_id: '{{dataset_id}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: promotions
      path: /sobjects/Promotion__c/{{promotion_id}}
      inputParameters:
      - name: promotion_id
        in: path
      operations:
      - name: get-promotion
        method: GET
  - type: http
    namespace: circana
    baseUri: https://api.circana.com/v2
    authentication:
      type: bearer
      token: $secrets.circana_token
    resources:
    - name: pos-lift
      path: /pos/lift?brand={{brand}}&start={{start_date}}&end={{end_date}}
      inputParameters:
      - name: brand
        in: query
      - name: start_date
        in: query
      - name: end_date
        in: query
      operations:
      - name: get-pos-lift
        method: GET
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets/{{dataset_id}}/refreshes
      inputParameters:
      - name: dataset_id
        in: path
      operations:
      - name: trigger-refresh
        method: POST

Schedules syrup concentrate production by checking raw material availability in SAP, creating production orders, and notifying the bottling plant via Microsoft Teams.

naftiko: '0.5'
info:
  label: Syrup Concentrate Production Scheduling
  description: Schedules syrup concentrate production by checking raw material availability in SAP, creating production orders, and notifying the bottling plant via Microsoft Teams.
  tags:
  - manufacturing
  - supply-chain
  - sap
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: production-scheduling
    port: 8080
    tools:
    - name: schedule-concentrate-production
      description: 'Schedule concentrate production: check SAP raw materials, create production order, and notify bottling plant.'
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number for the concentrate.
      - name: plant_code
        in: body
        type: string
        description: The manufacturing plant code.
      - name: quantity
        in: body
        type: string
        description: The quantity to produce.
      - name: production_date
        in: body
        type: string
        description: The target production date in YYYY-MM-DD format.
      steps:
      - name: check-raw-materials
        type: call
        call: sap.check-material-availability
        with:
          material_number: '{{material_number}}'
          plant: '{{plant_code}}'
          quantity: '{{quantity}}'
      - name: create-production-order
        type: call
        call: sap.create-production-order
        with:
          material_number: '{{material_number}}'
          plant: '{{plant_code}}'
          quantity: '{{quantity}}'
          start_date: '{{production_date}}'
      - name: notify-plant
        type: call
        call: msteams.send-message
        with:
          channel_id: plant-{{plant_code}}-production
          text: 'Concentrate production scheduled: Material {{material_number}}. Qty: {{quantity}}. Date: {{production_date}}. Order: {{create-production-order.order_number}}. Raw material status: {{check-raw-materials.availability_status}}.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PRODUCTION_ORDER_2_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: availability
      path: /MaterialAvailability(Material='{{material_number}}',Plant='{{plant}}')
      inputParameters:
      - name: material_number
        in: path
      - name: plant
        in: path
      operations:
      - name: check-material-availability
        method: GET
    - name: production-orders
      path: /A_ProductionOrder_2
      operations:
      - name: create-production-order
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Records a goods receipt in SAP S/4HANA for a delivered purchase order line, updates inventory, and notifies the procurement team via Teams.

naftiko: '0.5'
info:
  label: SAP Goods Receipt Confirmation
  description: Records a goods receipt in SAP S/4HANA for a delivered purchase order line, updates inventory, and notifies the procurement team via Teams.
  tags:
  - supply-chain
  - sap
  - procurement
  - inventory
capability:
  exposes:
  - type: mcp
    namespace: supply-chain
    port: 8080
    tools:
    - name: confirm-goods-receipt
      description: Given a SAP purchase order number and delivery quantity, post a goods receipt in SAP S/4HANA to update inventory and notify the procurement team via Teams.
      inputParameters:
      - name: po_number
        in: body
        type: string
        description: The SAP purchase order number for the delivery.
      - name: quantity
        in: body
        type: number
        description: The quantity delivered.
      steps:
      - name: post-gr
        type: call
        call: sap.post-goods-receipt
        with:
          po_number: '{{po_number}}'
          quantity: '{{quantity}}'
      - name: notify-procurement
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_procurement_channel_id
          text: 'Goods receipt posted for PO {{po_number}}: {{quantity}} units received. GR Document: {{post-gr.material_document}}.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_DOCUMENT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: material-documents
      path: /A_MaterialDocumentHeader
      operations:
      - name: post-goods-receipt
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Tracks regulatory compliance documents by checking expiry dates in SharePoint, creating renewal tasks in ServiceNow, and alerting the legal and compliance team via Microsoft Teams.

naftiko: '0.5'
info:
  label: Regulatory Compliance Document Tracker
  description: Tracks regulatory compliance documents by checking expiry dates in SharePoint, creating renewal tasks in ServiceNow, and alerting the legal and compliance team via Microsoft Teams.
  tags:
  - manufacturing
  - sharepoint
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: regulatory-compliance
    port: 8080
    tools:
    - name: track-compliance-documents
      description: 'Track regulatory compliance docs: check SharePoint expiry dates, create ServiceNow tasks, and alert compliance team.'
      inputParameters:
      - name: document_category
        in: body
        type: string
        description: The compliance document category, e.g. FDA, EPA, OSHA.
      - name: plant_code
        in: body
        type: string
        description: The plant code.
      steps:
      - name: get-documents
        type: call
        call: sharepoint.get-compliance-docs
        with:
          site_id: regulatory
          category: '{{document_category}}'
          plant: '{{plant_code}}'
      - name: create-renewal-tasks
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Compliance document renewal: {{document_category}} for plant {{plant_code}}'
          description: 'Documents expiring: {{get-documents.expiring_count}}. Next expiry: {{get-documents.next_expiry_date}}.'
          category: regulatory_compliance
          assignment_group: Legal_Compliance
      - name: alert-compliance
        type: call
        call: msteams.send-message
        with:
          channel_id: regulatory-compliance
          text: 'Compliance Alert: {{document_category}} documents for plant {{plant_code}}. Expiring soon: {{get-documents.expiring_count}}. Next expiry: {{get-documents.next_expiry_date}}. Task: {{create-renewal-tasks.number}}.'
  consumes:
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: compliance-docs
      path: /sites/{{site_id}}/lists/{{category}}/items?$filter=Plant eq '{{plant}}'
      inputParameters:
      - name: site_id
        in: path
      - name: category
        in: path
      - name: plant
        in: query
      operations:
      - name: get-compliance-docs
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/sc_task
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Handles e-commerce order exceptions by pulling order details from BigCommerce, checking SAP inventory availability, and creating a Zendesk ticket for customer communication.

naftiko: '0.5'
info:
  label: E-Commerce Order Exception Handler
  description: Handles e-commerce order exceptions by pulling order details from BigCommerce, checking SAP inventory availability, and creating a Zendesk ticket for customer communication.
  tags:
  - distribution
  - bigcommerce
  - sap
  - zendesk
  - customer-service
capability:
  exposes:
  - type: mcp
    namespace: ecommerce
    port: 8080
    tools:
    - name: handle-order-exception
      description: 'Orchestrate e-commerce order exception: pull BigCommerce order, check SAP stock, and create Zendesk ticket.'
      inputParameters:
      - name: order_id
        in: body
        type: string
        description: The BigCommerce order ID.
      steps:
      - name: get-order
        type: call
        call: bigcommerce.get-order
        with:
          order_id: '{{order_id}}'
      - name: check-stock
        type: call
        call: sap.get-material-stock
        with:
          material_number: '{{get-order.sku}}'
      - name: create-support-ticket
        type: call
        call: zendesk.create-ticket
        with:
          subject: 'Order exception: #{{order_id}}'
          description: 'Order {{order_id}} for {{get-order.customer_name}} requires attention. Product: {{get-order.product_name}}. Available stock: {{check-stock.available_stock}}.'
          requester_email: '{{get-order.customer_email}}'
          priority: high
  consumes:
  - type: http
    namespace: bigcommerce
    baseUri: https://api.bigcommerce.com/stores/cocacola/v2
    authentication:
      type: apiKey
      header: X-Auth-Token
      value: $secrets.bigcommerce_token
    resources:
    - name: orders
      path: /orders/{{order_id}}
      inputParameters:
      - name: order_id
        in: path
      operations:
      - name: get-order
        method: GET
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: material-stock
      path: /A_MatlStkInAcctMod(Material='{{material_number}}')
      inputParameters:
      - name: material_number
        in: path
      operations:
      - name: get-material-stock
        method: GET
  - type: http
    namespace: zendesk
    baseUri: https://cocacola.zendesk.com/api/v2
    authentication:
      type: bearer
      token: $secrets.zendesk_token
    resources:
    - name: tickets
      path: /tickets
      operations:
      - name: create-ticket
        method: POST

Assesses ingredient supplier risk by pulling vendor data from SAP, checking compliance status in ServiceNow, and generating a risk report posted to Microsoft Teams.

naftiko: '0.5'
info:
  label: Ingredient Supplier Risk Assessment
  description: Assesses ingredient supplier risk by pulling vendor data from SAP, checking compliance status in ServiceNow, and generating a risk report posted to Microsoft Teams.
  tags:
  - procurement
  - supply-chain
  - sap
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: supplier-risk
    port: 8080
    tools:
    - name: assess-supplier-risk
      description: 'Assess ingredient supplier risk: pull SAP vendor data, check ServiceNow compliance, and post risk report.'
      inputParameters:
      - name: vendor_id
        in: body
        type: string
        description: The SAP vendor ID.
      steps:
      - name: get-vendor-data
        type: call
        call: sap.get-vendor
        with:
          vendor_id: '{{vendor_id}}'
      - name: check-compliance
        type: call
        call: servicenow.get-compliance-record
        with:
          vendor_name: '{{get-vendor-data.vendor_name}}'
      - name: post-risk-report
        type: call
        call: msteams.send-message
        with:
          channel_id: procurement-risk
          text: 'Supplier Risk Assessment: {{get-vendor-data.vendor_name}} ({{vendor_id}}). Country: {{get-vendor-data.country}}. Payment terms: {{get-vendor-data.payment_terms}}. Compliance status: {{check-compliance.status}}. Last audit: {{check-compliance.last_audit_date}}.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_BUSINESS_PARTNER
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: vendors
      path: /A_BusinessPartner('{{vendor_id}}')
      inputParameters:
      - name: vendor_id
        in: path
      operations:
      - name: get-vendor
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: compliance
      path: /table/vendor_compliance?sysparm_query=vendor_name={{vendor_name}}
      inputParameters:
      - name: vendor_name
        in: query
      operations:
      - name: get-compliance-record
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves campaign performance metrics from Google Analytics including sessions, bounce rate, and conversions for a specified campaign.

naftiko: '0.5'
info:
  label: Google Analytics Campaign Metrics
  description: Retrieves campaign performance metrics from Google Analytics including sessions, bounce rate, and conversions for a specified campaign.
  tags:
  - marketing
  - google-analytics
  - campaign-management
capability:
  exposes:
  - type: mcp
    namespace: marketing-analytics
    port: 8080
    tools:
    - name: get-campaign-metrics
      description: Fetch Google Analytics campaign performance data. Returns sessions, bounce rate, and goal completions for a given campaign.
      inputParameters:
      - name: campaign_id
        in: body
        type: string
        description: The Google Analytics campaign identifier.
      - name: date_range
        in: body
        type: string
        description: Date range in YYYY-MM-DD:YYYY-MM-DD format.
      call: ga.get-campaign-report
      with:
        campaign_id: '{{campaign_id}}'
        date_range: '{{date_range}}'
      outputParameters:
      - name: sessions
        type: string
        mapping: $.reports[0].data.totals[0].values[0]
      - name: bounce_rate
        type: string
        mapping: $.reports[0].data.totals[0].values[1]
      - name: conversions
        type: string
        mapping: $.reports[0].data.totals[0].values[2]
  consumes:
  - type: http
    namespace: ga
    baseUri: https://analyticsreporting.googleapis.com/v4
    authentication:
      type: bearer
      token: $secrets.google_analytics_token
    resources:
    - name: reports
      path: /reports:batchGet
      operations:
      - name: get-campaign-report
        method: POST

Monitors co-packer production by pulling production reports from SAP, validating against contracted volumes in Salesforce, and sending a variance report to Microsoft Teams.

naftiko: '0.5'
info:
  label: Co-Packer Production Monitoring
  description: Monitors co-packer production by pulling production reports from SAP, validating against contracted volumes in Salesforce, and sending a variance report to Microsoft Teams.
  tags:
  - manufacturing
  - supply-chain
  - sap
  - salesforce
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: co-packer
    port: 8080
    tools:
    - name: monitor-copacker-production
      description: 'Monitor co-packer production: pull SAP reports, validate against Salesforce contracts, and post variance.'
      inputParameters:
      - name: vendor_id
        in: body
        type: string
        description: The SAP co-packer vendor ID.
      - name: sf_contract_id
        in: body
        type: string
        description: The Salesforce contract record ID.
      - name: period
        in: body
        type: string
        description: The production period.
      steps:
      - name: get-production-report
        type: call
        call: sap.get-copacker-production
        with:
          vendor_id: '{{vendor_id}}'
          period: '{{period}}'
      - name: get-contracted-volumes
        type: call
        call: salesforce.get-contract
        with:
          contract_id: '{{sf_contract_id}}'
      - name: post-variance
        type: call
        call: msteams.send-message
        with:
          channel_id: co-packer-ops
          text: 'Co-Packer Report for {{get-production-report.vendor_name}} ({{period}}): Produced: {{get-production-report.actual_volume}}. Contracted: {{get-contracted-volumes.contracted_volume}}. Variance: {{get-production-report.variance_percent}}%.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PRODUCTION_ORDER_2_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: copacker-production
      path: /CopackerProduction(VendorId='{{vendor_id}}',Period='{{period}}')
      inputParameters:
      - name: vendor_id
        in: path
      - name: period
        in: path
      operations:
      - name: get-copacker-production
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: contracts
      path: /sobjects/Contract/{{contract_id}}
      inputParameters:
      - name: contract_id
        in: path
      operations:
      - name: get-contract
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

When a GitHub Actions workflow fails on a protected branch, opens a ServiceNow incident and posts a failure summary to the engineering Microsoft Teams channel.

naftiko: '0.5'
info:
  label: GitHub Pipeline Failure Alert
  description: When a GitHub Actions workflow fails on a protected branch, opens a ServiceNow incident and posts a failure summary to the engineering Microsoft Teams channel.
  tags:
  - devops
  - cicd
  - github
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: devops
    port: 8080
    tools:
    - name: handle-pipeline-failure
      description: Given a GitHub Actions run ID and repository, retrieve failure details, open a ServiceNow incident, and alert the engineering Teams channel. Use when a protected-branch workflow fails.
      inputParameters:
      - name: run_id
        in: body
        type: string
        description: The GitHub Actions workflow run ID.
      - name: repo
        in: body
        type: string
        description: The repository in owner/repo format, e.g. coca-cola/supply-chain-service.
      - name: branch
        in: body
        type: string
        description: The branch name where the failure occurred.
      steps:
      - name: get-run
        type: call
        call: github.get-workflow-run
        with:
          owner: coca-cola
          repo: '{{repo}}'
          run_id: '{{run_id}}'
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'CI/CD failure: {{repo}} / {{branch}}'
          description: 'GitHub Actions run {{run_id}} failed on branch {{branch}}. URL: {{get-run.html_url}}'
          urgency: '2'
      - name: post-alert
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_engineering_channel_id
          text: 'Pipeline Failure: {{repo}} | Branch: {{branch}} | Run: {{run_id}} | Incident: {{create-incident.number}} | Log: {{get-run.html_url}}'
  consumes:
  - type: http
    namespace: github
    baseUri: https://api.github.com
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: workflow-run
      path: /repos/{{owner}}/{{repo}}/actions/runs/{{run_id}}
      inputParameters:
      - name: owner
        in: path
      - name: repo
        in: path
      - name: run_id
        in: path
      operations:
      - name: get-workflow-run
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Synchronizes seasonal demand plans by pulling historical sales data from Teradata, adjusting SAP MRP parameters, and notifying supply chain planners via Microsoft Teams.

naftiko: '0.5'
info:
  label: Seasonal Demand Planning Sync
  description: Synchronizes seasonal demand plans by pulling historical sales data from Teradata, adjusting SAP MRP parameters, and notifying supply chain planners via Microsoft Teams.
  tags:
  - supply-chain
  - manufacturing
  - teradata
  - sap
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: seasonal-planning
    port: 8080
    tools:
    - name: sync-seasonal-demand
      description: 'Sync seasonal demand: pull Teradata sales history, adjust SAP MRP, and notify planners.'
      inputParameters:
      - name: product_group
        in: body
        type: string
        description: The product group code.
      - name: season
        in: body
        type: string
        description: 'The season: spring, summer, fall, winter.'
      steps:
      - name: get-historical-sales
        type: call
        call: teradata.get-seasonal-sales
        with:
          product_group: '{{product_group}}'
          season: '{{season}}'
      - name: update-mrp-parameters
        type: call
        call: sap.update-mrp-forecast
        with:
          product_group: '{{product_group}}'
          forecast_quantity: '{{get-historical-sales.projected_demand}}'
      - name: notify-planners
        type: call
        call: msteams.send-message
        with:
          channel_id: demand-planning
          text: 'Seasonal demand update for {{product_group}} ({{season}}): Historical avg: {{get-historical-sales.avg_volume}}. Projected demand: {{get-historical-sales.projected_demand}}. SAP MRP parameters updated.'
  consumes:
  - type: http
    namespace: teradata
    baseUri: https://coca-cola-td.teradata.com/api/v1
    authentication:
      type: bearer
      token: $secrets.teradata_token
    resources:
    - name: seasonal-sales
      path: /queries/seasonal-sales?product_group={{product_group}}&season={{season}}
      inputParameters:
      - name: product_group
        in: query
      - name: season
        in: query
      operations:
      - name: get-seasonal-sales
        method: GET
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_MRP_FORECAST_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: mrp-forecast
      path: /MRPForecast
      operations:
      - name: update-mrp-forecast
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Monitors contract renewal dates by checking SAP vendor contracts, creating renewal tasks in ServiceNow, and sending reminders to procurement managers via Microsoft Outlook.

naftiko: '0.5'
info:
  label: Contract Renewal Reminder Workflow
  description: Monitors contract renewal dates by checking SAP vendor contracts, creating renewal tasks in ServiceNow, and sending reminders to procurement managers via Microsoft Outlook.
  tags:
  - procurement
  - sap
  - servicenow
  - microsoft-outlook
capability:
  exposes:
  - type: mcp
    namespace: contract-management
    port: 8080
    tools:
    - name: trigger-renewal-reminder
      description: 'Orchestrate contract renewal reminder: check SAP contract, create ServiceNow task, and send Outlook reminder.'
      inputParameters:
      - name: contract_number
        in: body
        type: string
        description: The SAP contract number.
      steps:
      - name: get-contract
        type: call
        call: sap.get-contract
        with:
          contract_number: '{{contract_number}}'
      - name: create-renewal-task
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Contract renewal: {{contract_number}} - {{get-contract.vendor_name}}'
          due_date: '{{get-contract.expiry_date}}'
          assignment_group: Procurement_Management
      - name: send-reminder-email
        type: call
        call: outlook.send-email
        with:
          to: '{{get-contract.procurement_manager_email}}'
          subject: 'Contract Renewal Reminder: {{get-contract.vendor_name}}'
          body: 'Contract {{contract_number}} with {{get-contract.vendor_name}} expires on {{get-contract.expiry_date}}. Value: ${{get-contract.total_value}}. ServiceNow task: {{create-renewal-task.number}}.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PURCHASECONTRACT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: contracts
      path: /A_PurchaseContract('{{contract_number}}')
      inputParameters:
      - name: contract_number
        in: path
      operations:
      - name: get-contract
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/sc_task
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: outlook
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /me/sendMail
      operations:
      - name: send-email
        method: POST

When a bottling line goes down, retrieves equipment status from SAP, creates a ServiceNow maintenance ticket, and notifies the plant operations team via Microsoft Teams.

naftiko: '0.5'
info:
  label: Bottling Line Downtime Response
  description: When a bottling line goes down, retrieves equipment status from SAP, creates a ServiceNow maintenance ticket, and notifies the plant operations team via Microsoft Teams.
  tags:
  - manufacturing
  - sap
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: manufacturing-ops
    port: 8080
    tools:
    - name: handle-bottling-downtime
      description: 'Orchestrate bottling line downtime response: check SAP equipment status, create ServiceNow ticket, and notify plant ops via Teams.'
      inputParameters:
      - name: equipment_id
        in: body
        type: string
        description: The SAP equipment ID for the bottling line.
      - name: plant_code
        in: body
        type: string
        description: The plant code where the downtime occurred.
      steps:
      - name: get-equipment-status
        type: call
        call: sap.get-equipment
        with:
          equipment_id: '{{equipment_id}}'
      - name: create-maintenance-ticket
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Bottling line downtime: {{equipment_id}} at plant {{plant_code}}'
          category: plant_maintenance
          urgency: '1'
          assignment_group: Plant_Maintenance_{{plant_code}}
      - name: notify-plant-ops
        type: call
        call: msteams.send-message
        with:
          channel_id: plant-ops-{{plant_code}}
          text: 'ALERT: Bottling line {{equipment_id}} is down at plant {{plant_code}}. Equipment status: {{get-equipment-status.system_status}}. Maintenance ticket: {{create-maintenance-ticket.number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_EQUIPMENT
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: equipment
      path: /A_Equipment('{{equipment_id}}')
      inputParameters:
      - name: equipment_id
        in: path
      operations:
      - name: get-equipment
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Aggregates marketing attribution data from Google Analytics, Adobe Analytics, and LinkedIn to create a unified campaign performance view in Salesforce.

naftiko: '0.5'
info:
  label: Multi-Channel Marketing Attribution
  description: Aggregates marketing attribution data from Google Analytics, Adobe Analytics, and LinkedIn to create a unified campaign performance view in Salesforce.
  tags:
  - marketing
  - google-analytics
  - adobe-analytics
  - linkedin
  - salesforce
capability:
  exposes:
  - type: mcp
    namespace: marketing-attribution
    port: 8080
    tools:
    - name: aggregate-attribution
      description: 'Aggregate marketing attribution: pull GA, Adobe Analytics, and LinkedIn data, then update Salesforce campaign.'
      inputParameters:
      - name: campaign_id
        in: body
        type: string
        description: The Salesforce campaign ID.
      - name: ga_campaign_id
        in: body
        type: string
        description: The Google Analytics campaign ID.
      - name: linkedin_campaign_id
        in: body
        type: string
        description: The LinkedIn campaign ID.
      steps:
      - name: get-ga-attribution
        type: call
        call: ga.get-campaign-report
        with:
          campaign_id: '{{ga_campaign_id}}'
      - name: get-adobe-attribution
        type: call
        call: adobe.get-campaign-attribution
        with:
          campaign_id: '{{campaign_id}}'
      - name: get-linkedin-attribution
        type: call
        call: linkedin.get-campaign-analytics
        with:
          campaign_id: '{{linkedin_campaign_id}}'
      - name: update-sf-campaign
        type: call
        call: salesforce.update-campaign
        with:
          campaign_id: '{{campaign_id}}'
          web_conversions: '{{get-ga-attribution.conversions}}'
          display_impressions: '{{get-adobe-attribution.impressions}}'
          social_engagements: '{{get-linkedin-attribution.engagements}}'
  consumes:
  - type: http
    namespace: ga
    baseUri: https://analyticsreporting.googleapis.com/v4
    authentication:
      type: bearer
      token: $secrets.google_analytics_token
    resources:
    - name: reports
      path: /reports:batchGet
      operations:
      - name: get-campaign-report
        method: POST
  - type: http
    namespace: adobe
    baseUri: https://analytics.adobe.io/api/cocacola
    authentication:
      type: bearer
      token: $secrets.adobe_analytics_token
    resources:
    - name: attribution
      path: /attribution
      operations:
      - name: get-campaign-attribution
        method: POST
  - type: http
    namespace: linkedin
    baseUri: https://api.linkedin.com/v2
    authentication:
      type: bearer
      token: $secrets.linkedin_token
    resources:
    - name: analytics
      path: /adAnalyticsV2?campaigns=urn:li:sponsoredCampaign:{{campaign_id}}
      inputParameters:
      - name: campaign_id
        in: query
      operations:
      - name: get-campaign-analytics
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: campaigns
      path: /sobjects/Campaign/{{campaign_id}}
      inputParameters:
      - name: campaign_id
        in: path
      operations:
      - name: update-campaign
        method: PATCH

Queries Salesforce for opportunities that have changed stage in the last 24 hours and logs the changes to a Power BI dataset for sales pipeline reporting.

naftiko: '0.5'
info:
  label: Salesforce Opportunity Stage Sync
  description: Queries Salesforce for opportunities that have changed stage in the last 24 hours and logs the changes to a Power BI dataset for sales pipeline reporting.
  tags:
  - sales
  - crm
  - salesforce
  - power-bi
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: sales-reporting
    port: 8080
    tools:
    - name: sync-opportunity-stages
      description: Fetch all Salesforce opportunities with stage changes in the last 24 hours and push the updated records to the Power BI sales pipeline dataset. Use for daily sales pipeline refresh.
      steps:
      - name: get-changed-opps
        type: call
        call: salesforce.query-opportunities
        with:
          soql: SELECT Id,Name,StageName,Amount,CloseDate FROM Opportunity WHERE LastModifiedDate = LAST_N_DAYS:1
      - name: push-to-powerbi
        type: call
        call: powerbi.push-rows
        with:
          dataset_id: $secrets.powerbi_pipeline_dataset_id
          table_name: Opportunities
          rows: '{{get-changed-opps.records}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://cocacola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: query
      path: /query
      inputParameters:
      - name: soql
        in: query
      operations:
      - name: query-opportunities
        method: GET
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: dataset-rows
      path: /datasets/{{dataset_id}}/tables/{{table_name}}/rows
      inputParameters:
      - name: dataset_id
        in: path
      - name: table_name
        in: path
      operations:
      - name: push-rows
        method: POST

Triggers a scheduled refresh for a Power BI dataset and monitors refresh status, notifying the data analytics team via Teams when complete or failed.

naftiko: '0.5'
info:
  label: Power BI Dataset Refresh Trigger
  description: Triggers a scheduled refresh for a Power BI dataset and monitors refresh status, notifying the data analytics team via Teams when complete or failed.
  tags:
  - data
  - analytics
  - power-bi
  - microsoft-teams
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: data-analytics
    port: 8080
    tools:
    - name: trigger-dataset-refresh
      description: Trigger a Power BI dataset refresh for the given dataset ID and post completion status to the analytics Teams channel. Use for scheduled BI report refresh automation.
      inputParameters:
      - name: dataset_id
        in: body
        type: string
        description: The Power BI dataset ID to refresh.
      steps:
      - name: start-refresh
        type: call
        call: powerbi.refresh-dataset
        with:
          dataset_id: '{{dataset_id}}'
      - name: notify-team
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_analytics_channel_id
          text: Power BI dataset {{dataset_id}} refresh triggered successfully.
  consumes:
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: dataset-refreshes
      path: /datasets/{{dataset_id}}/refreshes
      inputParameters:
      - name: dataset_id
        in: path
      operations:
      - name: refresh-dataset
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves the latest build status for a specified Azure DevOps pipeline, returning build result, duration, and triggered by.

naftiko: '0.5'
info:
  label: Azure DevOps Build Status
  description: Retrieves the latest build status for a specified Azure DevOps pipeline, returning build result, duration, and triggered by.
  tags:
  - devops
  - azure-devops
  - ci-cd
capability:
  exposes:
  - type: mcp
    namespace: devops
    port: 8080
    tools:
    - name: get-build-status
      description: Check the latest build status for an Azure DevOps pipeline. Returns result, duration, and source branch.
      inputParameters:
      - name: pipeline_id
        in: body
        type: string
        description: The Azure DevOps pipeline definition ID.
      call: azdo.get-latest-build
      with:
        pipeline_id: '{{pipeline_id}}'
      outputParameters:
      - name: result
        type: string
        mapping: $.value[0].result
      - name: duration
        type: string
        mapping: $.value[0].finishTime
      - name: source_branch
        type: string
        mapping: $.value[0].sourceBranch
  consumes:
  - type: http
    namespace: azdo
    baseUri: https://dev.azure.com/coca-cola
    authentication:
      type: basic
      username: $secrets.azdo_user
      password: $secrets.azdo_pat
    resources:
    - name: builds
      path: /_apis/build/builds?definitions={{pipeline_id}}&$top=1&api-version=7.0
      inputParameters:
      - name: pipeline_id
        in: query
      operations:
      - name: get-latest-build
        method: GET

Rebalances warehouse inventory by checking stock levels across plants in SAP, creating stock transfer orders, and logging the rebalance action in ServiceNow.

naftiko: '0.5'
info:
  label: Warehouse Inventory Rebalance
  description: Rebalances warehouse inventory by checking stock levels across plants in SAP, creating stock transfer orders, and logging the rebalance action in ServiceNow.
  tags:
  - supply-chain
  - distribution
  - sap
  - servicenow
capability:
  exposes:
  - type: mcp
    namespace: warehouse-ops
    port: 8080
    tools:
    - name: rebalance-inventory
      description: 'Orchestrate inventory rebalance: check multi-plant stock in SAP, create transfer orders, and log in ServiceNow.'
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number.
      - name: source_plant
        in: body
        type: string
        description: The source plant code.
      - name: target_plant
        in: body
        type: string
        description: The target plant code.
      - name: quantity
        in: body
        type: string
        description: The quantity to transfer.
      steps:
      - name: check-source-stock
        type: call
        call: sap.get-material-stock
        with:
          material_number: '{{material_number}}'
          plant: '{{source_plant}}'
      - name: create-transfer-order
        type: call
        call: sap.create-stock-transfer
        with:
          material_number: '{{material_number}}'
          source_plant: '{{source_plant}}'
          target_plant: '{{target_plant}}'
          quantity: '{{quantity}}'
      - name: log-rebalance
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Inventory rebalance: {{material_number}} from {{source_plant}} to {{target_plant}}'
          description: 'Transferred {{quantity}} units. Transfer order: {{create-transfer-order.transfer_order_number}}'
          category: warehouse_operations
          assignment_group: Warehouse_Ops
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: material-stock
      path: /A_MatlStkInAcctMod(Material='{{material_number}}',Plant='{{plant}}')
      inputParameters:
      - name: material_number
        in: path
      - name: plant
        in: path
      operations:
      - name: get-material-stock
        method: GET
    - name: stock-transfers
      path: /A_StockTransferOrder
      operations:
      - name: create-stock-transfer
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST

Queries Datadog Logs for error spikes in a specified service over the past hour and returns a ranked summary of the top error patterns.

naftiko: '0.5'
info:
  label: Datadog Log Anomaly Investigation
  description: Queries Datadog Logs for error spikes in a specified service over the past hour and returns a ranked summary of the top error patterns.
  tags:
  - observability
  - datadog
  - logging
  - incident-response
capability:
  exposes:
  - type: mcp
    namespace: log-analysis
    port: 8080
    tools:
    - name: get-error-log-summary
      description: Query Datadog Logs for the top error patterns in a given service over the past hour. Returns ranked error messages and counts for rapid incident triage.
      inputParameters:
      - name: service_name
        in: body
        type: string
        description: The Datadog service name to query logs for, e.g. beverage-order-service.
      call: datadog.search-logs
      with:
        query: service:{{service_name}} status:error
      outputParameters:
      - name: logs
        type: array
        mapping: $.data
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: logs
      path: /logs-queries/list
      inputParameters:
      - name: query
        in: query
      operations:
      - name: search-logs
        method: GET

Looks up a SAP S/4HANA purchase order by PO number and returns header status, vendor, total value, and open line items.

naftiko: '0.5'
info:
  label: SAP Purchase Order Lookup
  description: Looks up a SAP S/4HANA purchase order by PO number and returns header status, vendor, total value, and open line items.
  tags:
  - finance
  - procurement
  - sap
  - erp
capability:
  exposes:
  - type: mcp
    namespace: erp
    port: 8080
    tools:
    - name: get-purchase-order
      description: Look up a Coca-Cola SAP S/4HANA purchase order by PO number. Returns status, vendor name, total amount, and currency. Use for procurement tracking or invoice reconciliation.
      inputParameters:
      - name: po_number
        in: body
        type: string
        description: The SAP purchase order number, e.g. 4500001234.
      call: sap.get-po
      with:
        po_number: '{{po_number}}'
      outputParameters:
      - name: status
        type: string
        mapping: $.d.OverallStatus
      - name: vendor
        type: string
        mapping: $.d.Supplier.CompanyName
      - name: total_value
        type: string
        mapping: $.d.TotalAmount
      - name: currency
        type: string
        mapping: $.d.TransactionCurrency
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/MM_PUR_PO_MAINT_V2_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: purchase-orders
      path: /A_PurchaseOrder('{{po_number}}')
      inputParameters:
      - name: po_number
        in: path
      operations:
      - name: get-po
        method: GET

Retrieves the current status of a ServiceNow incident by incident number, returning state, priority, assigned group, and resolution notes.

naftiko: '0.5'
info:
  label: ServiceNow Incident Status Lookup
  description: Retrieves the current status of a ServiceNow incident by incident number, returning state, priority, assigned group, and resolution notes.
  tags:
  - it-operations
  - servicenow
  - incident-management
capability:
  exposes:
  - type: mcp
    namespace: itsm
    port: 8080
    tools:
    - name: get-incident-status
      description: Look up a ServiceNow incident by number. Returns current state, priority, assignment group, and short description.
      inputParameters:
      - name: incident_number
        in: body
        type: string
        description: The ServiceNow incident number, e.g. INC0012345.
      call: servicenow.get-incident
      with:
        incident_number: '{{incident_number}}'
      outputParameters:
      - name: state
        type: string
        mapping: $.result.state
      - name: priority
        type: string
        mapping: $.result.priority
      - name: assignment_group
        type: string
        mapping: $.result.assignment_group.display_value
      - name: short_description
        type: string
        mapping: $.result.short_description
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident?sysparm_query=number={{incident_number}}
      inputParameters:
      - name: incident_number
        in: query
      operations:
      - name: get-incident
        method: GET

Manages IT asset lifecycle by checking asset status in ServiceNow, verifying user assignment in Workday, and updating the asset tracking record.

naftiko: '0.5'
info:
  label: IT Asset Lifecycle Management
  description: Manages IT asset lifecycle by checking asset status in ServiceNow, verifying user assignment in Workday, and updating the asset tracking record.
  tags:
  - it-operations
  - servicenow
  - workday
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: it-asset
    port: 8080
    tools:
    - name: manage-asset-lifecycle
      description: 'Manage IT asset lifecycle: check ServiceNow asset, verify Workday user, and update tracking.'
      inputParameters:
      - name: asset_tag
        in: body
        type: string
        description: The ServiceNow asset tag.
      steps:
      - name: get-asset
        type: call
        call: servicenow.get-asset
        with:
          asset_tag: '{{asset_tag}}'
      - name: get-assigned-user
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{get-asset.assigned_to_worker_id}}'
      - name: update-asset-record
        type: call
        call: servicenow.update-asset
        with:
          asset_tag: '{{asset_tag}}'
          assigned_user: '{{get-assigned-user.full_name}}'
          department: '{{get-assigned-user.department}}'
      - name: notify-it-ops
        type: call
        call: msteams.send-message
        with:
          channel_id: it-asset-management
          text: 'Asset {{asset_tag}} verified. Assigned to: {{get-assigned-user.full_name}} ({{get-assigned-user.department}}). Status: {{get-asset.status}}. Age: {{get-asset.age_months}} months.'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: assets
      path: /table/alm_hardware?sysparm_query=asset_tag={{asset_tag}}
      inputParameters:
      - name: asset_tag
        in: query
      operations:
      - name: get-asset
        method: GET
      - name: update-asset
        method: PATCH
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /coca-cola/workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Given a Salesforce account ID, retrieves account details, open opportunities, and recent service cases to produce a unified health summary for the account manager.

naftiko: '0.5'
info:
  label: Salesforce Account Health Check
  description: Given a Salesforce account ID, retrieves account details, open opportunities, and recent service cases to produce a unified health summary for the account manager.
  tags:
  - sales
  - crm
  - salesforce
  - customer-success
capability:
  exposes:
  - type: mcp
    namespace: crm
    port: 8080
    tools:
    - name: get-account-health
      description: Given a Salesforce account ID, retrieve the account profile, open opportunities, and recent service cases. Returns a consolidated health view for account review meetings.
      inputParameters:
      - name: account_id
        in: body
        type: string
        description: The Salesforce Account ID (18-character Salesforce ID).
      steps:
      - name: get-account
        type: call
        call: salesforce-acct.get-account
        with:
          account_id: '{{account_id}}'
      - name: get-opportunities
        type: call
        call: salesforce-opp.query-opportunities
        with:
          soql: SELECT Id,Name,StageName,Amount FROM Opportunity WHERE AccountId='{{account_id}}' AND IsClosed=false
      - name: get-cases
        type: call
        call: salesforce-case.query-cases
        with:
          soql: SELECT Id,Subject,Status,CreatedDate FROM Case WHERE AccountId='{{account_id}}' ORDER BY CreatedDate DESC LIMIT 5
  consumes:
  - type: http
    namespace: salesforce-acct
    baseUri: https://cocacola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: account
      path: /sobjects/Account/{{account_id}}
      inputParameters:
      - name: account_id
        in: path
      operations:
      - name: get-account
        method: GET
  - type: http
    namespace: salesforce-opp
    baseUri: https://cocacola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: query
      path: /query
      inputParameters:
      - name: soql
        in: query
      operations:
      - name: query-opportunities
        method: GET
  - type: http
    namespace: salesforce-case
    baseUri: https://cocacola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: query
      path: /query
      inputParameters:
      - name: soql
        in: query
      operations:
      - name: query-cases
        method: GET

Pulls production order data from SAP, calculates yield variance, refreshes the Power BI manufacturing dashboard, and posts a yield summary to Microsoft Teams.

naftiko: '0.5'
info:
  label: Production Yield Analysis and Report
  description: Pulls production order data from SAP, calculates yield variance, refreshes the Power BI manufacturing dashboard, and posts a yield summary to Microsoft Teams.
  tags:
  - manufacturing
  - sap
  - power-bi
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: manufacturing-analytics
    port: 8080
    tools:
    - name: analyze-production-yield
      description: 'Orchestrate production yield analysis: pull SAP production data, refresh Power BI dashboard, and post summary to Teams.'
      inputParameters:
      - name: plant_code
        in: body
        type: string
        description: The manufacturing plant code.
      - name: production_date
        in: body
        type: string
        description: The production date in YYYY-MM-DD format.
      - name: dataset_id
        in: body
        type: string
        description: The Power BI manufacturing dataset ID.
      steps:
      - name: get-production-orders
        type: call
        call: sap.get-production-orders-by-plant
        with:
          plant_code: '{{plant_code}}'
          date: '{{production_date}}'
      - name: refresh-dashboard
        type: call
        call: powerbi.trigger-refresh
        with:
          dataset_id: '{{dataset_id}}'
      - name: post-yield-summary
        type: call
        call: msteams.send-message
        with:
          channel_id: manufacturing-ops
          text: 'Production Yield Report for Plant {{plant_code}} on {{production_date}}: Total orders: {{get-production-orders.count}}. Dashboard refresh status: {{refresh-dashboard.status}}.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PRODUCTION_ORDER_2_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: production-orders
      path: /A_ProductionOrder_2?$filter=ProductionPlant eq '{{plant_code}}' and MfgOrderPlannedStartDate eq datetime'{{date}}'
      inputParameters:
      - name: plant_code
        in: query
      - name: date
        in: query
      operations:
      - name: get-production-orders-by-plant
        method: GET
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets/{{dataset_id}}/refreshes
      inputParameters:
      - name: dataset_id
        in: path
      operations:
      - name: trigger-refresh
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves a SAP plant maintenance order by order number, returning equipment, functional location, priority, and system status.

naftiko: '0.5'
info:
  label: SAP Plant Maintenance Order Lookup
  description: Retrieves a SAP plant maintenance order by order number, returning equipment, functional location, priority, and system status.
  tags:
  - manufacturing
  - sap
  - maintenance
capability:
  exposes:
  - type: mcp
    namespace: plant-maintenance
    port: 8080
    tools:
    - name: get-maintenance-order
      description: Look up a SAP plant maintenance order. Returns equipment ID, functional location, priority, and current status.
      inputParameters:
      - name: order_number
        in: body
        type: string
        description: The SAP maintenance order number.
      call: sap.get-maintenance-order
      with:
        order_number: '{{order_number}}'
      outputParameters:
      - name: equipment
        type: string
        mapping: $.d.Equipment
      - name: functional_location
        type: string
        mapping: $.d.FunctionalLocation
      - name: priority
        type: string
        mapping: $.d.MaintenanceOrderPriority
      - name: status
        type: string
        mapping: $.d.MaintenanceOrderSystemStatus
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_MAINTENANCEORDER
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: maintenance-orders
      path: /MaintenanceOrder('{{order_number}}')
      inputParameters:
      - name: order_number
        in: path
      operations:
      - name: get-maintenance-order
        method: GET

Syncs LinkedIn employer branding campaign metrics to Workday recruiting analytics and posts a talent acquisition report to Microsoft Teams.

naftiko: '0.5'
info:
  label: LinkedIn Employer Brand Campaign Sync
  description: Syncs LinkedIn employer branding campaign metrics to Workday recruiting analytics and posts a talent acquisition report to Microsoft Teams.
  tags:
  - hr
  - marketing
  - linkedin
  - workday
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: talent-marketing
    port: 8080
    tools:
    - name: sync-employer-brand
      description: Sync LinkedIn employer brand campaign data to Workday and post report to Teams.
      inputParameters:
      - name: campaign_id
        in: body
        type: string
        description: The LinkedIn campaign ID.
      steps:
      - name: get-linkedin-metrics
        type: call
        call: linkedin.get-campaign-analytics
        with:
          campaign_id: '{{campaign_id}}'
      - name: update-workday-recruiting
        type: call
        call: workday.update-recruiting-metrics
        with:
          source: linkedin
          impressions: '{{get-linkedin-metrics.impressions}}'
          applications: '{{get-linkedin-metrics.conversions}}'
      - name: post-report
        type: call
        call: msteams.send-message
        with:
          channel_id: talent-acquisition
          text: 'LinkedIn Employer Brand Report: Impressions: {{get-linkedin-metrics.impressions}}. Clicks: {{get-linkedin-metrics.clicks}}. Applications: {{get-linkedin-metrics.conversions}}. Cost per application: ${{get-linkedin-metrics.cost_per_conversion}}.'
  consumes:
  - type: http
    namespace: linkedin
    baseUri: https://api.linkedin.com/v2
    authentication:
      type: bearer
      token: $secrets.linkedin_token
    resources:
    - name: campaign-analytics
      path: /adAnalyticsV2?campaigns=urn:li:sponsoredCampaign:{{campaign_id}}
      inputParameters:
      - name: campaign_id
        in: query
      operations:
      - name: get-campaign-analytics
        method: GET
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: recruiting-metrics
      path: /coca-cola/recruiting/metrics
      operations:
      - name: update-recruiting-metrics
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

When an employee termination is recorded in Workday, deactivates the Microsoft 365 account, closes open ServiceNow tickets, and notifies the HR team via Teams.

naftiko: '0.5'
info:
  label: Employee Offboarding Workflow
  description: When an employee termination is recorded in Workday, deactivates the Microsoft 365 account, closes open ServiceNow tickets, and notifies the HR team via Teams.
  tags:
  - hr
  - offboarding
  - workday
  - servicenow
  - microsoft-365
capability:
  exposes:
  - type: mcp
    namespace: hr-offboarding
    port: 8080
    tools:
    - name: trigger-offboarding
      description: Given a Workday employee ID and termination date, deactivate the Microsoft 365 account, close open ServiceNow tickets assigned to the user, and notify the HR business partner via Teams.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The Workday worker ID of the departing employee.
      - name: termination_date
        in: body
        type: string
        description: The termination effective date in ISO 8601 format.
      steps:
      - name: get-worker
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{employee_id}}'
      - name: disable-account
        type: call
        call: msgraph.disable-user
        with:
          user_upn: '{{get-worker.work_email}}'
      - name: close-tickets
        type: call
        call: servicenow.close-user-incidents
        with:
          caller_email: '{{get-worker.work_email}}'
      - name: notify-hr
        type: call
        call: msteams-notify.send-message
        with:
          recipient_upn: '{{get-worker.manager_email}}'
          text: 'Offboarding complete for {{get-worker.full_name}} (termination date: {{termination_date}}). M365 account disabled.'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /coca-cola/workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: msgraph
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: user-account
      path: /users/{{user_upn}}
      inputParameters:
      - name: user_upn
        in: path
      operations:
      - name: disable-user
        method: PATCH
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: close-user-incidents
        method: PATCH
  - type: http
    namespace: msteams-notify
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: mail
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Assembles a QBR data pack by pulling account health, open opportunities, and case volume from Salesforce, then posts a summary to the sales leadership Teams channel.

naftiko: '0.5'
info:
  label: Salesforce Quarterly Business Review Pack Builder
  description: Assembles a QBR data pack by pulling account health, open opportunities, and case volume from Salesforce, then posts a summary to the sales leadership Teams channel.
  tags:
  - sales
  - salesforce
  - reporting
  - microsoft-teams
  - qbr
capability:
  exposes:
  - type: mcp
    namespace: sales-qbr
    port: 8080
    tools:
    - name: build-qbr-pack
      description: Given a Salesforce account ID, compile a QBR data pack with account health metrics, pipeline, and case volume, then post a summary to the sales leadership Teams channel.
      inputParameters:
      - name: account_id
        in: body
        type: string
        description: The Salesforce Account ID for the QBR.
      steps:
      - name: get-account
        type: call
        call: salesforce.get-account
        with:
          account_id: '{{account_id}}'
      - name: get-pipeline
        type: call
        call: salesforce-pipeline.query-opportunities
        with:
          soql: SELECT Id,Name,Amount,StageName FROM Opportunity WHERE AccountId='{{account_id}}' AND IsClosed=false
      - name: post-summary
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_sales_channel_id
          text: 'QBR Pack ready for {{get-account.Name}}: {{get-pipeline.totalSize}} open opportunities compiled.'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://cocacola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: account
      path: /sobjects/Account/{{account_id}}
      inputParameters:
      - name: account_id
        in: path
      operations:
      - name: get-account
        method: GET
  - type: http
    namespace: salesforce-pipeline
    baseUri: https://cocacola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: query
      path: /query
      inputParameters:
      - name: soql
        in: query
      operations:
      - name: query-opportunities
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Schedules fleet vehicle maintenance by checking SAP equipment records, creating a ServiceNow work order, and notifying the fleet management team via Microsoft Teams.

naftiko: '0.5'
info:
  label: Fleet Vehicle Maintenance Scheduler
  description: Schedules fleet vehicle maintenance by checking SAP equipment records, creating a ServiceNow work order, and notifying the fleet management team via Microsoft Teams.
  tags:
  - distribution
  - sap
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: fleet-ops
    port: 8080
    tools:
    - name: schedule-vehicle-maintenance
      description: 'Orchestrate fleet maintenance: check SAP equipment, create ServiceNow work order, and notify fleet team.'
      inputParameters:
      - name: vehicle_id
        in: body
        type: string
        description: The SAP equipment ID for the fleet vehicle.
      - name: maintenance_type
        in: body
        type: string
        description: 'Type of maintenance: preventive, corrective, inspection.'
      steps:
      - name: get-vehicle-record
        type: call
        call: sap.get-equipment
        with:
          equipment_id: '{{vehicle_id}}'
      - name: create-work-order
        type: call
        call: servicenow.create-work-order
        with:
          short_description: 'Fleet maintenance: {{vehicle_id}} - {{maintenance_type}}'
          assignment_group: Fleet_Maintenance
          vehicle_id: '{{vehicle_id}}'
          last_service_date: '{{get-vehicle-record.last_maintenance_date}}'
      - name: notify-fleet-team
        type: call
        call: msteams.send-message
        with:
          channel_id: fleet-management
          text: 'Maintenance scheduled for vehicle {{vehicle_id}}. Type: {{maintenance_type}}. Last service: {{get-vehicle-record.last_maintenance_date}}. Work order: {{create-work-order.number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_EQUIPMENT
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: equipment
      path: /A_Equipment('{{equipment_id}}')
      inputParameters:
      - name: equipment_id
        in: path
      operations:
      - name: get-equipment
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: work-orders
      path: /table/wm_order
      operations:
      - name: create-work-order
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

When a new hire record is created in Workday, opens a ServiceNow onboarding task, provisions a Microsoft 365 account, and sends a Microsoft Teams welcome message.

naftiko: '0.5'
info:
  label: New Hire Onboarding Orchestrator
  description: When a new hire record is created in Workday, opens a ServiceNow onboarding task, provisions a Microsoft 365 account, and sends a Microsoft Teams welcome message.
  tags:
  - hr
  - onboarding
  - workday
  - servicenow
  - microsoft-teams
  - microsoft-365
capability:
  exposes:
  - type: mcp
    namespace: hr-onboarding
    port: 8080
    tools:
    - name: trigger-onboarding
      description: Given a Workday employee ID and start date, orchestrate the full new hire onboarding sequence across ServiceNow, Microsoft 365, and Microsoft Teams.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The Workday worker ID for the new hire, e.g. WD-00123.
      - name: start_date
        in: body
        type: string
        description: The employee start date in ISO 8601 format (YYYY-MM-DD).
      steps:
      - name: get-worker
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{employee_id}}'
      - name: create-onboarding-ticket
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'New hire onboarding: {{get-worker.full_name}}'
          category: hr_onboarding
          assigned_to: IT_Onboarding_Team
      - name: provision-m365
        type: call
        call: msgraph.create-user
        with:
          displayName: '{{get-worker.full_name}}'
          mail: '{{get-worker.work_email}}'
          department: '{{get-worker.department}}'
      - name: send-welcome
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{get-worker.work_email}}'
          text: Welcome to Coca-Cola, {{get-worker.first_name}}! Your IT onboarding ticket is {{create-onboarding-ticket.number}}.
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /coca-cola/workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msgraph
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: users
      path: /users
      operations:
      - name: create-user
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: chats
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

When a cold chain temperature breach is detected, retrieves shipment details from SAP, creates a quality incident in ServiceNow, and alerts the distribution team via Microsoft Teams.

naftiko: '0.5'
info:
  label: Cold Chain Temperature Breach Response
  description: When a cold chain temperature breach is detected, retrieves shipment details from SAP, creates a quality incident in ServiceNow, and alerts the distribution team via Microsoft Teams.
  tags:
  - supply-chain
  - distribution
  - sap
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: cold-chain
    port: 8080
    tools:
    - name: handle-temperature-breach
      description: 'Orchestrate cold chain breach response: pull SAP shipment data, create quality incident, and alert distribution team.'
      inputParameters:
      - name: shipment_id
        in: body
        type: string
        description: The SAP shipment document number.
      - name: temperature_reading
        in: body
        type: string
        description: The recorded temperature in Celsius.
      steps:
      - name: get-shipment
        type: call
        call: sap.get-shipment
        with:
          shipment_id: '{{shipment_id}}'
      - name: create-quality-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Cold chain breach: Shipment {{shipment_id}} at {{temperature_reading}}C'
          category: quality_cold_chain
          urgency: '1'
          assignment_group: Quality_Distribution
      - name: alert-distribution
        type: call
        call: msteams.send-message
        with:
          channel_id: distribution-alerts
          text: 'COLD CHAIN ALERT: Shipment {{shipment_id}} recorded {{temperature_reading}}C. Destination: {{get-shipment.destination}}. ServiceNow: {{create-quality-incident.number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_SHIPMENT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: shipments
      path: /A_Shipment('{{shipment_id}}')
      inputParameters:
      - name: shipment_id
        in: path
      operations:
      - name: get-shipment
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Processes raw material procurement approvals by validating the SAP purchase requisition, checking budget availability in Oracle Cloud, and routing for approval via Microsoft Power Automate.

naftiko: '0.5'
info:
  label: Raw Material Procurement Approval
  description: Processes raw material procurement approvals by validating the SAP purchase requisition, checking budget availability in Oracle Cloud, and routing for approval via Microsoft Power Automate.
  tags:
  - procurement
  - supply-chain
  - sap
  - oracle-cloud
  - microsoft-power-automate
capability:
  exposes:
  - type: mcp
    namespace: procurement-approval
    port: 8080
    tools:
    - name: process-procurement-approval
      description: 'Orchestrate raw material procurement approval: validate SAP PR, check Oracle budget, and route approval.'
      inputParameters:
      - name: requisition_number
        in: body
        type: string
        description: The SAP purchase requisition number.
      steps:
      - name: get-requisition
        type: call
        call: sap.get-purchase-requisition
        with:
          requisition_number: '{{requisition_number}}'
      - name: check-budget
        type: call
        call: oracle.check-budget-availability
        with:
          cost_center: '{{get-requisition.cost_center}}'
          amount: '{{get-requisition.total_amount}}'
      - name: route-approval
        type: call
        call: power-automate.trigger-flow
        with:
          flow_id: procurement-approval
          requisition_number: '{{requisition_number}}'
          amount: '{{get-requisition.total_amount}}'
          budget_status: '{{check-budget.status}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PURCHASEREQ_PROCESS_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: requisitions
      path: /A_PurchaseRequisition('{{requisition_number}}')
      inputParameters:
      - name: requisition_number
        in: path
      operations:
      - name: get-purchase-requisition
        method: GET
  - type: http
    namespace: oracle
    baseUri: https://coca-cola.oraclecloud.com/fscmRestApi/resources/v1
    authentication:
      type: basic
      username: $secrets.oracle_user
      password: $secrets.oracle_password
    resources:
    - name: budgets
      path: /budgetBalances?q=CostCenter={{cost_center}}
      inputParameters:
      - name: cost_center
        in: query
      operations:
      - name: check-budget-availability
        method: GET
  - type: http
    namespace: power-automate
    baseUri: https://prod-cocacola.logic.azure.com
    authentication:
      type: apiKey
      header: x-flow-key
      value: $secrets.power_automate_key
    resources:
    - name: flows
      path: /workflows/{{flow_id}}/triggers/manual/paths/invoke
      inputParameters:
      - name: flow_id
        in: path
      operations:
      - name: trigger-flow
        method: POST

Reconciles goods movements by pulling movement data from SAP, validating against warehouse records, and creating discrepancy reports in ServiceNow.

naftiko: '0.5'
info:
  label: SAP Goods Movement Reconciliation
  description: Reconciles goods movements by pulling movement data from SAP, validating against warehouse records, and creating discrepancy reports in ServiceNow.
  tags:
  - supply-chain
  - sap
  - servicenow
  - manufacturing
capability:
  exposes:
  - type: mcp
    namespace: goods-movement
    port: 8080
    tools:
    - name: reconcile-goods-movements
      description: 'Reconcile SAP goods movements: pull movement data, validate against warehouse, and log discrepancies.'
      inputParameters:
      - name: plant_code
        in: body
        type: string
        description: The SAP plant code.
      - name: movement_date
        in: body
        type: string
        description: The date to reconcile in YYYY-MM-DD format.
      steps:
      - name: get-goods-movements
        type: call
        call: sap.get-goods-movements
        with:
          plant: '{{plant_code}}'
          date: '{{movement_date}}'
      - name: get-warehouse-records
        type: call
        call: sap.get-warehouse-inventory
        with:
          plant: '{{plant_code}}'
          date: '{{movement_date}}'
      - name: log-discrepancies
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Goods movement discrepancy: Plant {{plant_code}} on {{movement_date}}'
          description: 'Total movements: {{get-goods-movements.count}}. Warehouse records: {{get-warehouse-records.count}}.'
          category: inventory_reconciliation
          assignment_group: Warehouse_Ops_{{plant_code}}
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_DOCUMENT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: goods-movements
      path: /A_MaterialDocumentHeader?$filter=Plant eq '{{plant}}' and PostingDate eq datetime'{{date}}'
      inputParameters:
      - name: plant
        in: query
      - name: date
        in: query
      operations:
      - name: get-goods-movements
        method: GET
    - name: warehouse-inventory
      path: /WarehouseInventory(Plant='{{plant}}',Date='{{date}}')
      inputParameters:
      - name: plant
        in: path
      - name: date
        in: path
      operations:
      - name: get-warehouse-inventory
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST

Calculates trade promotion ROI by pulling promotion spend from SAP, incremental sales from Circana, and posting the ROI analysis to Salesforce and Microsoft Teams.

naftiko: '0.5'
info:
  label: Trade Promotion ROI Calculator
  description: Calculates trade promotion ROI by pulling promotion spend from SAP, incremental sales from Circana, and posting the ROI analysis to Salesforce and Microsoft Teams.
  tags:
  - marketing
  - finance
  - sap
  - salesforce
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: trade-promotion-roi
    port: 8080
    tools:
    - name: calculate-promotion-roi
      description: 'Calculate trade promotion ROI: pull SAP spend, Circana sales lift, and post analysis to Salesforce and Teams.'
      inputParameters:
      - name: promotion_id
        in: body
        type: string
        description: The Salesforce promotion record ID.
      - name: cost_center
        in: body
        type: string
        description: The SAP cost center for promotion spend.
      steps:
      - name: get-promotion-spend
        type: call
        call: sap.get-cost-center-actuals
        with:
          cost_center: '{{cost_center}}'
      - name: get-sales-lift
        type: call
        call: circana.get-promotion-lift
        with:
          promotion_id: '{{promotion_id}}'
      - name: update-sf-promotion
        type: call
        call: salesforce.update-promotion
        with:
          promotion_id: '{{promotion_id}}'
          total_spend: '{{get-promotion-spend.total_actual}}'
          incremental_volume: '{{get-sales-lift.incremental_volume}}'
          roi_percentage: '{{get-sales-lift.roi}}'
      - name: post-roi-report
        type: call
        call: msteams.send-message
        with:
          channel_id: trade-marketing
          text: 'Trade Promotion ROI: Promotion {{promotion_id}}. Spend: ${{get-promotion-spend.total_actual}}. Incremental volume: {{get-sales-lift.incremental_volume}}. ROI: {{get-sales-lift.roi}}%.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_COSTCENTER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: cost-centers
      path: /A_CostCenter('{{cost_center}}')/to_Actuals
      inputParameters:
      - name: cost_center
        in: path
      operations:
      - name: get-cost-center-actuals
        method: GET
  - type: http
    namespace: circana
    baseUri: https://api.circana.com/v2
    authentication:
      type: bearer
      token: $secrets.circana_token
    resources:
    - name: promotion-lift
      path: /promotions/{{promotion_id}}/lift
      inputParameters:
      - name: promotion_id
        in: path
      operations:
      - name: get-promotion-lift
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: promotions
      path: /sobjects/Promotion__c/{{promotion_id}}
      inputParameters:
      - name: promotion_id
        in: path
      operations:
      - name: update-promotion
        method: PATCH
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Audits all repositories in the Coca-Cola GitHub organization for missing branch protection rules and reports non-compliant repositories to the security team via Teams.

naftiko: '0.5'
info:
  label: GitHub Repository Security Policy Audit
  description: Audits all repositories in the Coca-Cola GitHub organization for missing branch protection rules and reports non-compliant repositories to the security team via Teams.
  tags:
  - security
  - github
  - devops
  - compliance
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: security-audit
    port: 8080
    tools:
    - name: audit-branch-protection
      description: List all repositories in the Coca-Cola GitHub organization and check each for branch protection rules on the default branch. Report non-compliant repos to the security Teams channel.
      steps:
      - name: list-repos
        type: call
        call: github.list-org-repos
        with:
          org: coca-cola
          type: private
      - name: post-audit-report
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_security_channel_id
          text: 'Branch Protection Audit: {{list-repos.total_count}} private repositories reviewed for compliance.'
  consumes:
  - type: http
    namespace: github
    baseUri: https://api.github.com
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: org-repos
      path: /orgs/{{org}}/repos
      inputParameters:
      - name: org
        in: path
      - name: type
        in: query
      operations:
      - name: list-org-repos
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Optimizes route-to-market by analyzing Salesforce retail account data, checking SAP warehouse inventory, and generating optimized delivery routes posted to Microsoft Teams.

naftiko: '0.5'
info:
  label: Route to Market Optimization
  description: Optimizes route-to-market by analyzing Salesforce retail account data, checking SAP warehouse inventory, and generating optimized delivery routes posted to Microsoft Teams.
  tags:
  - distribution
  - supply-chain
  - salesforce
  - sap
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: route-optimization
    port: 8080
    tools:
    - name: optimize-routes
      description: 'Optimize delivery routes: analyze Salesforce accounts, check SAP inventory, and post optimized routes.'
      inputParameters:
      - name: region_code
        in: body
        type: string
        description: The distribution region code.
      - name: delivery_date
        in: body
        type: string
        description: Target delivery date in YYYY-MM-DD format.
      steps:
      - name: get-retail-accounts
        type: call
        call: salesforce.get-region-accounts
        with:
          region: '{{region_code}}'
      - name: check-warehouse-stock
        type: call
        call: sap.get-regional-stock
        with:
          region: '{{region_code}}'
      - name: post-optimized-routes
        type: call
        call: msteams.send-message
        with:
          channel_id: distribution-{{region_code}}
          text: 'Route optimization for {{region_code}} on {{delivery_date}}: Active accounts: {{get-retail-accounts.count}}. Warehouse stock: {{check-warehouse-stock.total_cases}} cases. Routes generated and ready for dispatch.'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: accounts
      path: /query?q=SELECT+Id,Name+FROM+Account+WHERE+Region__c='{{region}}'
      inputParameters:
      - name: region
        in: query
      operations:
      - name: get-region-accounts
        method: GET
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: regional-stock
      path: /RegionalInventory('{{region}}')
      inputParameters:
      - name: region
        in: path
      operations:
      - name: get-regional-stock
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

When Dynatrace detects performance degradation, retrieves problem details, creates a ServiceNow incident, and notifies the SRE team via Microsoft Teams.

naftiko: '0.5'
info:
  label: Dynatrace Performance Degradation Alert
  description: When Dynatrace detects performance degradation, retrieves problem details, creates a ServiceNow incident, and notifies the SRE team via Microsoft Teams.
  tags:
  - it-operations
  - dynatrace
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: performance-ops
    port: 8080
    tools:
    - name: handle-performance-degradation
      description: 'Handle Dynatrace performance alert: get problem details, create ServiceNow incident, and notify SRE team.'
      inputParameters:
      - name: problem_id
        in: body
        type: string
        description: The Dynatrace problem ID.
      steps:
      - name: get-problem-details
        type: call
        call: dynatrace.get-problem
        with:
          problem_id: '{{problem_id}}'
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Performance degradation: {{get-problem-details.title}}'
          description: 'Impact: {{get-problem-details.impact_level}}. Root cause: {{get-problem-details.root_cause}}. Affected services: {{get-problem-details.affected_entities}}.'
          urgency: '2'
          assignment_group: SRE_Team
      - name: notify-sre
        type: call
        call: msteams.send-message
        with:
          channel_id: sre-alerts
          text: 'Performance Alert: {{get-problem-details.title}}. Impact: {{get-problem-details.impact_level}}. ServiceNow: {{create-incident.number}}.'
  consumes:
  - type: http
    namespace: dynatrace
    baseUri: https://cocacola.live.dynatrace.com/api/v2
    authentication:
      type: bearer
      token: $secrets.dynatrace_token
    resources:
    - name: problems
      path: /problems/{{problem_id}}
      inputParameters:
      - name: problem_id
        in: path
      operations:
      - name: get-problem
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Performs distributor credit checks by validating credit limits in SAP, checking payment history in Salesforce, and releasing or blocking the sales order.

naftiko: '0.5'
info:
  label: Distributor Credit Check and Order Release
  description: Performs distributor credit checks by validating credit limits in SAP, checking payment history in Salesforce, and releasing or blocking the sales order.
  tags:
  - distribution
  - finance
  - sap
  - salesforce
capability:
  exposes:
  - type: mcp
    namespace: credit-management
    port: 8080
    tools:
    - name: check-credit-and-release
      description: Check distributor credit in SAP, verify Salesforce payment history, and release or block sales order.
      inputParameters:
      - name: sales_order_number
        in: body
        type: string
        description: The SAP sales order number.
      - name: account_id
        in: body
        type: string
        description: The Salesforce distributor account ID.
      steps:
      - name: get-credit-status
        type: call
        call: sap.get-credit-status
        with:
          sales_order: '{{sales_order_number}}'
      - name: get-payment-history
        type: call
        call: salesforce.get-payment-history
        with:
          account_id: '{{account_id}}'
      - name: release-order
        type: call
        call: sap.release-credit-block
        with:
          sales_order: '{{sales_order_number}}'
          credit_status: '{{get-credit-status.credit_status}}'
          payment_score: '{{get-payment-history.payment_score}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_SALES_ORDER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: credit-status
      path: /A_SalesOrder('{{sales_order}}')/to_CreditStatus
      inputParameters:
      - name: sales_order
        in: path
      operations:
      - name: get-credit-status
        method: GET
    - name: credit-release
      path: /A_SalesOrder('{{sales_order}}')/to_CreditRelease
      inputParameters:
      - name: sales_order
        in: path
      operations:
      - name: release-credit-block
        method: POST
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: payment-history
      path: /sobjects/Account/{{account_id}}/Payment_History__r
      inputParameters:
      - name: account_id
        in: path
      operations:
      - name: get-payment-history
        method: GET

Retrieves the current stock level for a given material number from SAP S/4HANA, returning plant, storage location, and available quantity.

naftiko: '0.5'
info:
  label: SAP Material Stock Level Check
  description: Retrieves the current stock level for a given material number from SAP S/4HANA, returning plant, storage location, and available quantity.
  tags:
  - supply-chain
  - sap
  - inventory
capability:
  exposes:
  - type: mcp
    namespace: inventory
    port: 8080
    tools:
    - name: get-material-stock
      description: Look up current stock levels for a material in SAP S/4HANA. Returns plant, storage location, unrestricted stock, and unit of measure.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number, e.g. 000000000050001234.
      call: sap.get-material-stock
      with:
        material_number: '{{material_number}}'
      outputParameters:
      - name: plant
        type: string
        mapping: $.d.Plant
      - name: storage_location
        type: string
        mapping: $.d.StorageLocation
      - name: available_stock
        type: string
        mapping: $.d.MatlWrhsStkQtyInMatlBaseUnit
      - name: unit
        type: string
        mapping: $.d.MaterialBaseUnit
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: material-stock
      path: /A_MatlStkInAcctMod(Material='{{material_number}}')
      inputParameters:
      - name: material_number
        in: path
      operations:
      - name: get-material-stock
        method: GET

When a critical ServiceNow incident is raised, creates a Datadog event marker, pages the on-call engineer, and posts an alert to the IT-incidents Microsoft Teams channel.

naftiko: '0.5'
info:
  label: IT Incident Response Orchestrator
  description: When a critical ServiceNow incident is raised, creates a Datadog event marker, pages the on-call engineer, and posts an alert to the IT-incidents Microsoft Teams channel.
  tags:
  - itsm
  - incident-response
  - servicenow
  - datadog
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: it-ops
    port: 8080
    tools:
    - name: handle-critical-incident
      description: Given a ServiceNow incident number, retrieve incident details, create a Datadog event marker for correlation, and post an alert to the IT-incidents Teams channel. Use for critical P1/P2 incident bridges.
      inputParameters:
      - name: incident_number
        in: body
        type: string
        description: The ServiceNow incident number, e.g. INC0012345.
      steps:
      - name: get-incident
        type: call
        call: servicenow.get-incident
        with:
          incident_number: '{{incident_number}}'
      - name: create-datadog-event
        type: call
        call: datadog.create-event
        with:
          title: 'ServiceNow Incident: {{incident_number}}'
          text: '{{get-incident.short_description}} — Priority: {{get-incident.priority}}'
          alert_type: error
      - name: post-teams-alert
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_it_channel_id
          text: 'CRITICAL INCIDENT {{incident_number}}: {{get-incident.short_description}} | Assigned: {{get-incident.assigned_to}} | Datadog event: {{create-datadog-event.event_id}}'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      inputParameters:
      - name: incident_number
        in: query
      operations:
      - name: get-incident
        method: GET
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Reconciles digital marketing spend by pulling campaign costs from Google Analytics, comparing with SAP cost center actuals, and posting a variance report to Microsoft Teams.

naftiko: '0.5'
info:
  label: Digital Marketing Spend Reconciliation
  description: Reconciles digital marketing spend by pulling campaign costs from Google Analytics, comparing with SAP cost center actuals, and posting a variance report to Microsoft Teams.
  tags:
  - marketing
  - finance
  - google-analytics
  - sap
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: marketing-finance
    port: 8080
    tools:
    - name: reconcile-marketing-spend
      description: Reconcile digital marketing spend across Google Analytics and SAP, then post variance report to Teams.
      inputParameters:
      - name: cost_center
        in: body
        type: string
        description: The SAP cost center for marketing.
      - name: campaign_id
        in: body
        type: string
        description: The Google Analytics campaign ID.
      - name: period
        in: body
        type: string
        description: The fiscal period, e.g. 2026-03.
      steps:
      - name: get-ga-spend
        type: call
        call: ga.get-campaign-cost
        with:
          campaign_id: '{{campaign_id}}'
          period: '{{period}}'
      - name: get-sap-actuals
        type: call
        call: sap.get-cost-center-actuals
        with:
          cost_center: '{{cost_center}}'
          period: '{{period}}'
      - name: post-variance-report
        type: call
        call: msteams.send-message
        with:
          channel_id: marketing-finance
          text: 'Marketing Spend Reconciliation for {{period}}: GA Campaign Spend: ${{get-ga-spend.total_cost}}. SAP Cost Center Actuals: ${{get-sap-actuals.total_actual}}. Variance requires review.'
  consumes:
  - type: http
    namespace: ga
    baseUri: https://analyticsreporting.googleapis.com/v4
    authentication:
      type: bearer
      token: $secrets.google_analytics_token
    resources:
    - name: campaign-cost
      path: /reports:batchGet
      operations:
      - name: get-campaign-cost
        method: POST
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_COSTCENTER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: cost-centers
      path: /A_CostCenter('{{cost_center}}')/to_Actuals?$filter=Period eq '{{period}}'
      inputParameters:
      - name: cost_center
        in: path
      - name: period
        in: query
      operations:
      - name: get-cost-center-actuals
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Creates a ServiceNow change request for a planned infrastructure change, routes it for manager approval, and notifies the requester via Teams when approved or rejected.

naftiko: '0.5'
info:
  label: ServiceNow Change Request Approval
  description: Creates a ServiceNow change request for a planned infrastructure change, routes it for manager approval, and notifies the requester via Teams when approved or rejected.
  tags:
  - itsm
  - change-management
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: change-mgmt
    port: 8080
    tools:
    - name: create-change-request
      description: Given a change description, risk level, and planned start/end times, create a ServiceNow change request and notify the requester of submission via Teams.
      inputParameters:
      - name: description
        in: body
        type: string
        description: A description of the planned infrastructure change.
      - name: risk
        in: body
        type: string
        description: 'Risk level: low, medium, or high.'
      - name: planned_start
        in: body
        type: string
        description: Planned change start time in ISO 8601 format.
      - name: requester_upn
        in: body
        type: string
        description: UPN (email) of the person requesting the change.
      steps:
      - name: create-cr
        type: call
        call: servicenow.create-change
        with:
          description: '{{description}}'
          risk: '{{risk}}'
          start_date: '{{planned_start}}'
      - name: notify-requester
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{requester_upn}}'
          text: Your change request {{create-cr.number}} has been submitted and is pending approval.
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: change-requests
      path: /table/change_request
      operations:
      - name: create-change
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: mail
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves the status of a running Teradata query by session ID, returning query state, elapsed time, and CPU consumption.

naftiko: '0.5'
info:
  label: Teradata Warehouse Query Status
  description: Retrieves the status of a running Teradata query by session ID, returning query state, elapsed time, and CPU consumption.
  tags:
  - analytics
  - teradata
  - data-warehouse
capability:
  exposes:
  - type: mcp
    namespace: data-warehouse
    port: 8080
    tools:
    - name: get-query-status
      description: Check the status of a Teradata query by session ID. Returns query state, elapsed time, and CPU seconds.
      inputParameters:
      - name: session_id
        in: body
        type: string
        description: The Teradata session ID.
      call: teradata.get-query-status
      with:
        session_id: '{{session_id}}'
      outputParameters:
      - name: query_state
        type: string
        mapping: $.queryState
      - name: elapsed_time
        type: string
        mapping: $.elapsedTime
      - name: cpu_seconds
        type: string
        mapping: $.cpuSeconds
  consumes:
  - type: http
    namespace: teradata
    baseUri: https://coca-cola-td.teradata.com/api/v1
    authentication:
      type: bearer
      token: $secrets.teradata_token
    resources:
    - name: queries
      path: /queries/{{session_id}}/status
      inputParameters:
      - name: session_id
        in: path
      operations:
      - name: get-query-status
        method: GET

Retrieves a Zendesk support ticket by ID, returning status, priority, requester, and subject for customer service tracking.

naftiko: '0.5'
info:
  label: Zendesk Ticket Status Lookup
  description: Retrieves a Zendesk support ticket by ID, returning status, priority, requester, and subject for customer service tracking.
  tags:
  - customer-service
  - zendesk
  - support
capability:
  exposes:
  - type: mcp
    namespace: support
    port: 8080
    tools:
    - name: get-ticket
      description: Look up a Zendesk support ticket by ID. Returns status, priority, requester name, and subject.
      inputParameters:
      - name: ticket_id
        in: body
        type: string
        description: The Zendesk ticket ID.
      call: zendesk.get-ticket
      with:
        ticket_id: '{{ticket_id}}'
      outputParameters:
      - name: status
        type: string
        mapping: $.ticket.status
      - name: priority
        type: string
        mapping: $.ticket.priority
      - name: requester
        type: string
        mapping: $.ticket.requester.name
      - name: subject
        type: string
        mapping: $.ticket.subject
  consumes:
  - type: http
    namespace: zendesk
    baseUri: https://cocacola.zendesk.com/api/v2
    authentication:
      type: bearer
      token: $secrets.zendesk_token
    resources:
    - name: tickets
      path: /tickets/{{ticket_id}}
      inputParameters:
      - name: ticket_id
        in: path
      operations:
      - name: get-ticket
        method: GET

When Datadog detects an infrastructure anomaly above a threshold, creates a ServiceNow incident and notifies the SRE team in Teams with metric context.

naftiko: '0.5'
info:
  label: Datadog Infrastructure Anomaly Responder
  description: When Datadog detects an infrastructure anomaly above a threshold, creates a ServiceNow incident and notifies the SRE team in Teams with metric context.
  tags:
  - observability
  - datadog
  - servicenow
  - microsoft-teams
  - monitoring
capability:
  exposes:
  - type: mcp
    namespace: observability-ops
    port: 8080
    tools:
    - name: handle-infra-anomaly
      description: Given a Datadog monitor ID and alert status, fetch monitor details, create a ServiceNow incident, and post context-rich alert to the SRE Teams channel. Use for infrastructure anomaly response automation.
      inputParameters:
      - name: monitor_id
        in: body
        type: string
        description: The Datadog monitor ID that triggered the alert.
      - name: alert_status
        in: body
        type: string
        description: 'The alert status: Alert, Warn, or No Data.'
      steps:
      - name: get-monitor
        type: call
        call: datadog.get-monitor
        with:
          monitor_id: '{{monitor_id}}'
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Datadog anomaly: {{get-monitor.name}}'
          description: 'Monitor ID: {{monitor_id}} | Status: {{alert_status}} | Query: {{get-monitor.query}}'
          urgency: '1'
      - name: post-alert
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_sre_channel_id
          text: 'Infra Anomaly: {{get-monitor.name}} | Status: {{alert_status}} | Incident: {{create-incident.number}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: monitors
      path: /monitor/{{monitor_id}}
      inputParameters:
      - name: monitor_id
        in: path
      operations:
      - name: get-monitor
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Checks workforce training compliance by pulling training records from Workday, verifying certifications against requirements, and creating non-compliance tasks in ServiceNow.

naftiko: '0.5'
info:
  label: Workforce Training Compliance Check
  description: Checks workforce training compliance by pulling training records from Workday, verifying certifications against requirements, and creating non-compliance tasks in ServiceNow.
  tags:
  - hr
  - manufacturing
  - workday
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: training-compliance
    port: 8080
    tools:
    - name: check-training-compliance
      description: 'Check training compliance: pull Workday records, verify certifications, and create ServiceNow tasks for gaps.'
      inputParameters:
      - name: department
        in: body
        type: string
        description: The department to check.
      - name: plant_code
        in: body
        type: string
        description: The plant code.
      steps:
      - name: get-training-records
        type: call
        call: workday.get-training-records
        with:
          department: '{{department}}'
          location: '{{plant_code}}'
      - name: create-compliance-tasks
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Training compliance gap: {{department}} at plant {{plant_code}}'
          description: 'Overdue trainings: {{get-training-records.overdue_count}}. Expiring certifications: {{get-training-records.expiring_count}}.'
          category: training_compliance
          assignment_group: HR_Training
      - name: notify-hr
        type: call
        call: msteams.send-message
        with:
          channel_id: hr-compliance
          text: 'Training Compliance Report for {{department}} at plant {{plant_code}}: Total employees: {{get-training-records.total_employees}}. Compliant: {{get-training-records.compliant_count}}. Overdue: {{get-training-records.overdue_count}}. ServiceNow task: {{create-compliance-tasks.number}}.'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: training
      path: /coca-cola/training/records?department={{department}}&location={{location}}
      inputParameters:
      - name: department
        in: query
      - name: location
        in: query
      operations:
      - name: get-training-records
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/sc_task
      operations:
      - name: create-task
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Manages packaging changes by updating the SAP material master, creating a change request in ServiceNow, and notifying brand management and manufacturing via Microsoft Teams.

naftiko: '0.5'
info:
  label: Brand Packaging Change Management
  description: Manages packaging changes by updating the SAP material master, creating a change request in ServiceNow, and notifying brand management and manufacturing via Microsoft Teams.
  tags:
  - brand-management
  - manufacturing
  - sap
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: packaging-change
    port: 8080
    tools:
    - name: manage-packaging-change
      description: 'Manage packaging change: update SAP material, create ServiceNow change request, and notify teams.'
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number.
      - name: change_description
        in: body
        type: string
        description: Description of the packaging change.
      - name: effective_date
        in: body
        type: string
        description: Effective date in YYYY-MM-DD format.
      steps:
      - name: get-current-material
        type: call
        call: sap.get-material-master
        with:
          material_number: '{{material_number}}'
      - name: create-change-request
        type: call
        call: servicenow.create-change-request
        with:
          short_description: 'Packaging change: Material {{material_number}}'
          description: '{{change_description}}. Current packaging: {{get-current-material.packaging_type}}. Effective: {{effective_date}}.'
          category: packaging_change
          assignment_group: Brand_Packaging
      - name: notify-stakeholders
        type: call
        call: msteams.send-message
        with:
          channel_id: brand-packaging
          text: 'Packaging Change: Material {{material_number}} ({{get-current-material.description}}). Change: {{change_description}}. Effective: {{effective_date}}. Change request: {{create-change-request.number}}.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PRODUCT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: materials
      path: /A_Product('{{material_number}}')
      inputParameters:
      - name: material_number
        in: path
      operations:
      - name: get-material-master
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: change-requests
      path: /table/change_request
      operations:
      - name: create-change-request
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Orchestrates new supplier onboarding by creating the vendor master in SAP, setting up a contract workspace in SharePoint, and notifying procurement via Microsoft Teams.

naftiko: '0.5'
info:
  label: Supplier Onboarding Orchestrator
  description: Orchestrates new supplier onboarding by creating the vendor master in SAP, setting up a contract workspace in SharePoint, and notifying procurement via Microsoft Teams.
  tags:
  - procurement
  - sap
  - sharepoint
  - microsoft-teams
  - supply-chain
capability:
  exposes:
  - type: mcp
    namespace: procurement-onboarding
    port: 8080
    tools:
    - name: onboard-supplier
      description: 'Orchestrate supplier onboarding: create SAP vendor master, set up SharePoint workspace, and notify procurement team.'
      inputParameters:
      - name: vendor_name
        in: body
        type: string
        description: The supplier company name.
      - name: vendor_country
        in: body
        type: string
        description: The supplier country code.
      - name: category
        in: body
        type: string
        description: The procurement category, e.g. raw-materials, packaging.
      steps:
      - name: create-vendor
        type: call
        call: sap.create-vendor
        with:
          name: '{{vendor_name}}'
          country: '{{vendor_country}}'
          purchasing_group: '{{category}}'
      - name: create-contract-workspace
        type: call
        call: sharepoint.create-folder
        with:
          site_id: procurement
          folder_path: Vendors/{{vendor_name}}
      - name: notify-procurement
        type: call
        call: msteams.send-message
        with:
          channel_id: procurement-ops
          text: 'New supplier onboarded: {{vendor_name}} ({{vendor_country}}). SAP Vendor ID: {{create-vendor.vendor_id}}. Category: {{category}}. Contract workspace created in SharePoint.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_BUSINESS_PARTNER
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: vendors
      path: /A_BusinessPartner
      operations:
      - name: create-vendor
        method: POST
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: folders
      path: /sites/{{site_id}}/drive/root/children
      inputParameters:
      - name: site_id
        in: path
      operations:
      - name: create-folder
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Queries Workday for pending time-off requests older than 48 hours and sends a reminder to the responsible managers via Microsoft Teams.

naftiko: '0.5'
info:
  label: Workday Time-Off Request Approval Reminder
  description: Queries Workday for pending time-off requests older than 48 hours and sends a reminder to the responsible managers via Microsoft Teams.
  tags:
  - hr
  - workday
  - microsoft-teams
  - approval
capability:
  exposes:
  - type: mcp
    namespace: hr-leave
    port: 8080
    tools:
    - name: remind-pending-timeoff-approvals
      description: Fetch all Workday time-off requests that have been pending approval for more than 48 hours and send a reminder to each manager via Teams.
      steps:
      - name: get-pending-requests
        type: call
        call: workday.list-pending-timeoff
        with:
          status: Awaiting_Approval
      - name: notify-managers
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_hr_channel_id
          text: 'Reminder: {{get-pending-requests.total_count}} time-off requests are awaiting approval in Workday for more than 48 hours.'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: timeoff-requests
      path: /coca-cola/timeOffRequests
      inputParameters:
      - name: status
        in: query
      operations:
      - name: list-pending-timeoff
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves application health summary from New Relic, including response time, throughput, and error rate for a given application.

naftiko: '0.5'
info:
  label: New Relic Application Health
  description: Retrieves application health summary from New Relic, including response time, throughput, and error rate for a given application.
  tags:
  - it-operations
  - new-relic
  - monitoring
capability:
  exposes:
  - type: mcp
    namespace: apm
    port: 8080
    tools:
    - name: get-app-health
      description: Get the health summary of a New Relic application. Returns response time, throughput, and error rate.
      inputParameters:
      - name: app_id
        in: body
        type: string
        description: The New Relic application ID.
      call: newrelic.get-app-summary
      with:
        app_id: '{{app_id}}'
      outputParameters:
      - name: response_time
        type: string
        mapping: $.application_summary.response_time
      - name: throughput
        type: string
        mapping: $.application_summary.throughput
      - name: error_rate
        type: string
        mapping: $.application_summary.error_rate
  consumes:
  - type: http
    namespace: newrelic
    baseUri: https://api.newrelic.com/v2
    authentication:
      type: apiKey
      header: X-Api-Key
      value: $secrets.newrelic_api_key
    resources:
    - name: applications
      path: /applications/{{app_id}}.json
      inputParameters:
      - name: app_id
        in: path
      operations:
      - name: get-app-summary
        method: GET

Audits retail shelf compliance by pulling store audit data from Salesforce, comparing against planogram standards, and posting a compliance report to Microsoft Teams.

naftiko: '0.5'
info:
  label: Retail Shelf Compliance Audit
  description: Audits retail shelf compliance by pulling store audit data from Salesforce, comparing against planogram standards, and posting a compliance report to Microsoft Teams.
  tags:
  - distribution
  - brand-management
  - salesforce
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: retail-compliance
    port: 8080
    tools:
    - name: audit-shelf-compliance
      description: 'Audit retail shelf compliance: pull Salesforce audit data, compare with standards, and post report to Teams.'
      inputParameters:
      - name: store_account_id
        in: body
        type: string
        description: The Salesforce store account ID.
      - name: audit_date
        in: body
        type: string
        description: The audit date in YYYY-MM-DD format.
      steps:
      - name: get-audit-record
        type: call
        call: salesforce.get-audit-record
        with:
          account_id: '{{store_account_id}}'
          audit_date: '{{audit_date}}'
      - name: get-planogram
        type: call
        call: salesforce.get-planogram
        with:
          store_type: '{{get-audit-record.store_type}}'
      - name: post-compliance-report
        type: call
        call: msteams.send-message
        with:
          channel_id: retail-operations
          text: 'Shelf Compliance Audit: Store {{get-audit-record.store_name}} on {{audit_date}}. Compliance score: {{get-audit-record.compliance_score}}%. Planogram adherence: {{get-audit-record.planogram_match}}%. Action required: {{get-audit-record.action_items}}.'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: audits
      path: /sobjects/Store_Audit__c?q=AccountId='{{account_id}}' AND AuditDate='{{audit_date}}'
      inputParameters:
      - name: account_id
        in: query
      - name: audit_date
        in: query
      operations:
      - name: get-audit-record
        method: GET
    - name: planograms
      path: /sobjects/Planogram__c?q=StoreType='{{store_type}}'
      inputParameters:
      - name: store_type
        in: query
      operations:
      - name: get-planogram
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Validates cross-border trade compliance by checking SAP export documentation, verifying customs classification, and logging compliance status in ServiceNow.

naftiko: '0.5'
info:
  label: Cross-Border Trade Compliance Check
  description: Validates cross-border trade compliance by checking SAP export documentation, verifying customs classification, and logging compliance status in ServiceNow.
  tags:
  - distribution
  - supply-chain
  - sap
  - servicenow
capability:
  exposes:
  - type: mcp
    namespace: trade-compliance
    port: 8080
    tools:
    - name: check-trade-compliance
      description: 'Validate cross-border trade compliance: check SAP export docs, verify customs, and log in ServiceNow.'
      inputParameters:
      - name: delivery_number
        in: body
        type: string
        description: The SAP delivery document number.
      - name: destination_country
        in: body
        type: string
        description: The destination country code.
      steps:
      - name: get-export-docs
        type: call
        call: sap.get-export-documentation
        with:
          delivery_number: '{{delivery_number}}'
      - name: verify-customs
        type: call
        call: sap.get-customs-classification
        with:
          material: '{{get-export-docs.material_number}}'
          country: '{{destination_country}}'
      - name: log-compliance
        type: call
        call: servicenow.create-task
        with:
          short_description: 'Trade compliance: Delivery {{delivery_number}} to {{destination_country}}'
          description: 'Export docs status: {{get-export-docs.status}}. Customs classification: {{verify-customs.hs_code}}. Duty rate: {{verify-customs.duty_rate}}%.'
          category: trade_compliance
          assignment_group: Trade_Compliance
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_OUTBOUND_DELIVERY_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: export-docs
      path: /A_OutbDeliveryHeader('{{delivery_number}}')/to_ExportDocuments
      inputParameters:
      - name: delivery_number
        in: path
      operations:
      - name: get-export-documentation
        method: GET
    - name: customs
      path: /CustomsClassification(Material='{{material}}',Country='{{country}}')
      inputParameters:
      - name: material
        in: path
      - name: country
        in: path
      operations:
      - name: get-customs-classification
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: tasks
      path: /table/sc_task
      operations:
      - name: create-task
        method: POST

Tracks GitHub release deployments by checking release status, verifying Datadog health metrics post-deploy, and updating the ServiceNow change request.

naftiko: '0.5'
info:
  label: GitHub Release Deployment Tracker
  description: Tracks GitHub release deployments by checking release status, verifying Datadog health metrics post-deploy, and updating the ServiceNow change request.
  tags:
  - devops
  - github
  - datadog
  - servicenow
capability:
  exposes:
  - type: mcp
    namespace: deployment
    port: 8080
    tools:
    - name: track-release-deployment
      description: 'Track release deployment: check GitHub release, verify Datadog metrics, and update ServiceNow change request.'
      inputParameters:
      - name: repo
        in: body
        type: string
        description: The GitHub repository name.
      - name: release_tag
        in: body
        type: string
        description: The release tag version.
      - name: change_request_id
        in: body
        type: string
        description: The ServiceNow change request sys_id.
      steps:
      - name: get-release
        type: call
        call: github.get-release
        with:
          repo: '{{repo}}'
          tag: '{{release_tag}}'
      - name: check-post-deploy-health
        type: call
        call: datadog.get-service-metrics
        with:
          service_name: '{{repo}}'
      - name: update-change-request
        type: call
        call: servicenow.update-change-request
        with:
          sys_id: '{{change_request_id}}'
          state: review
          work_notes: 'Release {{release_tag}} deployed. Error rate: {{check-post-deploy-health.error_rate}}. P99 latency: {{check-post-deploy-health.p99_latency}}ms.'
  consumes:
  - type: http
    namespace: github
    baseUri: https://api.github.com
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: releases
      path: /repos/coca-cola/{{repo}}/releases/tags/{{tag}}
      inputParameters:
      - name: repo
        in: path
      - name: tag
        in: path
      operations:
      - name: get-release
        method: GET
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apiKey
      header: DD-API-KEY
      value: $secrets.datadog_api_key
    resources:
    - name: service-metrics
      path: /metrics/query?query=service:{{service_name}}
      inputParameters:
      - name: service_name
        in: query
      operations:
      - name: get-service-metrics
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: change-requests
      path: /table/change_request/{{sys_id}}
      inputParameters:
      - name: sys_id
        in: path
      operations:
      - name: update-change-request
        method: PATCH

Processes fountain equipment service requests by looking up the customer in Salesforce, creating a field service ticket in ServiceNow, and notifying the service technician via Microsoft Teams.

naftiko: '0.5'
info:
  label: Fountain Equipment Service Request
  description: Processes fountain equipment service requests by looking up the customer in Salesforce, creating a field service ticket in ServiceNow, and notifying the service technician via Microsoft Teams.
  tags:
  - distribution
  - customer-service
  - salesforce
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: field-service
    port: 8080
    tools:
    - name: create-fountain-service-request
      description: 'Process fountain service request: look up Salesforce customer, create ServiceNow ticket, notify technician.'
      inputParameters:
      - name: account_id
        in: body
        type: string
        description: The Salesforce customer account ID.
      - name: equipment_serial
        in: body
        type: string
        description: The fountain equipment serial number.
      - name: issue_description
        in: body
        type: string
        description: Description of the service issue.
      steps:
      - name: get-customer
        type: call
        call: salesforce.get-account
        with:
          account_id: '{{account_id}}'
      - name: create-service-ticket
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Fountain service: {{equipment_serial}} at {{get-customer.name}}'
          description: '{{issue_description}}'
          category: fountain_equipment
          assignment_group: Fountain_Service
      - name: notify-technician
        type: call
        call: msteams.send-message
        with:
          channel_id: fountain-service
          text: 'New fountain service request: {{get-customer.name}}. Equipment: {{equipment_serial}}. Issue: {{issue_description}}. Ticket: {{create-service-ticket.number}}.'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: accounts
      path: /sobjects/Account/{{account_id}}
      inputParameters:
      - name: account_id
        in: path
      operations:
      - name: get-account
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Monitors Azure Databricks ETL pipeline runs, checks for failures in Datadog, and creates a ServiceNow incident if errors are detected.

naftiko: '0.5'
info:
  label: Azure Databricks ETL Pipeline Monitor
  description: Monitors Azure Databricks ETL pipeline runs, checks for failures in Datadog, and creates a ServiceNow incident if errors are detected.
  tags:
  - analytics
  - azure-databricks
  - datadog
  - servicenow
capability:
  exposes:
  - type: mcp
    namespace: data-ops
    port: 8080
    tools:
    - name: monitor-etl-pipeline
      description: 'Monitor Databricks ETL pipeline: check run status, verify Datadog metrics, and create ServiceNow incident on failure.'
      inputParameters:
      - name: run_id
        in: body
        type: string
        description: The Databricks job run ID.
      steps:
      - name: get-run-status
        type: call
        call: databricks.get-run
        with:
          run_id: '{{run_id}}'
      - name: check-datadog-metrics
        type: call
        call: datadog.get-pipeline-metrics
        with:
          pipeline_name: '{{get-run-status.job_name}}'
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'ETL pipeline alert: {{get-run-status.job_name}} run {{run_id}}'
          description: 'Run status: {{get-run-status.state}}. Error rate: {{check-datadog-metrics.error_rate}}.'
          category: data_pipeline
          assignment_group: Data_Engineering
  consumes:
  - type: http
    namespace: databricks
    baseUri: https://adb-cocacola.azuredatabricks.net/api/2.1
    authentication:
      type: bearer
      token: $secrets.databricks_token
    resources:
    - name: runs
      path: /jobs/runs/get?run_id={{run_id}}
      inputParameters:
      - name: run_id
        in: query
      operations:
      - name: get-run
        method: GET
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apiKey
      header: DD-API-KEY
      value: $secrets.datadog_api_key
    resources:
    - name: pipeline-metrics
      path: /metrics/query?query=pipeline:{{pipeline_name}}
      inputParameters:
      - name: pipeline_name
        in: query
      operations:
      - name: get-pipeline-metrics
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST

When an employee changes roles in Workday, updates ServiceNow access groups, modifies SharePoint permissions, and notifies the employee and manager via Microsoft Teams.

naftiko: '0.5'
info:
  label: Employee Role Change Provisioning
  description: When an employee changes roles in Workday, updates ServiceNow access groups, modifies SharePoint permissions, and notifies the employee and manager via Microsoft Teams.
  tags:
  - hr
  - workday
  - servicenow
  - sharepoint
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: hr-provisioning
    port: 8080
    tools:
    - name: process-role-change
      description: 'Orchestrate employee role change: update ServiceNow access, modify SharePoint permissions, and notify via Teams.'
      inputParameters:
      - name: worker_id
        in: body
        type: string
        description: The Workday worker ID.
      - name: new_role
        in: body
        type: string
        description: The new role title.
      steps:
      - name: get-worker
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{worker_id}}'
      - name: update-access-groups
        type: call
        call: servicenow.update-user-groups
        with:
          user_email: '{{get-worker.work_email}}'
          new_role: '{{new_role}}'
      - name: update-sharepoint-access
        type: call
        call: sharepoint.update-permissions
        with:
          user_email: '{{get-worker.work_email}}'
          site_group: '{{new_role}}-team'
      - name: notify-employee
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{get-worker.work_email}}'
          text: Hi {{get-worker.first_name}}, your role has been updated to {{new_role}}. Your system access has been adjusted accordingly.
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /coca-cola/workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: user-groups
      path: /table/sys_user_grmember
      operations:
      - name: update-user-groups
        method: POST
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: permissions
      path: /sites/root/permissions
      operations:
      - name: update-permissions
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: chats
      path: /users/{{recipient_upn}}/chats
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Orchestrates a marketing campaign launch by creating the campaign in Salesforce, setting up tracking in Google Analytics, and posting the announcement to Microsoft Teams.

naftiko: '0.5'
info:
  label: Brand Marketing Campaign Launch
  description: Orchestrates a marketing campaign launch by creating the campaign in Salesforce, setting up tracking in Google Analytics, and posting the announcement to Microsoft Teams.
  tags:
  - marketing
  - brand-management
  - salesforce
  - google-analytics
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: marketing
    port: 8080
    tools:
    - name: launch-brand-campaign
      description: Orchestrate a brand campaign launch across Salesforce, Google Analytics, and Microsoft Teams.
      inputParameters:
      - name: campaign_name
        in: body
        type: string
        description: The name of the marketing campaign.
      - name: brand
        in: body
        type: string
        description: The Coca-Cola brand, e.g. Coca-Cola Classic, Sprite, Fanta.
      - name: start_date
        in: body
        type: string
        description: Campaign start date in YYYY-MM-DD format.
      - name: budget
        in: body
        type: string
        description: Campaign budget in USD.
      steps:
      - name: create-sf-campaign
        type: call
        call: salesforce.create-campaign
        with:
          name: '{{campaign_name}}'
          brand: '{{brand}}'
          start_date: '{{start_date}}'
          budgeted_cost: '{{budget}}'
      - name: create-ga-property
        type: call
        call: ga.create-custom-dimension
        with:
          campaign_id: '{{create-sf-campaign.id}}'
          campaign_name: '{{campaign_name}}'
      - name: announce-launch
        type: call
        call: msteams.send-message
        with:
          channel_id: brand-marketing
          text: 'New campaign launched: {{campaign_name}} for {{brand}}. Salesforce ID: {{create-sf-campaign.id}}. Budget: ${{budget}}. Start date: {{start_date}}.'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: campaigns
      path: /sobjects/Campaign
      operations:
      - name: create-campaign
        method: POST
  - type: http
    namespace: ga
    baseUri: https://analyticsadmin.googleapis.com/v1beta
    authentication:
      type: bearer
      token: $secrets.google_analytics_token
    resources:
    - name: custom-dimensions
      path: /properties/cocacola/customDimensions
      operations:
      - name: create-custom-dimension
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Pulls actual vs. planned spending by cost center from SAP S/4HANA and posts a variance summary to the Finance Microsoft Teams channel for monthly close review.

naftiko: '0.5'
info:
  label: SAP Cost Center Budget Variance Report
  description: Pulls actual vs. planned spending by cost center from SAP S/4HANA and posts a variance summary to the Finance Microsoft Teams channel for monthly close review.
  tags:
  - finance
  - sap
  - budgeting
  - reporting
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: finance-reporting
    port: 8080
    tools:
    - name: digest-budget-variance
      description: Retrieve actual vs. planned cost center spending from SAP S/4HANA for the current fiscal period and post a variance digest to the Finance Teams channel. Use for monthly close reviews.
      inputParameters:
      - name: fiscal_period
        in: body
        type: string
        description: Fiscal period in YYYYMM format, e.g. 202603.
      steps:
      - name: get-variance
        type: call
        call: sap.get-cost-center-variance
        with:
          fiscal_period: '{{fiscal_period}}'
      - name: post-report
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_finance_channel_id
          text: Budget Variance Report for period {{fiscal_period}} is ready. {{get-variance.total_cost_centers}} cost centers reviewed.
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_COSTCENTER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: cost-center-variance
      path: /A_CostCenter
      inputParameters:
      - name: fiscal_period
        in: query
      operations:
      - name: get-cost-center-variance
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Submits a compensation change request for an employee in Workday, routes it for manager and HR approval, and notifies all parties via Teams when the action is complete.

naftiko: '0.5'
info:
  label: Workday Compensation Change Approval
  description: Submits a compensation change request for an employee in Workday, routes it for manager and HR approval, and notifies all parties via Teams when the action is complete.
  tags:
  - hr
  - compensation
  - workday
  - microsoft-teams
  - approval
capability:
  exposes:
  - type: mcp
    namespace: hr-comp
    port: 8080
    tools:
    - name: submit-comp-change
      description: Given a Workday employee ID, new base salary, and effective date, submit a compensation change request in Workday and notify the manager and HR partner via Teams.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The Workday worker ID of the employee receiving the compensation change.
      - name: new_salary
        in: body
        type: number
        description: The new base salary amount in the employee's currency.
      - name: effective_date
        in: body
        type: string
        description: Effective date for the compensation change in ISO 8601 format.
      steps:
      - name: get-worker
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{employee_id}}'
      - name: submit-change
        type: call
        call: workday.submit-comp-change
        with:
          worker_id: '{{employee_id}}'
          new_salary: '{{new_salary}}'
          effective_date: '{{effective_date}}'
      - name: notify-manager
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{get-worker.manager_email}}'
          text: A compensation change for {{get-worker.full_name}} (effective {{effective_date}}) has been submitted and is pending your approval in Workday.
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /coca-cola/workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
      - name: submit-comp-change
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: mail
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves LinkedIn Sponsored Content campaign analytics for the past week and posts an engagement summary to the Marketing Microsoft Teams channel.

naftiko: '0.5'
info:
  label: LinkedIn Sponsored Campaign Performance Digest
  description: Retrieves LinkedIn Sponsored Content campaign analytics for the past week and posts an engagement summary to the Marketing Microsoft Teams channel.
  tags:
  - marketing
  - linkedin
  - social
  - reporting
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: marketing-reporting
    port: 8080
    tools:
    - name: digest-linkedin-campaigns
      description: Fetch LinkedIn Sponsored Content campaign performance metrics for the past 7 days and post an engagement digest to the Marketing Teams channel. Use for weekly social performance reviews.
      inputParameters:
      - name: account_id
        in: body
        type: string
        description: The LinkedIn ad account ID (numeric).
      steps:
      - name: get-analytics
        type: call
        call: linkedin.get-campaign-analytics
        with:
          account_id: '{{account_id}}'
          dateRange_start_day: '1'
          dateRange_end_day: '7'
      - name: post-digest
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_marketing_channel_id
          text: 'LinkedIn Campaign Digest: {{get-analytics.total_impressions}} impressions, {{get-analytics.total_clicks}} clicks this week for account {{account_id}}.'
  consumes:
  - type: http
    namespace: linkedin
    baseUri: https://api.linkedin.com/v2
    authentication:
      type: bearer
      token: $secrets.linkedin_token
    resources:
    - name: ad-analytics
      path: /adAnalytics
      inputParameters:
      - name: account_id
        in: query
      - name: dateRange_start_day
        in: query
      - name: dateRange_end_day
        in: query
      operations:
      - name: get-campaign-analytics
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Triggers a refresh of the Coca-Cola bottling operations Power BI dataset and returns the refresh status.

naftiko: '0.5'
info:
  label: Power BI Bottling Dashboard Refresh
  description: Triggers a refresh of the Coca-Cola bottling operations Power BI dataset and returns the refresh status.
  tags:
  - analytics
  - power-bi
  - manufacturing
capability:
  exposes:
  - type: mcp
    namespace: analytics
    port: 8080
    tools:
    - name: refresh-bottling-dashboard
      description: Trigger a Power BI dataset refresh for the bottling operations dashboard. Returns refresh request ID and status.
      inputParameters:
      - name: dataset_id
        in: body
        type: string
        description: The Power BI dataset ID for the bottling dashboard.
      call: powerbi.trigger-refresh
      with:
        dataset_id: '{{dataset_id}}'
      outputParameters:
      - name: request_id
        type: string
        mapping: $.requestId
      - name: status
        type: string
        mapping: $.status
  consumes:
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets/{{dataset_id}}/refreshes
      inputParameters:
      - name: dataset_id
        in: path
      operations:
      - name: trigger-refresh
        method: POST

Retrieves metadata for a document from a SharePoint document library, returning file name, modified date, modified by, and file size.

naftiko: '0.5'
info:
  label: SharePoint Document Retrieval
  description: Retrieves metadata for a document from a SharePoint document library, returning file name, modified date, modified by, and file size.
  tags:
  - collaboration
  - sharepoint
  - document-management
capability:
  exposes:
  - type: mcp
    namespace: documents
    port: 8080
    tools:
    - name: get-document-metadata
      description: Retrieve document metadata from SharePoint. Returns file name, last modified date, modified by, and file size.
      inputParameters:
      - name: site_id
        in: body
        type: string
        description: The SharePoint site ID.
      - name: file_path
        in: body
        type: string
        description: The path to the file in the document library.
      call: sharepoint.get-file
      with:
        site_id: '{{site_id}}'
        file_path: '{{file_path}}'
      outputParameters:
      - name: file_name
        type: string
        mapping: $.name
      - name: modified_date
        type: string
        mapping: $.lastModifiedDateTime
      - name: modified_by
        type: string
        mapping: $.lastModifiedBy.user.displayName
      - name: file_size
        type: string
        mapping: $.size
  consumes:
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /sites/{{site_id}}/drive/root:/{{file_path}}
      inputParameters:
      - name: site_id
        in: path
      - name: file_path
        in: path
      operations:
      - name: get-file
        method: GET

Initiates a performance review cycle in Workday for a given employee population and notifies managers via Teams to complete evaluations by the deadline.

naftiko: '0.5'
info:
  label: Workday Performance Review Cycle Kickoff
  description: Initiates a performance review cycle in Workday for a given employee population and notifies managers via Teams to complete evaluations by the deadline.
  tags:
  - hr
  - performance-management
  - workday
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: hr-performance
    port: 8080
    tools:
    - name: kickoff-review-cycle
      description: Start a performance review cycle in Workday for a defined employee group and post a notification to managers via Teams with the review deadline. Use for annual or mid-year performance cycle launches.
      inputParameters:
      - name: review_period
        in: body
        type: string
        description: The review period label, e.g. 2026-Annual.
      - name: due_date
        in: body
        type: string
        description: Review completion deadline in ISO 8601 format.
      steps:
      - name: create-review-event
        type: call
        call: workday.create-review-event
        with:
          period: '{{review_period}}'
          due_date: '{{due_date}}'
      - name: notify-managers
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_hr_channel_id
          text: Performance review cycle {{review_period}} is open. Please complete evaluations by {{due_date}}.
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: review-events
      path: /coca-cola/performanceReviews
      operations:
      - name: create-review-event
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Reports a plant safety incident by recording it in ServiceNow, updating the SAP plant maintenance log, notifying safety officers via Microsoft Teams, and creating a Workday worker safety record.

naftiko: '0.5'
info:
  label: Plant Safety Incident Reporting
  description: Reports a plant safety incident by recording it in ServiceNow, updating the SAP plant maintenance log, notifying safety officers via Microsoft Teams, and creating a Workday worker safety record.
  tags:
  - manufacturing
  - servicenow
  - sap
  - microsoft-teams
  - workday
capability:
  exposes:
  - type: mcp
    namespace: safety
    port: 8080
    tools:
    - name: report-safety-incident
      description: 'Orchestrate safety incident reporting: create ServiceNow record, update SAP maintenance log, notify safety team, and update Workday.'
      inputParameters:
      - name: plant_code
        in: body
        type: string
        description: The plant code where the incident occurred.
      - name: worker_id
        in: body
        type: string
        description: The Workday worker ID of the involved employee.
      - name: incident_description
        in: body
        type: string
        description: Description of the safety incident.
      - name: severity
        in: body
        type: string
        description: 'Severity level: low, medium, high, critical.'
      steps:
      - name: create-safety-record
        type: call
        call: servicenow.create-incident
        with:
          short_description: Plant safety incident at {{plant_code}}
          description: '{{incident_description}}'
          category: plant_safety
          urgency: '{{severity}}'
          assignment_group: Plant_Safety_{{plant_code}}
      - name: update-maintenance-log
        type: call
        call: sap.create-notification
        with:
          plant: '{{plant_code}}'
          notification_type: safety
          description: '{{incident_description}}'
      - name: get-worker
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{worker_id}}'
      - name: notify-safety-team
        type: call
        call: msteams.send-message
        with:
          channel_id: plant-safety
          text: 'SAFETY INCIDENT at plant {{plant_code}}: {{incident_description}}. Severity: {{severity}}. Involved: {{get-worker.full_name}}. ServiceNow: {{create-safety-record.number}}'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://cocacola.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_MAINTNOTIFICATION
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: notifications
      path: /MaintenanceNotification
      operations:
      - name: create-notification
        method: POST
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /coca-cola/workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves vendor master data from SAP S/4HANA by vendor ID, returning payment terms, bank details status, and contact information for supplier management.

naftiko: '0.5'
info:
  label: SAP Vendor Master Data Lookup
  description: Retrieves vendor master data from SAP S/4HANA by vendor ID, returning payment terms, bank details status, and contact information for supplier management.
  tags:
  - procurement
  - sap
  - vendor-management
capability:
  exposes:
  - type: mcp
    namespace: vendor-mgmt
    port: 8080
    tools:
    - name: get-vendor
      description: Look up a SAP supplier/vendor record by vendor ID. Returns company name, payment terms, currency, and bank verification status. Use for supplier onboarding checks or payment processing.
      inputParameters:
      - name: vendor_id
        in: body
        type: string
        description: The SAP vendor (supplier) ID, e.g. 1000012.
      call: sap.get-vendor
      with:
        vendor_id: '{{vendor_id}}'
      outputParameters:
      - name: company_name
        type: string
        mapping: $.d.SupplierName
      - name: payment_terms
        type: string
        mapping: $.d.PaymentTerms
      - name: currency
        type: string
        mapping: $.d.Currency
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_BUSINESS_PARTNER
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: suppliers
      path: /A_Supplier('{{vendor_id}}')
      inputParameters:
      - name: vendor_id
        in: path
      operations:
      - name: get-vendor
        method: GET

Retrieves batch details for a material from SAP S/4HANA, returning batch number, production date, shelf life expiry, and batch status.

naftiko: '0.5'
info:
  label: SAP Batch Traceability Lookup
  description: Retrieves batch details for a material from SAP S/4HANA, returning batch number, production date, shelf life expiry, and batch status.
  tags:
  - manufacturing
  - sap
  - quality
  - traceability
capability:
  exposes:
  - type: mcp
    namespace: quality
    port: 8080
    tools:
    - name: get-batch-details
      description: Look up batch traceability information in SAP. Returns batch number, production date, expiry date, and batch status.
      inputParameters:
      - name: material_number
        in: body
        type: string
        description: The SAP material number.
      - name: batch_number
        in: body
        type: string
        description: The SAP batch number.
      call: sap.get-batch
      with:
        material_number: '{{material_number}}'
        batch_number: '{{batch_number}}'
      outputParameters:
      - name: production_date
        type: string
        mapping: $.d.MfgDate
      - name: expiry_date
        type: string
        mapping: $.d.ShelfLifeExpirationDate
      - name: batch_status
        type: string
        mapping: $.d.BatchStatus
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_BATCH_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: batches
      path: /A_Batch(Material='{{material_number}}',Batch='{{batch_number}}')
      inputParameters:
      - name: material_number
        in: path
      - name: batch_number
        in: path
      operations:
      - name: get-batch
        method: GET

Tracks distributor order fulfillment by pulling the sales order from SAP, checking delivery status, and updating the Salesforce account with fulfillment details.

naftiko: '0.5'
info:
  label: Distributor Order Fulfillment Tracker
  description: Tracks distributor order fulfillment by pulling the sales order from SAP, checking delivery status, and updating the Salesforce account with fulfillment details.
  tags:
  - distribution
  - sap
  - salesforce
  - supply-chain
capability:
  exposes:
  - type: mcp
    namespace: distribution
    port: 8080
    tools:
    - name: track-distributor-order
      description: 'Track a distributor order: pull SAP sales order, check delivery, and update Salesforce account.'
      inputParameters:
      - name: sales_order_number
        in: body
        type: string
        description: The SAP sales order number.
      - name: account_id
        in: body
        type: string
        description: The Salesforce distributor account ID.
      steps:
      - name: get-sales-order
        type: call
        call: sap.get-sales-order
        with:
          sales_order_number: '{{sales_order_number}}'
      - name: get-delivery-status
        type: call
        call: sap.get-delivery-by-order
        with:
          sales_order: '{{sales_order_number}}'
      - name: update-sf-account
        type: call
        call: salesforce.update-account
        with:
          account_id: '{{account_id}}'
          last_order_status: '{{get-sales-order.status}}'
          last_delivery_status: '{{get-delivery-status.delivery_status}}'
          last_delivery_date: '{{get-delivery-status.actual_goods_issue_date}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_SALES_ORDER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: sales-orders
      path: /A_SalesOrder('{{sales_order_number}}')
      inputParameters:
      - name: sales_order_number
        in: path
      operations:
      - name: get-sales-order
        method: GET
    - name: deliveries
      path: /A_SalesOrder('{{sales_order}}')/to_Delivery
      inputParameters:
      - name: sales_order
        in: path
      operations:
      - name: get-delivery-by-order
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: accounts
      path: /sobjects/Account/{{account_id}}
      inputParameters:
      - name: account_id
        in: path
      operations:
      - name: update-account
        method: PATCH

Generates energy cost optimization reports by pulling plant energy data from SAP, comparing with utility rate data, and publishing the report to SharePoint.

naftiko: '0.5'
info:
  label: Energy Cost Optimization Report
  description: Generates energy cost optimization reports by pulling plant energy data from SAP, comparing with utility rate data, and publishing the report to SharePoint.
  tags:
  - manufacturing
  - finance
  - sap
  - sharepoint
capability:
  exposes:
  - type: mcp
    namespace: energy-optimization
    port: 8080
    tools:
    - name: generate-energy-report
      description: 'Generate energy cost report: pull SAP plant data, compare utility rates, and publish to SharePoint.'
      inputParameters:
      - name: plant_code
        in: body
        type: string
        description: The plant code.
      - name: period
        in: body
        type: string
        description: The reporting period, e.g. 2026-03.
      steps:
      - name: get-energy-consumption
        type: call
        call: sap.get-plant-energy-consumption
        with:
          plant: '{{plant_code}}'
          period: '{{period}}'
      - name: get-energy-costs
        type: call
        call: sap.get-cost-center-actuals
        with:
          cost_center: energy-{{plant_code}}
          period: '{{period}}'
      - name: publish-report
        type: call
        call: sharepoint.upload-file
        with:
          site_id: operations
          folder_path: Energy/Reports/{{period}}
          file_name: energy-optimization-{{plant_code}}.json
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PLANT_METRICS_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: energy
      path: /PlantEnergyConsumption(Plant='{{plant}}',Period='{{period}}')
      inputParameters:
      - name: plant
        in: path
      - name: period
        in: path
      operations:
      - name: get-plant-energy-consumption
        method: GET
    - name: cost-centers
      path: /A_CostCenter('{{cost_center}}')/to_Actuals?$filter=Period eq '{{period}}'
      inputParameters:
      - name: cost_center
        in: path
      - name: period
        in: query
      operations:
      - name: get-cost-center-actuals
        method: GET
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /sites/{{site_id}}/drive/root:/{{folder_path}}/{{file_name}}:/content
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      - name: file_name
        in: path
      operations:
      - name: upload-file
        method: PUT

Retrieves all open job requisitions from Workday and publishes a digest to a Microsoft Teams HR channel for weekly staffing review.

naftiko: '0.5'
info:
  label: Open Job Requisition Report
  description: Retrieves all open job requisitions from Workday and publishes a digest to a Microsoft Teams HR channel for weekly staffing review.
  tags:
  - hr
  - recruiting
  - workday
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: hr-recruiting
    port: 8080
    tools:
    - name: digest-open-requisitions
      description: Fetch all open job requisitions from Workday and post a summary digest to the HR staffing Microsoft Teams channel. Use for weekly recruiting pipeline reviews.
      steps:
      - name: get-requisitions
        type: call
        call: workday.list-job-requisitions
        with:
          status: Open
      - name: post-digest
        type: call
        call: msteams.send-message
        with:
          channel_id: $secrets.teams_hr_channel_id
          text: 'Weekly Open Requisitions: {{get-requisitions.total_count}} open roles across Coca-Cola.'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: job-requisitions
      path: /coca-cola/jobRequisitions
      inputParameters:
      - name: status
        in: query
      operations:
      - name: list-job-requisitions
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Retrieves a journal entry from Oracle Cloud Financials by journal header ID, returning period, status, total debit, and total credit.

naftiko: '0.5'
info:
  label: Oracle Cloud Financial Journal Entry Lookup
  description: Retrieves a journal entry from Oracle Cloud Financials by journal header ID, returning period, status, total debit, and total credit.
  tags:
  - finance
  - oracle-cloud
  - general-ledger
capability:
  exposes:
  - type: mcp
    namespace: finance
    port: 8080
    tools:
    - name: get-journal-entry
      description: Look up an Oracle Cloud Financials journal entry. Returns accounting period, status, total debit, and total credit amounts.
      inputParameters:
      - name: journal_header_id
        in: body
        type: string
        description: The Oracle Cloud journal header ID.
      call: oracle.get-journal
      with:
        journal_header_id: '{{journal_header_id}}'
      outputParameters:
      - name: period
        type: string
        mapping: $.AccountingPeriod
      - name: status
        type: string
        mapping: $.Status
      - name: total_debit
        type: string
        mapping: $.TotalDebitAmount
      - name: total_credit
        type: string
        mapping: $.TotalCreditAmount
  consumes:
  - type: http
    namespace: oracle
    baseUri: https://coca-cola.oraclecloud.com/fscmRestApi/resources/v1
    authentication:
      type: basic
      username: $secrets.oracle_user
      password: $secrets.oracle_password
    resources:
    - name: journals
      path: /journalHeaders/{{journal_header_id}}
      inputParameters:
      - name: journal_header_id
        in: path
      operations:
      - name: get-journal
        method: GET

Retrieves brand-level web analytics from Adobe Analytics, including page views, unique visitors, and average session duration.

naftiko: '0.5'
info:
  label: Adobe Analytics Brand Performance
  description: Retrieves brand-level web analytics from Adobe Analytics, including page views, unique visitors, and average session duration.
  tags:
  - marketing
  - adobe-analytics
  - brand-management
capability:
  exposes:
  - type: mcp
    namespace: brand-analytics
    port: 8080
    tools:
    - name: get-brand-performance
      description: Fetch brand web performance metrics from Adobe Analytics. Returns page views, unique visitors, and average session duration.
      inputParameters:
      - name: report_suite_id
        in: body
        type: string
        description: The Adobe Analytics report suite ID.
      - name: brand_segment
        in: body
        type: string
        description: The brand segment filter, e.g. coca-cola-classic.
      call: adobe.get-report
      with:
        report_suite_id: '{{report_suite_id}}'
        brand_segment: '{{brand_segment}}'
      outputParameters:
      - name: page_views
        type: string
        mapping: $.reportData.totals[0]
      - name: unique_visitors
        type: string
        mapping: $.reportData.totals[1]
      - name: avg_session_duration
        type: string
        mapping: $.reportData.totals[2]
  consumes:
  - type: http
    namespace: adobe
    baseUri: https://analytics.adobe.io/api/cocacola
    authentication:
      type: bearer
      token: $secrets.adobe_analytics_token
    resources:
    - name: reports
      path: /reports
      operations:
      - name: get-report
        method: POST

Aggregates sustainability metrics by pulling energy consumption from SAP plant maintenance, water usage from environmental monitoring, and posting a consolidated ESG report to SharePoint.

naftiko: '0.5'
info:
  label: Sustainability Reporting Aggregator
  description: Aggregates sustainability metrics by pulling energy consumption from SAP plant maintenance, water usage from environmental monitoring, and posting a consolidated ESG report to SharePoint.
  tags:
  - manufacturing
  - sap
  - sharepoint
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: sustainability
    port: 8080
    tools:
    - name: aggregate-sustainability-report
      description: Aggregate sustainability data from SAP and environmental monitoring, then publish report to SharePoint and Teams.
      inputParameters:
      - name: plant_code
        in: body
        type: string
        description: The plant code.
      - name: reporting_period
        in: body
        type: string
        description: The reporting period, e.g. 2026-Q1.
      steps:
      - name: get-energy-data
        type: call
        call: sap.get-plant-energy-consumption
        with:
          plant: '{{plant_code}}'
          period: '{{reporting_period}}'
      - name: get-water-usage
        type: call
        call: sap.get-plant-water-usage
        with:
          plant: '{{plant_code}}'
          period: '{{reporting_period}}'
      - name: upload-report
        type: call
        call: sharepoint.upload-file
        with:
          site_id: sustainability
          folder_path: Reports/{{reporting_period}}
          file_name: plant-{{plant_code}}-sustainability.json
      - name: notify-esg-team
        type: call
        call: msteams.send-message
        with:
          channel_id: sustainability
          text: 'Sustainability report for plant {{plant_code}} ({{reporting_period}}): Energy consumption: {{get-energy-data.total_kwh}} kWh. Water usage: {{get-water-usage.total_liters}} liters. Report uploaded to SharePoint.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_PLANT_METRICS_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: energy
      path: /PlantEnergyConsumption(Plant='{{plant}}',Period='{{period}}')
      inputParameters:
      - name: plant
        in: path
      - name: period
        in: path
      operations:
      - name: get-plant-energy-consumption
        method: GET
    - name: water
      path: /PlantWaterUsage(Plant='{{plant}}',Period='{{period}}')
      inputParameters:
      - name: plant
        in: path
      - name: period
        in: path
      operations:
      - name: get-plant-water-usage
        method: GET
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /sites/{{site_id}}/drive/root:/{{folder_path}}/{{file_name}}:/content
      inputParameters:
      - name: site_id
        in: path
      - name: folder_path
        in: path
      - name: file_name
        in: path
      operations:
      - name: upload-file
        method: PUT
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Monitors accounts receivable aging by pulling AR data from SAP, matching with Salesforce customer accounts, and alerting the collections team via Microsoft Teams.

naftiko: '0.5'
info:
  label: Accounts Receivable Aging Alert
  description: Monitors accounts receivable aging by pulling AR data from SAP, matching with Salesforce customer accounts, and alerting the collections team via Microsoft Teams.
  tags:
  - finance
  - sap
  - salesforce
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: ar-management
    port: 8080
    tools:
    - name: check-ar-aging
      description: 'Check AR aging: pull SAP receivables, match Salesforce accounts, and alert collections team.'
      inputParameters:
      - name: company_code
        in: body
        type: string
        description: The SAP company code.
      - name: aging_bucket
        in: body
        type: string
        description: 'The aging bucket to check: 30, 60, 90, 120.'
      steps:
      - name: get-ar-aging
        type: call
        call: sap.get-ar-aging-report
        with:
          company_code: '{{company_code}}'
          aging_days: '{{aging_bucket}}'
      - name: get-customer-accounts
        type: call
        call: salesforce.get-customer-list
        with:
          overdue_threshold: '{{aging_bucket}}'
      - name: alert-collections
        type: call
        call: msteams.send-message
        with:
          channel_id: finance-collections
          text: 'AR Aging Alert ({{aging_bucket}}+ days): Total overdue: ${{get-ar-aging.total_overdue}}. Customer count: {{get-ar-aging.customer_count}}. Top overdue: {{get-ar-aging.top_customer}}.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_AR_AGING_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: aging
      path: /ARAgingReport(CompanyCode='{{company_code}}',AgingDays={{aging_days}})
      inputParameters:
      - name: company_code
        in: path
      - name: aging_days
        in: path
      operations:
      - name: get-ar-aging-report
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: customers
      path: /query?q=SELECT+Id,Name+FROM+Account+WHERE+Days_Overdue__c>=+{{overdue_threshold}}
      inputParameters:
      - name: overdue_threshold
        in: query
      operations:
      - name: get-customer-list
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Converts a qualified Salesforce lead into an opportunity, creates an account if needed, and notifies the account owner via Teams.

naftiko: '0.5'
info:
  label: Salesforce Lead-to-Opportunity Conversion
  description: Converts a qualified Salesforce lead into an opportunity, creates an account if needed, and notifies the account owner via Teams.
  tags:
  - sales
  - crm
  - salesforce
  - lead-management
capability:
  exposes:
  - type: mcp
    namespace: sales-ops
    port: 8080
    tools:
    - name: convert-lead
      description: Given a Salesforce lead ID, convert the lead to an opportunity and account in Salesforce, then notify the assigned sales rep via Teams. Use for automated lead qualification workflows.
      inputParameters:
      - name: lead_id
        in: body
        type: string
        description: The Salesforce Lead ID to convert.
      steps:
      - name: get-lead
        type: call
        call: salesforce-lead.get-lead
        with:
          lead_id: '{{lead_id}}'
      - name: convert-lead
        type: call
        call: salesforce-convert.convert-lead
        with:
          lead_id: '{{lead_id}}'
          convertedStatus: Qualified
      - name: notify-owner
        type: call
        call: msteams.send-message
        with:
          recipient_upn: '{{get-lead.owner_email}}'
          text: 'Lead {{get-lead.name}} has been converted to an opportunity. Account: {{convert-lead.accountId}}'
  consumes:
  - type: http
    namespace: salesforce-lead
    baseUri: https://cocacola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: lead
      path: /sobjects/Lead/{{lead_id}}
      inputParameters:
      - name: lead_id
        in: path
      operations:
      - name: get-lead
        method: GET
  - type: http
    namespace: salesforce-convert
    baseUri: https://cocacola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: lead-convert
      path: /sobjects/Lead/{{lead_id}}
      inputParameters:
      - name: lead_id
        in: path
      operations:
      - name: convert-lead
        method: PATCH
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: mail
      path: /users/{{recipient_upn}}/sendMail
      inputParameters:
      - name: recipient_upn
        in: path
      operations:
      - name: send-message
        method: POST

When a shipment delay is detected, retrieves delivery details from SAP, updates the Salesforce opportunity, and escalates to the logistics team via Microsoft Teams.

naftiko: '0.5'
info:
  label: Supply Chain Shipment Delay Escalation
  description: When a shipment delay is detected, retrieves delivery details from SAP, updates the Salesforce opportunity, and escalates to the logistics team via Microsoft Teams.
  tags:
  - supply-chain
  - sap
  - salesforce
  - microsoft-teams
  - distribution
capability:
  exposes:
  - type: mcp
    namespace: supply-chain
    port: 8080
    tools:
    - name: escalate-shipment-delay
      description: 'Orchestrate shipment delay escalation: pull SAP delivery details, update Salesforce opportunity, and notify logistics team.'
      inputParameters:
      - name: delivery_number
        in: body
        type: string
        description: The SAP delivery document number.
      - name: opportunity_id
        in: body
        type: string
        description: The related Salesforce opportunity ID.
      steps:
      - name: get-delivery
        type: call
        call: sap.get-delivery
        with:
          delivery_number: '{{delivery_number}}'
      - name: update-opportunity
        type: call
        call: salesforce.update-opportunity
        with:
          opportunity_id: '{{opportunity_id}}'
          delivery_status: Delayed
          delivery_notes: 'Shipment {{delivery_number}} delayed. Original GI date: {{get-delivery.planned_goods_issue_date}}'
      - name: notify-logistics
        type: call
        call: msteams.send-message
        with:
          channel_id: logistics-alerts
          text: 'Shipment delay alert: Delivery {{delivery_number}} to {{get-delivery.ship_to_party}} is delayed. Salesforce opportunity {{opportunity_id}} updated.'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://coca-cola-s4.sap.com/sap/opu/odata/sap/API_OUTBOUND_DELIVERY_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: deliveries
      path: /A_OutbDeliveryHeader('{{delivery_number}}')
      inputParameters:
      - name: delivery_number
        in: path
      operations:
      - name: get-delivery
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://coca-cola.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: opportunities
      path: /sobjects/Opportunity/{{opportunity_id}}
      inputParameters:
      - name: opportunity_id
        in: path
      operations:
      - name: update-opportunity
        method: PATCH
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channels
      path: /teams/{{channel_id}}/channels/{{channel_id}}/messages
      inputParameters:
      - name: channel_id
        in: path
      operations:
      - name: send-message
        method: POST

Handles shortages by checking SAP stock, identifying affected orders, and creating Ariba procurement requests.

naftiko: '0.5'
info:
  label: Raw Material Shortage Alert Handler
  description: Handles shortages by checking SAP stock, identifying affected orders, and creating Ariba procurement requests.
  tags:
  - supply-chain
  - procurement
  - sap
  - manufacturing
capability:
  exposes:
  - type: mcp
    namespace: supply-ops
    port: 8080
    tools:
    - name: handle-shortage
      description: Handle raw material shortage.
      inputParameters:
      - name: material_number
        type: string
        description: Material number.
      - name: plant_code
        type: string
        description: Plant code.
      - name: reorder_qty
        type: number
        description: Reorder quantity.
      steps:
      - name: check-stock
        type: call
        call: sap.get-stock
        with:
          material: '{{material_number}}'
          plant: '{{plant_code}}'
      - name: get-orders
        type: call
        call: sap.get-orders
        with:
          material: '{{material_number}}'
      - name: create-req
        type: call
        call: ariba.create-requisition
        with:
          material: '{{material_number}}'
          quantity: '{{reorder_qty}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-stock
        method: GET
      - name: get-orders
        method: GET
  - type: http
    namespace: ariba
    baseUri: https://openapi.ariba.com/api/supplier-management/v1
    authentication:
      type: bearer
      token: $secrets.ariba_token
    resources:
    - name: suppliers
      path: /suppliers
      operations:
      - name: get-supplier
        method: GET

When an employee's role changes in Workday, updates their Okta application assignments to reflect the new role's access profile.

naftiko: '0.5'
info:
  label: Workday Role Change Access Provisioning
  description: When an employee's role changes in Workday, updates their Okta application assignments to reflect the new role's access profile.
  tags:
  - hr
  - identity
  - workday
  - okta
  - access-management
capability:
  exposes:
  - type: mcp
    namespace: hr-identity
    port: 8080
    tools:
    - name: sync-role-access
      description: Given a Workday employee ID and new job profile, update Okta group memberships to match the new role's access entitlements.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The Workday worker ID.
      - name: new_job_profile
        in: body
        type: string
        description: The new Workday job profile name.
      steps:
      - name: get-worker
        type: call
        call: workday.get-worker
        with:
          worker_id: '{{employee_id}}'
      - name: assign-okta-group
        type: call
        call: okta.add-user-to-group
        with:
          userId: '{{get-worker.okta_user_id}}'
          groupProfile: '{{new_job_profile}}'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /colgate-palmolive/workers/{{worker_id}}
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: okta
    baseUri: https://colgate-palmolive.okta.com/api/v1
    authentication:
      type: apikey
      key: Authorization
      value: $secrets.okta_api_token
      placement: header
    resources:
    - name: group-members
      path: /groups/{{groupProfile}}/users/{{userId}}
      inputParameters:
      - name: groupProfile
        in: path
      - name: userId
        in: path
      operations:
      - name: add-user-to-group
        method: PUT

Retrieves the sales opportunity pipeline from Salesforce for a business unit.

naftiko: '0.5'
info:
  label: Salesforce Opportunity Pipeline Lookup
  description: Retrieves the sales opportunity pipeline from Salesforce for a business unit.
  tags:
  - sales
  - crm
  - salesforce
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: crm-sales
    port: 8080
    tools:
    - name: get-pipeline
      description: Look up Salesforce opportunity pipeline by business unit.
      inputParameters:
      - name: business_unit
        type: string
        description: Business unit name.
      call: salesforce.get-pipeline
      with:
        bu: '{{business_unit}}'
      outputParameters:
      - name: total_value
        type: string
        mapping: $.totalSize
      - name: opportunities
        type: string
        mapping: $.records
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://colgatepalmolive.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: sobjects
      path: /sobjects
      operations:
      - name: query
        method: GET

Retrieves Jira project backlog summary with issue counts by priority and status.

naftiko: '0.5'
info:
  label: Jira Project Backlog Summary
  description: Retrieves Jira project backlog summary with issue counts by priority and status.
  tags:
  - project-management
  - operations
  - jira
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: project-ops
    port: 8080
    tools:
    - name: get-backlog
      description: Get Jira project backlog summary.
      inputParameters:
      - name: project_key
        type: string
        description: Jira project key.
      call: jira.search-issues
      with:
        jql: project={{project_key}} AND status!=Done
      outputParameters:
      - name: total
        type: string
        mapping: $.total
      - name: issues
        type: string
        mapping: $.issues
  consumes:
  - type: http
    namespace: jira
    baseUri: https://colgatepalmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST

Retrieves web traffic metrics from Google Analytics for a brand website.

naftiko: '0.5'
info:
  label: Google Analytics Web Traffic Report
  description: Retrieves web traffic metrics from Google Analytics for a brand website.
  tags:
  - marketing
  - analytics
  - google-analytics
  - web
capability:
  exposes:
  - type: mcp
    namespace: web-analytics
    port: 8080
    tools:
    - name: get-traffic
      description: Fetch web traffic data from Google Analytics.
      inputParameters:
      - name: property_id
        type: string
        description: GA4 property ID.
      - name: date_from
        type: string
        description: Start date.
      - name: date_to
        type: string
        description: End date.
      call: ga.run-report
      with:
        property: '{{property_id}}'
        startDate: '{{date_from}}'
      outputParameters:
      - name: sessions
        type: string
        mapping: $.rows[0].metricValues[0].value
      - name: conversion_rate
        type: string
        mapping: $.rows[0].metricValues[1].value
  consumes:
  - type: http
    namespace: ga
    baseUri: https://analyticsdata.googleapis.com/v1beta
    authentication:
      type: bearer
      token: $secrets.google_analytics_token
    resources:
    - name: reports
      path: /properties/runReport
      operations:
      - name: run-report
        method: POST

Pulls current headcount by department and cost center from Workday and returns the structured dataset for workforce planning and finance reporting.

naftiko: '0.5'
info:
  label: Workday Headcount Report Snapshot
  description: Pulls current headcount by department and cost center from Workday and returns the structured dataset for workforce planning and finance reporting.
  tags:
  - hr
  - finance
  - workday
  - reporting
  - headcount
capability:
  exposes:
  - type: mcp
    namespace: hr-reporting
    port: 8080
    tools:
    - name: get-headcount-snapshot
      description: Returns current active employee headcount grouped by department and cost center from Workday. Use for workforce planning, finance period close, and budget reviews.
      call: workday.get-headcount
      outputParameters:
      - name: employees
        type: array
        mapping: $.data
        items:
        - name: employee_id
          type: string
          mapping: $.id
        - name: full_name
          type: string
          mapping: $.name
        - name: department
          type: string
          mapping: $.department
        - name: cost_center
          type: string
          mapping: $.costCenter
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /colgate-palmolive/workers
      operations:
      - name: get-headcount
        method: GET

Tracks regulatory compliance from Jira submissions, SharePoint docs, and Power BI dashboard.

naftiko: '0.5'
info:
  label: Regulatory Document Compliance Tracker
  description: Tracks regulatory compliance from Jira submissions, SharePoint docs, and Power BI dashboard.
  tags:
  - regulatory
  - quality
  - jira
  - sharepoint
  - power-bi
capability:
  exposes:
  - type: mcp
    namespace: regulatory-ops
    port: 8080
    tools:
    - name: track-compliance
      description: Track regulatory submission status.
      inputParameters:
      - name: submission_id
        type: string
        description: Jira submission key.
      steps:
      - name: get-status
        type: call
        call: jira.get-issue
        with:
          issue_key: '{{submission_id}}'
      - name: check-docs
        type: call
        call: sharepoint.list-folder
        with:
          folder: '{{submission_id}}'
      - name: refresh
        type: call
        call: powerbi.refresh-dataset
        with:
          datasetId: regulatory-tracker
  consumes:
  - type: http
    namespace: jira
    baseUri: https://colgatepalmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /sites/drive/items
      operations:
      - name: search-docs
        method: GET
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets
      operations:
      - name: refresh-dataset
        method: POST

Audits privileged Okta accounts against Workday employment, creating ServiceNow review tasks.

naftiko: '0.5'
info:
  label: Okta Privileged Access Audit
  description: Audits privileged Okta accounts against Workday employment, creating ServiceNow review tasks.
  tags:
  - security
  - identity
  - okta
  - workday
  - servicenow
capability:
  exposes:
  - type: mcp
    namespace: security-audit
    port: 8080
    tools:
    - name: audit-access
      description: Audit privileged access.
      inputParameters:
      - name: role_type
        type: string
        description: Okta admin role type.
      steps:
      - name: get-admins
        type: call
        call: okta.list-admins
        with:
          role_type: '{{role_type}}'
      - name: check-employment
        type: call
        call: workday.get-active
        with:
          emails: '{{get-admins.emails}}'
      - name: create-review
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Access audit: {{role_type}}'
  consumes:
  - type: http
    namespace: okta
    baseUri: https://colgatepalmolive.okta.com/api/v1
    authentication:
      type: bearer
      token: $secrets.okta_api_token
    resources:
    - name: users
      path: /users
      operations:
      - name: get-user
        method: GET
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /colgatepalmolive/workers
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://colgatepalmolive.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST

Creates intercompany transfers in SAP, updates Snowflake forecasts, and notifies via Teams.

naftiko: '0.5'
info:
  label: SAP Intercompany Transfer Workflow
  description: Creates intercompany transfers in SAP, updates Snowflake forecasts, and notifies via Teams.
  tags:
  - supply-chain
  - logistics
  - sap
  - snowflake
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: intercompany
    port: 8080
    tools:
    - name: create-transfer
      description: Create intercompany stock transfer.
      inputParameters:
      - name: material
        type: string
        description: Material.
      - name: from_plant
        type: string
        description: Source plant.
      - name: to_plant
        type: string
        description: Target plant.
      - name: quantity
        type: number
        description: Quantity.
      steps:
      - name: transfer
        type: call
        call: sap.create-transfer
        with:
          material: '{{material}}'
          from: '{{from_plant}}'
          to: '{{to_plant}}'
      - name: update
        type: call
        call: snowflake.execute-query
        with:
          warehouse: SC_WH
          query: CALL update_forecast('{{to_plant}}', '{{material}}', {{quantity}})
      - name: notify
        type: call
        call: msteams.send-message
        with:
          channel_id: logistics
          text: 'Transfer: {{quantity}} of {{material}} from {{from_plant}} to {{to_plant}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_STOCK_TRANSFER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: create-transfer
        method: POST
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /teams/channels/messages
      operations:
      - name: send-message
        method: POST

Queries the Snowflake account usage schema to identify long-running and expensive queries, and posts a performance audit report to the data engineering Teams channel.

naftiko: '0.5'
info:
  label: Snowflake Query Performance Audit
  description: Queries the Snowflake account usage schema to identify long-running and expensive queries, and posts a performance audit report to the data engineering Teams channel.
  tags:
  - data
  - analytics
  - snowflake
  - microsoft-teams
  - monitoring
capability:
  exposes:
  - type: mcp
    namespace: data-performance
    port: 8080
    tools:
    - name: audit-query-performance
      description: Given a time window and cost threshold, retrieve expensive Snowflake queries from account usage and post a top offenders report to the data engineering Teams channel.
      inputParameters:
      - name: hours_back
        in: body
        type: integer
        description: Number of hours to look back for query history.
      - name: credits_threshold
        in: body
        type: number
        description: Minimum credits consumed to flag a query as expensive.
      steps:
      - name: get-expensive-queries
        type: call
        call: snowflake.get-query-history
        with:
          hoursBack: '{{hours_back}}'
          creditsThreshold: '{{credits_threshold}}'
      - name: post-audit-report
        type: call
        call: msteams.post-channel-message
        with:
          channelId: data-engineering
          message: 'Snowflake query audit (last {{hours_back}}h): {{get-expensive-queries.queryCount}} expensive queries found. Top query: {{get-expensive-queries.topQuery}}.'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://colgate-palmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: query-history
      path: /statements
      operations:
      - name: get-query-history
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

When a high-priority ServiceNow incident is raised for a digital product, automatically creates a linked Jira bug and notifies the engineering team in Microsoft Teams.

naftiko: '0.5'
info:
  label: ServiceNow Incident to Jira Bug Bridge
  description: When a high-priority ServiceNow incident is raised for a digital product, automatically creates a linked Jira bug and notifies the engineering team in Microsoft Teams.
  tags:
  - itsm
  - devops
  - servicenow
  - jira
  - microsoft-teams
  - incident-response
capability:
  exposes:
  - type: mcp
    namespace: itsm-ops
    port: 8080
    tools:
    - name: handle-p1-incident
      description: Given a ServiceNow P1 incident number, create a linked Jira bug in the engineering project and post an alert to the engineering Teams channel.
      inputParameters:
      - name: incident_number
        in: body
        type: string
        description: The ServiceNow incident number, e.g. INC0012345.
      steps:
      - name: get-incident
        type: call
        call: servicenow.get-incident
        with:
          number: '{{incident_number}}'
      - name: create-jira-bug
        type: call
        call: jira.create-issue
        with:
          projectKey: ENG
          issuetype: Bug
          summary: '[P1 Incident] {{get-incident.short_description}}'
          description: 'ServiceNow: {{incident_number}}

            Impact: {{get-incident.impact}}

            Description: {{get-incident.description}}'
      - name: alert-engineering
        type: call
        call: msteams.post-channel-message
        with:
          channelId: engineering-alerts
          message: 'P1 Incident {{incident_number}}: {{get-incident.short_description}} | Jira: {{create-jira-bug.key}}'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://colgate-palmolive.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.snow_user
      password: $secrets.snow_password
    resources:
    - name: incidents
      path: /table/incident
      inputParameters:
      - name: number
        in: query
      operations:
      - name: get-incident
        method: GET
  - type: http
    namespace: jira
    baseUri: https://colgate-palmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

Registers a new supplier in SAP Ariba, creates the corresponding vendor master record in SAP S/4HANA, and notifies procurement via Teams.

naftiko: '0.5'
info:
  label: SAP Ariba Supplier Onboarding
  description: Registers a new supplier in SAP Ariba, creates the corresponding vendor master record in SAP S/4HANA, and notifies procurement via Teams.
  tags:
  - procurement
  - supplier-management
  - sap-ariba
  - sap
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: supplier-onboarding
    port: 8080
    tools:
    - name: onboard-supplier
      description: Given supplier details, register the supplier in SAP Ariba, create the vendor master in SAP S/4HANA, and notify the procurement team in Teams.
      inputParameters:
      - name: supplier_name
        in: body
        type: string
        description: Legal name of the supplier.
      - name: supplier_email
        in: body
        type: string
        description: Primary contact email for the supplier.
      - name: country_code
        in: body
        type: string
        description: ISO 2-letter country code for the supplier's primary country.
      steps:
      - name: register-ariba
        type: call
        call: ariba.create-supplier
        with:
          name: '{{supplier_name}}'
          email: '{{supplier_email}}'
          country: '{{country_code}}'
      - name: create-vendor-master
        type: call
        call: sap-erp.create-vendor
        with:
          companyName: '{{supplier_name}}'
          aribaId: '{{register-ariba.supplierId}}'
          country: '{{country_code}}'
      - name: notify-procurement
        type: call
        call: msteams.post-channel-message
        with:
          channelId: procurement-team
          message: 'New supplier onboarded: {{supplier_name}} | Ariba ID: {{register-ariba.supplierId}} | SAP Vendor: {{create-vendor-master.vendorId}}'
  consumes:
  - type: http
    namespace: ariba
    baseUri: https://openapi.ariba.com/api/supplier-management/v1
    authentication:
      type: bearer
      token: $secrets.ariba_token
    resources:
    - name: suppliers
      path: /suppliers
      operations:
      - name: create-supplier
        method: POST
  - type: http
    namespace: sap-erp
    baseUri: https://colgate-palmolive-s4.sap.com/sap/opu/odata/sap/API_BUSINESS_PARTNER
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: vendors
      path: /A_BusinessPartner
      operations:
      - name: create-vendor
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

Generates media mix reports from Snowflake, refreshes Power BI, and posts summary to Teams.

naftiko: '0.5'
info:
  label: Media Mix Optimization Report
  description: Generates media mix reports from Snowflake, refreshes Power BI, and posts summary to Teams.
  tags:
  - marketing
  - analytics
  - snowflake
  - power-bi
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: media-planning
    port: 8080
    tools:
    - name: gen-media-report
      description: Generate media mix optimization report.
      inputParameters:
      - name: brand
        type: string
        description: Brand.
      - name: date_from
        type: string
        description: Start.
      - name: date_to
        type: string
        description: End.
      steps:
      - name: get-data
        type: call
        call: snowflake.execute-query
        with:
          warehouse: MARKETING_WH
          query: SELECT channel, roas FROM media WHERE brand='{{brand}}'
      - name: refresh
        type: call
        call: powerbi.refresh-dataset
        with:
          datasetId: media-mix
      - name: post
        type: call
        call: msteams.send-message
        with:
          channel_id: media
          text: Media report for {{brand}} ready
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets
      operations:
      - name: refresh-dataset
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /teams/channels/messages
      operations:
      - name: send-message
        method: POST

When a Datadog monitor triggers a critical alert for a production service, automatically creates a ServiceNow P1 incident and pages the on-call team.

naftiko: '0.5'
info:
  label: Datadog Alert to ServiceNow Incident
  description: When a Datadog monitor triggers a critical alert for a production service, automatically creates a ServiceNow P1 incident and pages the on-call team.
  tags:
  - observability
  - itsm
  - datadog
  - servicenow
  - incident-response
capability:
  exposes:
  - type: mcp
    namespace: observability-ops
    port: 8080
    tools:
    - name: handle-datadog-alert
      description: Given a Datadog monitor alert, create a ServiceNow P1 incident and post a notification to the on-call Teams channel.
      inputParameters:
      - name: monitor_id
        in: body
        type: string
        description: The Datadog monitor ID that triggered the alert.
      - name: monitor_name
        in: body
        type: string
        description: The Datadog monitor name.
      - name: alert_message
        in: body
        type: string
        description: The alert message body from Datadog.
      steps:
      - name: get-monitor
        type: call
        call: datadog.get-monitor
        with:
          monitor_id: '{{monitor_id}}'
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Datadog alert: {{monitor_name}}'
          description: '{{alert_message}}

            Monitor: {{monitor_id}}

            Status: {{get-monitor.overall_state}}'
          urgency: '1'
          impact: '1'
      - name: page-oncall
        type: call
        call: msteams.post-channel-message
        with:
          channelId: oncall-alerts
          message: 'P1 Incident: {{monitor_name}} | ServiceNow: {{create-incident.number}} | Details: {{alert_message}}'
  consumes:
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: monitors
      path: /monitor/{{monitor_id}}
      inputParameters:
      - name: monitor_id
        in: path
      operations:
      - name: get-monitor
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://colgate-palmolive.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.snow_user
      password: $secrets.snow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

Monitors budgets from SAP actuals, Snowflake plans, and alerts via Teams.

naftiko: '0.5'
info:
  label: SAP Cost Center Budget Monitor
  description: Monitors budgets from SAP actuals, Snowflake plans, and alerts via Teams.
  tags:
  - finance
  - operations
  - sap
  - snowflake
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: budget-monitoring
    port: 8080
    tools:
    - name: monitor-budget
      description: Monitor cost center budget.
      inputParameters:
      - name: cost_center
        type: string
        description: Cost center.
      - name: period
        type: string
        description: Period.
      - name: threshold
        type: number
        description: Threshold pct.
      steps:
      - name: get-actuals
        type: call
        call: sap.get-actuals
        with:
          cc: '{{cost_center}}'
          period: '{{period}}'
      - name: get-plan
        type: call
        call: snowflake.execute-query
        with:
          warehouse: FINANCE_WH
          query: SELECT planned FROM budget WHERE cc='{{cost_center}}'
      - name: alert
        type: call
        call: msteams.send-message
        with:
          channel_id: finance
          text: 'Budget: {{cost_center}} at {{get-plan.consumed_pct}}%'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_OPLACCTGDOCITEMCUBE_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-actuals
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /teams/channels/messages
      operations:
      - name: send-message
        method: POST

When Azure Cost Management detects a cost spike exceeding threshold, opens a ServiceNow ticket, tags the offending resources, and alerts the FinOps team in Teams.

naftiko: '0.5'
info:
  label: Azure Cost Anomaly Responder
  description: When Azure Cost Management detects a cost spike exceeding threshold, opens a ServiceNow ticket, tags the offending resources, and alerts the FinOps team in Teams.
  tags:
  - cloud
  - finops
  - azure
  - servicenow
  - microsoft-teams
  - cost-management
capability:
  exposes:
  - type: mcp
    namespace: cloud-finops
    port: 8080
    tools:
    - name: handle-cost-anomaly
      description: Given an Azure subscription ID and anomaly alert details, create a ServiceNow cost management ticket and post an alert to the FinOps Teams channel.
      inputParameters:
      - name: subscription_id
        in: body
        type: string
        description: The Azure subscription ID where the anomaly was detected.
      - name: anomaly_amount
        in: body
        type: number
        description: The anomalous spend amount in USD.
      - name: resource_group
        in: body
        type: string
        description: The Azure resource group associated with the cost spike.
      steps:
      - name: get-cost-details
        type: call
        call: azure-cost.get-usage
        with:
          subscriptionId: '{{subscription_id}}'
          resourceGroup: '{{resource_group}}'
      - name: create-ticket
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Azure cost anomaly: {{resource_group}} +${{anomaly_amount}}'
          category: cloud_cost
          urgency: '2'
      - name: alert-finops
        type: call
        call: msteams.post-channel-message
        with:
          channelId: finops-alerts
          message: 'Cost anomaly detected in {{resource_group}}: +${{anomaly_amount}}. ServiceNow: {{create-ticket.number}}.'
  consumes:
  - type: http
    namespace: azure-cost
    baseUri: https://management.azure.com
    authentication:
      type: bearer
      token: $secrets.azure_token
    resources:
    - name: usage
      path: /subscriptions/{{subscriptionId}}/resourceGroups/{{resourceGroup}}/providers/Microsoft.CostManagement/query
      inputParameters:
      - name: subscriptionId
        in: path
      - name: resourceGroup
        in: path
      operations:
      - name: get-usage
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://colgate-palmolive.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.snow_user
      password: $secrets.snow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

Compares current period payroll totals from Workday against the previous period and flags variances exceeding threshold for finance review.

naftiko: '0.5'
info:
  label: Workday Payroll Variance Report
  description: Compares current period payroll totals from Workday against the previous period and flags variances exceeding threshold for finance review.
  tags:
  - hr
  - finance
  - workday
  - payroll
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: payroll-reporting
    port: 8080
    tools:
    - name: get-payroll-variance
      description: Given a pay period and variance threshold percentage, retrieve Workday payroll totals for the current and prior period, identify variances, and return flagged entries.
      inputParameters:
      - name: pay_period
        in: body
        type: string
        description: Pay period identifier in YYYY-MM format.
      - name: variance_threshold
        in: body
        type: number
        description: Percentage threshold above which a variance is flagged, e.g. 5 for 5%.
      call: workday.get-payroll-results
      with:
        payPeriod: '{{pay_period}}'
      outputParameters:
      - name: total_gross_pay
        type: number
        mapping: $.totals.grossPay
      - name: total_net_pay
        type: number
        mapping: $.totals.netPay
      - name: period
        type: string
        mapping: $.payPeriod
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: payroll-results
      path: /colgate-palmolive/payrollResults
      inputParameters:
      - name: payPeriod
        in: query
      operations:
      - name: get-payroll-results
        method: GET

Retrieves the current hiring pipeline status for an open Workday job requisition and summarizes candidate stage counts for recruiters.

naftiko: '0.5'
info:
  label: Workday Recruiting Candidate Status Tracker
  description: Retrieves the current hiring pipeline status for an open Workday job requisition and summarizes candidate stage counts for recruiters.
  tags:
  - hr
  - recruiting
  - workday
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: recruiting
    port: 8080
    tools:
    - name: get-requisition-pipeline
      description: Given a Workday job requisition ID, return a summary of candidates by stage including screened, interviewed, offered, and rejected counts.
      inputParameters:
      - name: requisition_id
        in: body
        type: string
        description: The Workday job requisition ID.
      call: workday.get-job-requisition
      with:
        requisitionId: '{{requisition_id}}'
      outputParameters:
      - name: job_title
        type: string
        mapping: $.jobRequisition.jobTitle
      - name: total_candidates
        type: number
        mapping: $.jobRequisition.candidateCount
      - name: stage_summary
        type: string
        mapping: $.jobRequisition.stageSummary
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: job-requisitions
      path: /colgate-palmolive/jobRequisitions/{{requisitionId}}
      inputParameters:
      - name: requisitionId
        in: path
      operations:
      - name: get-job-requisition
        method: GET

When an expense report is submitted in SAP Concur, validates the amount against policy limits and routes for manager approval via Microsoft Teams.

naftiko: '0.5'
info:
  label: SAP Concur Expense Report Approval
  description: When an expense report is submitted in SAP Concur, validates the amount against policy limits and routes for manager approval via Microsoft Teams.
  tags:
  - finance
  - expense-management
  - sap-concur
  - microsoft-teams
  - approval
capability:
  exposes:
  - type: mcp
    namespace: expense-approval
    port: 8080
    tools:
    - name: approve-expense-report
      description: Given an SAP Concur expense report ID, validate the total against company policy and send an approval request card to the submitter's manager in Teams.
      inputParameters:
      - name: report_id
        in: body
        type: string
        description: The SAP Concur expense report ID.
      - name: manager_email
        in: body
        type: string
        description: Email address of the approving manager.
      steps:
      - name: get-report
        type: call
        call: concur.get-expense-report
        with:
          reportId: '{{report_id}}'
      - name: send-approval
        type: call
        call: msteams.post-message
        with:
          recipient: '{{manager_email}}'
          message: 'Expense approval needed: Report {{report_id}} for {{get-report.Total}} {{get-report.CurrencyCode}} submitted by {{get-report.OwnerName}}.'
  consumes:
  - type: http
    namespace: concur
    baseUri: https://www.concursolutions.com/api/v3.0
    authentication:
      type: bearer
      token: $secrets.concur_token
    resources:
    - name: expense-reports
      path: /expense/reports/{{reportId}}
      inputParameters:
      - name: reportId
        in: path
      operations:
      - name: get-expense-report
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /chats/messages
      operations:
      - name: post-message
        method: POST

Retrieves a list of Okta users with privileged application assignments for a quarterly access review and posts the report to SharePoint.

naftiko: '0.5'
info:
  label: Okta User Access Review
  description: Retrieves a list of Okta users with privileged application assignments for a quarterly access review and posts the report to SharePoint.
  tags:
  - identity
  - security
  - okta
  - sharepoint
  - access-management
capability:
  exposes:
  - type: mcp
    namespace: identity-ops
    port: 8080
    tools:
    - name: run-access-review
      description: Given an Okta group ID, retrieve all active members and their application assignments, then upload the access review report to SharePoint.
      inputParameters:
      - name: group_id
        in: body
        type: string
        description: The Okta group ID to review.
      - name: sharepoint_site_id
        in: body
        type: string
        description: The SharePoint site ID where the report should be uploaded.
      steps:
      - name: get-group-members
        type: call
        call: okta.get-group-members
        with:
          groupId: '{{group_id}}'
      - name: upload-report
        type: call
        call: sharepoint.create-file
        with:
          siteId: '{{sharepoint_site_id}}'
          fileName: access-review-{{group_id}}.json
          content: '{{get-group-members.members}}'
  consumes:
  - type: http
    namespace: okta
    baseUri: https://colgate-palmolive.okta.com/api/v1
    authentication:
      type: apikey
      key: Authorization
      value: $secrets.okta_api_token
      placement: header
    resources:
    - name: group-members
      path: /groups/{{groupId}}/users
      inputParameters:
      - name: groupId
        in: path
      operations:
      - name: get-group-members
        method: GET
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /sites/{{siteId}}/drive/root/children
      inputParameters:
      - name: siteId
        in: path
      operations:
      - name: create-file
        method: POST

Checks the status of Snowflake data pipelines and tasks, surfaces any failures, and creates ServiceNow incidents for failed jobs requiring manual intervention.

naftiko: '0.5'
info:
  label: Snowflake Data Pipeline Health Monitor
  description: Checks the status of Snowflake data pipelines and tasks, surfaces any failures, and creates ServiceNow incidents for failed jobs requiring manual intervention.
  tags:
  - data
  - analytics
  - snowflake
  - servicenow
  - monitoring
capability:
  exposes:
  - type: mcp
    namespace: data-ops
    port: 8080
    tools:
    - name: check-pipeline-health
      description: Given a Snowflake task name, retrieve task execution history, identify failures, and open a ServiceNow incident if the failure count exceeds threshold.
      inputParameters:
      - name: task_name
        in: body
        type: string
        description: The Snowflake task name to check.
      - name: failure_threshold
        in: body
        type: integer
        description: Number of consecutive failures before opening an incident.
      steps:
      - name: get-task-history
        type: call
        call: snowflake.get-task-history
        with:
          taskName: '{{task_name}}'
      - name: open-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Snowflake task failure: {{task_name}}'
          category: data_pipeline
          description: 'Task {{task_name}} has exceeded failure threshold. Last error: {{get-task-history.error_message}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://colgate-palmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: task-history
      path: /databases/tasks/{{taskName}}/executions
      inputParameters:
      - name: taskName
        in: path
      operations:
      - name: get-task-history
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://colgate-palmolive.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.snow_user
      password: $secrets.snow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST

Aggregates demand signals from Salesforce opportunity pipeline and SAP inventory positions to produce a consolidated supply chain outlook report.

naftiko: '0.5'
info:
  label: Supply Chain Demand Signal Aggregator
  description: Aggregates demand signals from Salesforce opportunity pipeline and SAP inventory positions to produce a consolidated supply chain outlook report.
  tags:
  - supply-chain
  - finance
  - salesforce
  - sap
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: supply-chain-reporting
    port: 8080
    tools:
    - name: get-demand-outlook
      description: Given a product family code and planning horizon, retrieve open Salesforce pipeline opportunities and SAP inventory positions to produce a demand vs. supply summary.
      inputParameters:
      - name: product_family
        in: body
        type: string
        description: The Salesforce product family code, e.g. ORAL_CARE.
      - name: horizon_weeks
        in: body
        type: integer
        description: Planning horizon in weeks.
      steps:
      - name: get-pipeline
        type: call
        call: salesforce.get-opportunities-by-product
        with:
          productFamily: '{{product_family}}'
      - name: get-inventory
        type: call
        call: sap-inventory.get-stock-overview
        with:
          productFamily: '{{product_family}}'
      - name: post-outlook
        type: call
        call: msteams.post-channel-message
        with:
          channelId: supply-chain-team
          message: 'Demand outlook for {{product_family}} ({{horizon_weeks}}w): Pipeline={{get-pipeline.totalValue}}, On-hand stock={{get-inventory.totalUnits}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://colgate-palmolive.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: opportunities
      path: /sobjects/Opportunity
      inputParameters:
      - name: productFamily
        in: query
      operations:
      - name: get-opportunities-by-product
        method: GET
  - type: http
    namespace: sap-inventory
    baseUri: https://colgate-palmolive-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: stock
      path: /A_MatlStkInAcctMod
      inputParameters:
      - name: productFamily
        in: query
      operations:
      - name: get-stock-overview
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

Analyzes costing variances between SAP standard and Snowflake actual costs, creating Jira reviews.

naftiko: '0.5'
info:
  label: Product Costing Variance Analyzer
  description: Analyzes costing variances between SAP standard and Snowflake actual costs, creating Jira reviews.
  tags:
  - finance
  - manufacturing
  - sap
  - snowflake
  - jira
capability:
  exposes:
  - type: mcp
    namespace: cost-analytics
    port: 8080
    tools:
    - name: analyze-variance
      description: Analyze product costing variances.
      inputParameters:
      - name: material_number
        type: string
        description: Material number.
      - name: period
        type: string
        description: Period.
      steps:
      - name: get-standard
        type: call
        call: sap.get-cost
        with:
          material: '{{material_number}}'
      - name: get-actual
        type: call
        call: snowflake.execute-query
        with:
          warehouse: FINANCE_WH
          query: SELECT actual_cost FROM costs WHERE material='{{material_number}}'
      - name: create-review
        type: call
        call: jira.create-issue
        with:
          project_key: FIN
          summary: 'Variance: {{material_number}} ({{period}})'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_PRODUCT_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-cost
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: jira
    baseUri: https://colgatepalmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST

Tracks GMP training compliance by pulling Workday certifications, checking overdue trainings in Snowflake, and creating ServiceNow remediation tasks.

naftiko: '0.5'
info:
  label: GMP Training Compliance Tracker
  description: Tracks GMP training compliance by pulling Workday certifications, checking overdue trainings in Snowflake, and creating ServiceNow remediation tasks.
  tags:
  - quality
  - manufacturing
  - workday
  - snowflake
  - servicenow
capability:
  exposes:
  - type: mcp
    namespace: gmp-compliance
    port: 8080
    tools:
    - name: track-gmp-compliance
      description: Track GMP training compliance across the workforce.
      inputParameters:
      - name: plant_code
        type: string
        description: Plant code.
      - name: department
        type: string
        description: Department name.
      steps:
      - name: get-certifications
        type: call
        call: workday.get-certifications
        with:
          plant: '{{plant_code}}'
          department: '{{department}}'
      - name: check-overdue
        type: call
        call: snowflake.execute-query
        with:
          warehouse: HR_WH
          query: SELECT employee_id, training, days_overdue FROM gmp_compliance WHERE plant='{{plant_code}}' AND overdue=true
      - name: create-remediation
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'GMP training overdue: {{plant_code}} {{department}}'
          description: '{{check-overdue.count}} employees with overdue GMP training'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: certifications
      path: /colgatepalmolive/certifications
      operations:
      - name: get-certifications
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: servicenow
    baseUri: https://colgatepalmolive.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST

Generates supplier scorecards from Ariba delivery data, Snowflake quality metrics, and posts to Teams.

naftiko: '0.5'
info:
  label: Supplier Performance Scorecard Generator
  description: Generates supplier scorecards from Ariba delivery data, Snowflake quality metrics, and posts to Teams.
  tags:
  - procurement
  - supply-chain
  - sap
  - snowflake
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: procurement-analytics
    port: 8080
    tools:
    - name: generate-scorecard
      description: Generate supplier performance scorecard.
      inputParameters:
      - name: supplier_id
        type: string
        description: Ariba supplier ID.
      - name: period
        type: string
        description: Period.
      steps:
      - name: get-delivery
        type: call
        call: ariba.get-performance
        with:
          supplier_id: '{{supplier_id}}'
          period: '{{period}}'
      - name: get-quality
        type: call
        call: snowflake.execute-query
        with:
          warehouse: PROCUREMENT_WH
          query: SELECT defect_rate FROM supplier_quality WHERE supplier='{{supplier_id}}'
      - name: post
        type: call
        call: msteams.send-message
        with:
          channel_id: procurement
          text: 'Supplier {{supplier_id}}: OTD {{get-delivery.on_time_rate}}%'
  consumes:
  - type: http
    namespace: ariba
    baseUri: https://openapi.ariba.com/api/supplier-management/v1
    authentication:
      type: bearer
      token: $secrets.ariba_token
    resources:
    - name: suppliers
      path: /suppliers
      operations:
      - name: get-supplier
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /teams/channels/messages
      operations:
      - name: send-message
        method: POST

Queries Snowflake for retail POS analytics including velocity, distribution, and share data.

naftiko: '0.5'
info:
  label: Snowflake Retail POS Analytics Query
  description: Queries Snowflake for retail POS analytics including velocity, distribution, and share data.
  tags:
  - analytics
  - sales
  - snowflake
  - retail
capability:
  exposes:
  - type: mcp
    namespace: retail-analytics
    port: 8080
    tools:
    - name: query-pos-data
      description: Query Snowflake retail POS data for a category and retailer.
      inputParameters:
      - name: category
        type: string
        description: Product category.
      - name: retailer
        type: string
        description: Retail account.
      - name: date_from
        type: string
        description: Start date.
      call: snowflake.execute-query
      with:
        warehouse: RETAIL_ANALYTICS_WH
        query: SELECT * FROM pos WHERE category='{{category}}'
      outputParameters:
      - name: data
        type: string
        mapping: $.data
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST

Retrieves actual spending for a cost center from SAP for a fiscal period.

naftiko: '0.5'
info:
  label: SAP Cost Center Actuals Lookup
  description: Retrieves actual spending for a cost center from SAP for a fiscal period.
  tags:
  - finance
  - operations
  - sap
  - erp
capability:
  exposes:
  - type: mcp
    namespace: finance-reporting
    port: 8080
    tools:
    - name: get-actuals
      description: Look up cost center actuals in SAP.
      inputParameters:
      - name: cost_center
        type: string
        description: SAP cost center ID.
      - name: period
        type: string
        description: Fiscal period.
      call: sap.get-actuals
      with:
        cost_center: '{{cost_center}}'
        period: '{{period}}'
      outputParameters:
      - name: total
        type: string
        mapping: $.d.TotalAmount
      - name: currency
        type: string
        mapping: $.d.Currency
  consumes:
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_OPLACCTGDOCITEMCUBE_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-actuals
        method: GET

Audits planogram compliance from Salesforce visits, Snowflake metrics, and Jira follow-ups.

naftiko: '0.5'
info:
  label: Retail Planogram Compliance Audit
  description: Audits planogram compliance from Salesforce visits, Snowflake metrics, and Jira follow-ups.
  tags:
  - sales
  - retail
  - salesforce
  - snowflake
  - jira
capability:
  exposes:
  - type: mcp
    namespace: retail-compliance
    port: 8080
    tools:
    - name: audit-planogram
      description: Audit planogram compliance.
      inputParameters:
      - name: region
        type: string
        description: Region.
      - name: audit_week
        type: string
        description: Audit week.
      steps:
      - name: get-visits
        type: call
        call: salesforce.get-visits
        with:
          region: '{{region}}'
      - name: get-compliance
        type: call
        call: snowflake.execute-query
        with:
          warehouse: RETAIL_WH
          query: SELECT score FROM planogram WHERE region='{{region}}'
      - name: create-followup
        type: call
        call: jira.create-issue
        with:
          project_key: RETAIL
          summary: 'Planogram: {{region}} week {{audit_week}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://colgatepalmolive.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: sobjects
      path: /sobjects
      operations:
      - name: query
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: jira
    baseUri: https://colgatepalmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST

Orchestrates shelf audits from Salesforce data, Snowflake compliance, and Jira follow-ups.

naftiko: '0.5'
info:
  label: Retail Shelf Audit Orchestrator
  description: Orchestrates shelf audits from Salesforce data, Snowflake compliance, and Jira follow-ups.
  tags:
  - sales
  - retail
  - salesforce
  - snowflake
  - jira
capability:
  exposes:
  - type: mcp
    namespace: retail-ops
    port: 8080
    tools:
    - name: run-audit
      description: Orchestrate retail shelf audit.
      inputParameters:
      - name: account_id
        type: string
        description: Salesforce account ID.
      - name: audit_period
        type: string
        description: Period.
      steps:
      - name: get-account
        type: call
        call: salesforce.get-account
        with:
          account_id: '{{account_id}}'
      - name: get-compliance
        type: call
        call: snowflake.execute-query
        with:
          warehouse: RETAIL_WH
          query: SELECT score FROM audit WHERE account='{{account_id}}'
      - name: create-followup
        type: call
        call: jira.create-issue
        with:
          project_key: RETAIL
          summary: 'Audit: {{get-account.name}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://colgatepalmolive.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: sobjects
      path: /sobjects
      operations:
      - name: query
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: jira
    baseUri: https://colgatepalmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST

Monitors product shelf life by checking SAP batch expiry dates, identifying at-risk inventory in Snowflake, and alerting supply chain via Teams.

naftiko: '0.5'
info:
  label: Product Shelf Life Monitoring
  description: Monitors product shelf life by checking SAP batch expiry dates, identifying at-risk inventory in Snowflake, and alerting supply chain via Teams.
  tags:
  - quality
  - supply-chain
  - sap
  - snowflake
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: shelf-life
    port: 8080
    tools:
    - name: monitor-shelf-life
      description: Monitor product shelf life and alert on expiring inventory.
      inputParameters:
      - name: plant_code
        type: string
        description: SAP plant code.
      - name: days_threshold
        type: number
        description: Days until expiry threshold.
      steps:
      - name: get-expiring
        type: call
        call: sap.get-expiring-batches
        with:
          plant: '{{plant_code}}'
          threshold: '{{days_threshold}}'
      - name: get-inventory-value
        type: call
        call: snowflake.execute-query
        with:
          warehouse: SC_WH
          query: SELECT sum(value) FROM inventory WHERE plant='{{plant_code}}' AND days_to_expiry<={{days_threshold}}
      - name: alert-team
        type: call
        call: msteams.send-message
        with:
          channel_id: supply-chain
          text: 'Shelf life alert: {{get-expiring.count}} batches expiring within {{days_threshold}} days at {{plant_code}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_BATCH_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: batches
      path: /data
      operations:
      - name: get-expiring-batches
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /teams/channels/messages
      operations:
      - name: send-message
        method: POST

When a purchase requisition is submitted in SAP Ariba, validates budget availability in SAP S/4HANA and routes the approval to the appropriate manager via Microsoft Teams.

naftiko: '0.5'
info:
  label: SAP Ariba Requisition Approval
  description: When a purchase requisition is submitted in SAP Ariba, validates budget availability in SAP S/4HANA and routes the approval to the appropriate manager via Microsoft Teams.
  tags:
  - procurement
  - finance
  - sap-ariba
  - sap
  - microsoft-teams
  - approval
capability:
  exposes:
  - type: mcp
    namespace: procurement-approval
    port: 8080
    tools:
    - name: approve-requisition
      description: Given an Ariba requisition ID, check budget in SAP S/4HANA and send an approval card to the responsible manager in Microsoft Teams.
      inputParameters:
      - name: requisition_id
        in: body
        type: string
        description: The SAP Ariba requisition ID.
      - name: manager_email
        in: body
        type: string
        description: The Microsoft Teams UPN of the approving manager.
      steps:
      - name: get-requisition
        type: call
        call: ariba.get-requisition
        with:
          requisitionId: '{{requisition_id}}'
      - name: check-budget
        type: call
        call: sap-finance.check-budget
        with:
          cost_center: '{{get-requisition.costCenter}}'
          amount: '{{get-requisition.totalAmount}}'
      - name: send-approval-card
        type: call
        call: msteams.post-message
        with:
          recipient: '{{manager_email}}'
          message: 'Approval needed: Requisition {{requisition_id}} for {{get-requisition.totalAmount}} {{get-requisition.currency}}. Budget status: {{check-budget.status}}.'
  consumes:
  - type: http
    namespace: ariba
    baseUri: https://openapi.ariba.com/api/purchase-requisitions/v1
    authentication:
      type: bearer
      token: $secrets.ariba_token
    resources:
    - name: requisitions
      path: /requisitions/{{requisitionId}}
      inputParameters:
      - name: requisitionId
        in: path
      operations:
      - name: get-requisition
        method: GET
  - type: http
    namespace: sap-finance
    baseUri: https://colgate-palmolive-s4.sap.com/sap/opu/odata/sap/API_COSTCENTER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: budgets
      path: /A_CostCenter('{{cost_center}}')
      inputParameters:
      - name: cost_center
        in: path
      operations:
      - name: check-budget
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /chats/messages
      operations:
      - name: post-message
        method: POST

Handles releases by checking Azure DevOps pipeline, ServiceNow change, and notifying Teams.

naftiko: '0.5'
info:
  label: Azure DevOps Release Approval Handler
  description: Handles releases by checking Azure DevOps pipeline, ServiceNow change, and notifying Teams.
  tags:
  - operations
  - devops
  - azure-devops
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: release-mgmt
    port: 8080
    tools:
    - name: handle-release
      description: Handle release approval.
      inputParameters:
      - name: pipeline_id
        type: string
        description: Pipeline ID.
      - name: change_request
        type: string
        description: Change request.
      steps:
      - name: get-pipeline
        type: call
        call: azuredevops.get-run
        with:
          pipeline_id: '{{pipeline_id}}'
      - name: validate
        type: call
        call: servicenow.get-change
        with:
          number: '{{change_request}}'
      - name: notify
        type: call
        call: msteams.send-message
        with:
          channel_id: releases
          text: 'Release: Pipeline {{pipeline_id}} ({{get-pipeline.status}})'
  consumes:
  - type: http
    namespace: azuredevops
    baseUri: https://dev.azure.com/colgatepalmolive
    authentication:
      type: bearer
      token: $secrets.azure_devops_token
    resources:
    - name: pipelines
      path: /_apis/pipelines
      operations:
      - name: get-run
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://colgatepalmolive.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /teams/channels/messages
      operations:
      - name: send-message
        method: POST

Analyzes consumer reviews from Snowflake, creates Jira tasks, and posts summary to Teams.

naftiko: '0.5'
info:
  label: Consumer Review Analysis Pipeline
  description: Analyzes consumer reviews from Snowflake, creates Jira tasks, and posts summary to Teams.
  tags:
  - marketing
  - quality
  - snowflake
  - jira
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: consumer-insights
    port: 8080
    tools:
    - name: analyze-reviews
      description: Analyze consumer reviews for complaint trends.
      inputParameters:
      - name: product_line
        type: string
        description: Product line.
      - name: period_days
        type: number
        description: Lookback days.
      steps:
      - name: get-reviews
        type: call
        call: snowflake.execute-query
        with:
          warehouse: CONSUMER_WH
          query: SELECT topic, count FROM reviews WHERE product='{{product_line}}'
      - name: create-task
        type: call
        call: jira.create-issue
        with:
          project_key: PROD
          summary: 'Reviews: {{product_line}}'
      - name: post
        type: call
        call: msteams.send-message
        with:
          channel_id: insights
          text: Review analysis for {{product_line}} complete
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: jira
    baseUri: https://colgatepalmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /teams/channels/messages
      operations:
      - name: send-message
        method: POST

On a GitHub Actions workflow failure on a protected branch, creates a Jira bug, posts a failure summary to the engineering Teams channel, and logs the incident in Datadog.

naftiko: '0.5'
info:
  label: GitHub CI/CD Pipeline Failure Handler
  description: On a GitHub Actions workflow failure on a protected branch, creates a Jira bug, posts a failure summary to the engineering Teams channel, and logs the incident in Datadog.
  tags:
  - devops
  - cicd
  - github
  - jira
  - datadog
  - incident-response
capability:
  exposes:
  - type: mcp
    namespace: devops-cicd
    port: 8080
    tools:
    - name: handle-pipeline-failure
      description: Given a GitHub Actions workflow failure event, create a Jira bug, log a Datadog event, and alert the engineering Teams channel with full context.
      inputParameters:
      - name: repo
        in: body
        type: string
        description: The GitHub repository name in owner/repo format.
      - name: workflow_name
        in: body
        type: string
        description: The name of the failed GitHub Actions workflow.
      - name: branch
        in: body
        type: string
        description: The branch on which the failure occurred.
      - name: run_id
        in: body
        type: string
        description: The GitHub Actions workflow run ID.
      steps:
      - name: get-run-details
        type: call
        call: github.get-workflow-run
        with:
          repo: '{{repo}}'
          run_id: '{{run_id}}'
      - name: create-jira-bug
        type: call
        call: jira.create-issue
        with:
          projectKey: ENG
          issuetype: Bug
          summary: '[CI Failure] {{repo}} / {{branch}} — {{workflow_name}}'
          description: 'Run: {{run_id}}

            Branch: {{branch}}

            Conclusion: {{get-run-details.conclusion}}'
      - name: log-datadog-event
        type: call
        call: datadog.create-event
        with:
          title: 'CI Failure: {{repo}} {{workflow_name}}'
          text: 'Branch: {{branch}}, Run: {{run_id}}'
          alert_type: error
      - name: alert-team
        type: call
        call: msteams.post-channel-message
        with:
          channelId: engineering-alerts
          message: 'CI Failure: {{repo}} | Branch: {{branch}} | Workflow: {{workflow_name}} | Jira: {{create-jira-bug.key}}'
  consumes:
  - type: http
    namespace: github
    baseUri: https://api.github.com
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: workflow-runs
      path: /repos/{{repo}}/actions/runs/{{run_id}}
      inputParameters:
      - name: repo
        in: path
      - name: run_id
        in: path
      operations:
      - name: get-workflow-run
        method: GET
  - type: http
    namespace: jira
    baseUri: https://colgate-palmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: datadog
    baseUri: https://api.datadoghq.com/api/v1
    authentication:
      type: apikey
      key: DD-API-KEY
      value: $secrets.datadog_api_key
      placement: header
    resources:
    - name: events
      path: /events
      operations:
      - name: create-event
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

Generates TPE by pulling Salesforce promotions, Snowflake sales, and refreshing Power BI.

naftiko: '0.5'
info:
  label: Trade Promotion Effectiveness Report
  description: Generates TPE by pulling Salesforce promotions, Snowflake sales, and refreshing Power BI.
  tags:
  - sales
  - marketing
  - salesforce
  - snowflake
  - power-bi
capability:
  exposes:
  - type: mcp
    namespace: trade-analytics
    port: 8080
    tools:
    - name: generate-tpe
      description: Generate trade promotion effectiveness report.
      inputParameters:
      - name: promotion_id
        type: string
        description: Salesforce promotion ID.
      - name: date_from
        type: string
        description: Start date.
      - name: date_to
        type: string
        description: End date.
      steps:
      - name: get-promo
        type: call
        call: salesforce.get-promotion
        with:
          promotion_id: '{{promotion_id}}'
      - name: get-sales
        type: call
        call: snowflake.execute-query
        with:
          warehouse: SALES_WH
          query: SELECT revenue FROM pos WHERE promo='{{promotion_id}}'
      - name: refresh
        type: call
        call: powerbi.refresh-dataset
        with:
          datasetId: trade-promotion-effectiveness
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://colgatepalmolive.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: sobjects
      path: /sobjects
      operations:
      - name: query
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets
      operations:
      - name: refresh-dataset
        method: POST

Tracks fulfillment from Salesforce order, SAP picking, and updates ServiceNow customer ticket.

naftiko: '0.5'
info:
  label: E-commerce Order Fulfillment Tracker
  description: Tracks fulfillment from Salesforce order, SAP picking, and updates ServiceNow customer ticket.
  tags:
  - ecommerce
  - supply-chain
  - salesforce
  - sap
  - servicenow
capability:
  exposes:
  - type: mcp
    namespace: ecom-fulfillment
    port: 8080
    tools:
    - name: track-fulfillment
      description: Track e-commerce order fulfillment.
      inputParameters:
      - name: order_id
        type: string
        description: Salesforce order ID.
      - name: ticket_id
        type: string
        description: ServiceNow ticket.
      steps:
      - name: get-order
        type: call
        call: salesforce.get-order
        with:
          order_id: '{{order_id}}'
      - name: check-picking
        type: call
        call: sap.get-delivery
        with:
          order: '{{get-order.sap_order}}'
      - name: update-ticket
        type: call
        call: servicenow.update-incident
        with:
          number: '{{ticket_id}}'
          comment: 'Status: {{get-order.status}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://colgatepalmolive.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: sobjects
      path: /sobjects
      operations:
      - name: query
        method: GET
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_OUTBOUND_DELIVERY_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-delivery
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://colgatepalmolive.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST

Retrieves engagement metrics for Colgate-Palmolive's LinkedIn brand campaigns and publishes a weekly performance digest to the marketing Teams channel.

naftiko: '0.5'
info:
  label: LinkedIn Brand Campaign Digest
  description: Retrieves engagement metrics for Colgate-Palmolive's LinkedIn brand campaigns and publishes a weekly performance digest to the marketing Teams channel.
  tags:
  - marketing
  - social
  - linkedin
  - microsoft-teams
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: social-reporting
    port: 8080
    tools:
    - name: digest-linkedin-performance
      description: Given a LinkedIn campaign ID and date range, retrieve engagement metrics and post a performance digest to the marketing Teams channel.
      inputParameters:
      - name: campaign_id
        in: body
        type: string
        description: The LinkedIn campaign ID.
      - name: start_date
        in: body
        type: string
        description: Start date in YYYY-MM-DD format.
      - name: end_date
        in: body
        type: string
        description: End date in YYYY-MM-DD format.
      steps:
      - name: get-campaign-stats
        type: call
        call: linkedin.get-campaign-analytics
        with:
          campaignId: '{{campaign_id}}'
          startDate: '{{start_date}}'
          endDate: '{{end_date}}'
      - name: post-digest
        type: call
        call: msteams.post-channel-message
        with:
          channelId: marketing-team
          message: 'LinkedIn Campaign {{campaign_id}} ({{start_date}} to {{end_date}}): Impressions={{get-campaign-stats.impressions}}, Clicks={{get-campaign-stats.clicks}}, Engagement={{get-campaign-stats.engagementRate}}'
  consumes:
  - type: http
    namespace: linkedin
    baseUri: https://api.linkedin.com/v2
    authentication:
      type: bearer
      token: $secrets.linkedin_token
    resources:
    - name: campaign-analytics
      path: /adAnalytics
      inputParameters:
      - name: campaignId
        in: query
      - name: startDate
        in: query
      - name: endDate
        in: query
      operations:
      - name: get-campaign-analytics
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

Creates a standard ServiceNow change request for planned maintenance, associates it with affected CI records, and sends pre-change notifications via Microsoft Teams.

naftiko: '0.5'
info:
  label: ServiceNow Change Request Automation
  description: Creates a standard ServiceNow change request for planned maintenance, associates it with affected CI records, and sends pre-change notifications via Microsoft Teams.
  tags:
  - itsm
  - change-management
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: change-management
    port: 8080
    tools:
    - name: open-change-request
      description: Given a change description, affected configuration items, and planned window, create a ServiceNow standard change request and notify stakeholders in Teams.
      inputParameters:
      - name: change_description
        in: body
        type: string
        description: Description of the planned change.
      - name: affected_ci
        in: body
        type: string
        description: Comma-separated list of affected configuration item names.
      - name: planned_start
        in: body
        type: string
        description: Planned change start datetime in ISO 8601 format.
      - name: planned_end
        in: body
        type: string
        description: Planned change end datetime in ISO 8601 format.
      steps:
      - name: create-change
        type: call
        call: servicenow.create-change
        with:
          short_description: '{{change_description}}'
          type: standard
          start_date: '{{planned_start}}'
          end_date: '{{planned_end}}'
          cmdb_ci: '{{affected_ci}}'
      - name: notify-stakeholders
        type: call
        call: msteams.post-channel-message
        with:
          channelId: it-operations
          message: 'Change request {{create-change.number}} opened: {{change_description}} | Window: {{planned_start}} to {{planned_end}} | CIs: {{affected_ci}}'
  consumes:
  - type: http
    namespace: servicenow
    baseUri: https://colgate-palmolive.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.snow_user
      password: $secrets.snow_password
    resources:
    - name: change-requests
      path: /table/change_request
      operations:
      - name: create-change
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

Analyzes warehouse capacity from SAP, demand from Snowflake, and refreshes Power BI dashboard.

naftiko: '0.5'
info:
  label: Warehouse Capacity Planning Orchestrator
  description: Analyzes warehouse capacity from SAP, demand from Snowflake, and refreshes Power BI dashboard.
  tags:
  - supply-chain
  - logistics
  - sap
  - snowflake
  - power-bi
capability:
  exposes:
  - type: mcp
    namespace: warehouse-planning
    port: 8080
    tools:
    - name: plan-capacity
      description: Analyze warehouse capacity.
      inputParameters:
      - name: warehouse_id
        type: string
        description: Warehouse number.
      - name: weeks
        type: number
        description: Forecast weeks.
      steps:
      - name: get-util
        type: call
        call: sap.get-warehouse-stock
        with:
          warehouse: '{{warehouse_id}}'
      - name: get-forecast
        type: call
        call: snowflake.execute-query
        with:
          warehouse: SC_WH
          query: SELECT pallets FROM forecast WHERE id='{{warehouse_id}}'
      - name: refresh
        type: call
        call: powerbi.refresh-dataset
        with:
          datasetId: warehouse-capacity
  consumes:
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_WAREHOUSE_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-warehouse-stock
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: powerbi
    baseUri: https://api.powerbi.com/v1.0/myorg
    authentication:
      type: bearer
      token: $secrets.powerbi_token
    resources:
    - name: datasets
      path: /datasets
      operations:
      - name: refresh-dataset
        method: POST

Initiates CM audit from Ariba supplier data, Jira tasks, and SharePoint checklists.

naftiko: '0.5'
info:
  label: Contract Manufacturer Quality Audit
  description: Initiates CM audit from Ariba supplier data, Jira tasks, and SharePoint checklists.
  tags:
  - quality
  - procurement
  - sap
  - jira
  - sharepoint
capability:
  exposes:
  - type: mcp
    namespace: quality-audit
    port: 8080
    tools:
    - name: initiate-audit
      description: Start contract manufacturer quality audit.
      inputParameters:
      - name: supplier_id
        type: string
        description: Supplier ID.
      - name: audit_type
        type: string
        description: Audit type.
      steps:
      - name: get-supplier
        type: call
        call: ariba.get-supplier
        with:
          supplier_id: '{{supplier_id}}'
      - name: create-task
        type: call
        call: jira.create-issue
        with:
          project_key: QAUDIT
          summary: 'CM Audit: {{get-supplier.name}}'
      - name: share-checklist
        type: call
        call: sharepoint.copy-template
        with:
          template: audit-{{audit_type}}
          destination: audits/{{supplier_id}}
  consumes:
  - type: http
    namespace: ariba
    baseUri: https://openapi.ariba.com/api/supplier-management/v1
    authentication:
      type: bearer
      token: $secrets.ariba_token
    resources:
    - name: suppliers
      path: /suppliers
      operations:
      - name: get-supplier
        method: GET
  - type: http
    namespace: jira
    baseUri: https://colgatepalmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /sites/drive/items
      operations:
      - name: search-docs
        method: GET

Returns the current paid time off and vacation accrual balances for an employee from Workday, for use in absence planning and manager approvals.

naftiko: '0.5'
info:
  label: Workday Time-Off Balance Lookup
  description: Returns the current paid time off and vacation accrual balances for an employee from Workday, for use in absence planning and manager approvals.
  tags:
  - hr
  - workday
  - absence-management
capability:
  exposes:
  - type: mcp
    namespace: hr-absence
    port: 8080
    tools:
    - name: get-time-off-balance
      description: Given a Workday employee ID, return current accrued vacation, PTO, and sick leave balances. Use when an employee or manager needs to verify available time-off before approving a request.
      inputParameters:
      - name: employee_id
        in: body
        type: string
        description: The Workday worker ID.
      call: workday.get-leave-balance
      with:
        worker_id: '{{employee_id}}'
      outputParameters:
      - name: vacation_days
        type: number
        mapping: $.leaveBalances.vacation
      - name: pto_days
        type: number
        mapping: $.leaveBalances.pto
      - name: sick_days
        type: number
        mapping: $.leaveBalances.sick
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: leave-balances
      path: /colgate-palmolive/workers/{{worker_id}}/leaveBalance
      inputParameters:
      - name: worker_id
        in: path
      operations:
      - name: get-leave-balance
        method: GET

Retrieves headcount data from Workday by department including active employees and open positions.

naftiko: '0.5'
info:
  label: Workday Headcount Report Lookup
  description: Retrieves headcount data from Workday by department including active employees and open positions.
  tags:
  - hr
  - workforce
  - workday
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: hr-reporting
    port: 8080
    tools:
    - name: get-headcount
      description: Get headcount report from Workday by department.
      inputParameters:
      - name: department
        type: string
        description: Department name.
      call: workday.get-headcount
      with:
        department: '{{department}}'
      outputParameters:
      - name: active_count
        type: string
        mapping: $.headcount.active
      - name: open_positions
        type: string
        mapping: $.headcount.open
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /colgatepalmolive/workers
      operations:
      - name: get-worker
        method: GET

Traces affected batch in SAP, creates ServiceNow incident, and alerts quality team via Teams.

naftiko: '0.5'
info:
  label: Product Recall Investigation Orchestrator
  description: Traces affected batch in SAP, creates ServiceNow incident, and alerts quality team via Teams.
  tags:
  - quality
  - supply-chain
  - sap
  - servicenow
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: quality-ops
    port: 8080
    tools:
    - name: investigate-recall
      description: Orchestrate product recall investigation.
      inputParameters:
      - name: batch_number
        type: string
        description: Batch number.
      - name: material_number
        type: string
        description: Material number.
      - name: severity
        type: string
        description: Severity level.
      steps:
      - name: trace-batch
        type: call
        call: sap.get-batch-details
        with:
          batch: '{{batch_number}}'
          material: '{{material_number}}'
      - name: create-incident
        type: call
        call: servicenow.create-incident
        with:
          short_description: 'Recall: batch {{batch_number}}'
          urgency: '{{severity}}'
      - name: notify-team
        type: call
        call: msteams.send-message
        with:
          channel_id: quality-alerts
          text: 'RECALL: Batch {{batch_number}}. Incident: {{create-incident.number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_BATCH_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-batch-details
        method: GET
  - type: http
    namespace: servicenow
    baseUri: https://colgatepalmolive.service-now.com/api/now
    authentication:
      type: basic
      username: $secrets.servicenow_user
      password: $secrets.servicenow_password
    resources:
    - name: incidents
      path: /table/incident
      operations:
      - name: create-incident
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /teams/channels/messages
      operations:
      - name: send-message
        method: POST

Generates maintenance reports from SAP orders, Snowflake equipment history, and posts to Teams.

naftiko: '0.5'
info:
  label: Plant Maintenance Schedule Report
  description: Generates maintenance reports from SAP orders, Snowflake equipment history, and posts to Teams.
  tags:
  - manufacturing
  - operations
  - sap
  - snowflake
  - microsoft-teams
capability:
  exposes:
  - type: mcp
    namespace: maintenance-reporting
    port: 8080
    tools:
    - name: gen-schedule
      description: Generate maintenance schedule report.
      inputParameters:
      - name: plant_code
        type: string
        description: Plant code.
      - name: weeks
        type: number
        description: Weeks ahead.
      steps:
      - name: get-orders
        type: call
        call: sap.get-orders
        with:
          plant: '{{plant_code}}'
      - name: get-history
        type: call
        call: snowflake.execute-query
        with:
          warehouse: MFG_WH
          query: SELECT mtbf FROM equipment WHERE plant='{{plant_code}}'
      - name: post
        type: call
        call: msteams.send-message
        with:
          channel_id: maintenance
          text: 'Maintenance for {{plant_code}}: {{get-orders.count}} orders'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_MAINTENANCEORDER_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-orders
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: messages
      path: /teams/channels/messages
      operations:
      - name: send-message
        method: POST

Enriches talent pipeline from Workday requisitions, LinkedIn data, and Jira sourcing tasks.

naftiko: '0.5'
info:
  label: LinkedIn Talent Pipeline Enrichment
  description: Enriches talent pipeline from Workday requisitions, LinkedIn data, and Jira sourcing tasks.
  tags:
  - hr
  - recruiting
  - workday
  - linkedin
  - jira
capability:
  exposes:
  - type: mcp
    namespace: talent-acquisition
    port: 8080
    tools:
    - name: enrich-pipeline
      description: Enrich talent pipeline.
      inputParameters:
      - name: department
        type: string
        description: Department.
      steps:
      - name: get-reqs
        type: call
        call: workday.get-positions
        with:
          department: '{{department}}'
      - name: create-tasks
        type: call
        call: jira.create-issue
        with:
          project_key: RECRUIT
          summary: 'Sourcing: {{department}}'
  consumes:
  - type: http
    namespace: workday
    baseUri: https://wd2-impl-services1.workday.com/ccx/api/v1
    authentication:
      type: bearer
      token: $secrets.workday_token
    resources:
    - name: workers
      path: /colgatepalmolive/workers
      operations:
      - name: get-worker
        method: GET
  - type: http
    namespace: jira
    baseUri: https://colgatepalmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST

Syncs demand forecasts from Snowflake with SAP inventory and creates planned production orders.

naftiko: '0.5'
info:
  label: Demand Forecast to Production Sync
  description: Syncs demand forecasts from Snowflake with SAP inventory and creates planned production orders.
  tags:
  - supply-chain
  - manufacturing
  - snowflake
  - sap
  - planning
capability:
  exposes:
  - type: mcp
    namespace: demand-planning
    port: 8080
    tools:
    - name: sync-demand
      description: Synchronize demand forecasts with production planning.
      inputParameters:
      - name: category
        type: string
        description: Product category.
      - name: plant_code
        type: string
        description: Plant code.
      - name: weeks
        type: number
        description: Planning weeks.
      steps:
      - name: get-forecast
        type: call
        call: snowflake.execute-query
        with:
          warehouse: DEMAND_WH
          query: SELECT sku, units FROM forecast WHERE category='{{category}}'
      - name: check-stock
        type: call
        call: sap.get-stock
        with:
          plant: '{{plant_code}}'
          category: '{{category}}'
      - name: create-orders
        type: call
        call: sap.create-planned-order
        with:
          plant: '{{plant_code}}'
          data: '{{get-forecast.data}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-stock
        method: GET
      - name: create-planned-order
        method: POST

Checks Azure AD group memberships for a user to validate access rights.

naftiko: '0.5'
info:
  label: Azure AD User Group Membership Check
  description: Checks Azure AD group memberships for a user to validate access rights.
  tags:
  - security
  - identity
  - azure-active-directory
  - access
capability:
  exposes:
  - type: mcp
    namespace: identity
    port: 8080
    tools:
    - name: check-groups
      description: List Azure AD group memberships for access validation.
      inputParameters:
      - name: user_upn
        type: string
        description: User principal name.
      call: azuread.get-member-of
      with:
        upn: '{{user_upn}}'
      outputParameters:
      - name: groups
        type: string
        mapping: $.value
  consumes:
  - type: http
    namespace: azuread
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: member-of
      path: /users/memberOf
      operations:
      - name: get-member-of
        method: GET

Scans GitHub Dependabot alerts for critical vulnerabilities, creates Jira security tickets, and notifies the security team in Microsoft Teams.

naftiko: '0.5'
info:
  label: GitHub Security Vulnerability Triage
  description: Scans GitHub Dependabot alerts for critical vulnerabilities, creates Jira security tickets, and notifies the security team in Microsoft Teams.
  tags:
  - security
  - devops
  - github
  - jira
  - microsoft-teams
  - vulnerability-management
capability:
  exposes:
  - type: mcp
    namespace: security-ops
    port: 8080
    tools:
    - name: triage-vulnerability-alerts
      description: Given a GitHub repository, retrieve critical Dependabot security alerts, create Jira security tickets for each, and post a summary to the security Teams channel.
      inputParameters:
      - name: repo
        in: body
        type: string
        description: GitHub repository in owner/repo format.
      steps:
      - name: get-alerts
        type: call
        call: github.get-dependabot-alerts
        with:
          repo: '{{repo}}'
          severity: critical
      - name: create-security-ticket
        type: call
        call: jira.create-issue
        with:
          projectKey: SEC
          issuetype: Security
          summary: 'Critical vulnerability: {{get-alerts.advisory_summary}}'
          description: 'Package: {{get-alerts.package_name}}

            CVSS: {{get-alerts.cvss_score}}

            Repo: {{repo}}'
      - name: notify-security
        type: call
        call: msteams.post-channel-message
        with:
          channelId: security-team
          message: 'Critical vulnerability in {{repo}}: {{get-alerts.advisory_summary}} | Jira: {{create-security-ticket.key}}'
  consumes:
  - type: http
    namespace: github
    baseUri: https://api.github.com
    authentication:
      type: bearer
      token: $secrets.github_token
    resources:
    - name: dependabot-alerts
      path: /repos/{{repo}}/dependabot/alerts
      inputParameters:
      - name: repo
        in: path
      - name: severity
        in: query
      operations:
      - name: get-dependabot-alerts
        method: GET
  - type: http
    namespace: jira
    baseUri: https://colgate-palmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

At month end, retrieves the SAP S/4HANA period close status for all entities, checks for open items, and posts the close checklist status to the finance Teams channel.

naftiko: '0.5'
info:
  label: SAP Finance Period Close Checklist
  description: At month end, retrieves the SAP S/4HANA period close status for all entities, checks for open items, and posts the close checklist status to the finance Teams channel.
  tags:
  - finance
  - erp
  - sap
  - microsoft-teams
  - period-close
capability:
  exposes:
  - type: mcp
    namespace: finance-close
    port: 8080
    tools:
    - name: check-period-close-status
      description: Given a fiscal year and period, retrieve the SAP period close status for all company codes and post the consolidated status report to the finance Teams channel.
      inputParameters:
      - name: fiscal_year
        in: body
        type: string
        description: The fiscal year, e.g. 2025.
      - name: fiscal_period
        in: body
        type: string
        description: The fiscal period number, e.g. 03 for March.
      steps:
      - name: get-close-status
        type: call
        call: sap-finance.get-period-status
        with:
          fiscalYear: '{{fiscal_year}}'
          fiscalPeriod: '{{fiscal_period}}'
      - name: post-status
        type: call
        call: msteams.post-channel-message
        with:
          channelId: finance-team
          message: 'Period close status FY{{fiscal_year}} P{{fiscal_period}}: Open items={{get-close-status.openItems}}, Blocked postings={{get-close-status.blockedPostings}}'
  consumes:
  - type: http
    namespace: sap-finance
    baseUri: https://colgate-palmolive-s4.sap.com/sap/opu/odata/sap/API_FIGL_PERIOD_LOCK_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: period-status
      path: /A_AccountingPeriodLock
      inputParameters:
      - name: fiscalYear
        in: query
      - name: fiscalPeriod
        in: query
      operations:
      - name: get-period-status
        method: GET
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

Tracks shipments from SAP delivery docs and updates Salesforce orders with tracking info.

naftiko: '0.5'
info:
  label: SAP Transport Shipment Tracker
  description: Tracks shipments from SAP delivery docs and updates Salesforce orders with tracking info.
  tags:
  - supply-chain
  - logistics
  - sap
  - salesforce
capability:
  exposes:
  - type: mcp
    namespace: logistics-tracking
    port: 8080
    tools:
    - name: track-shipment
      description: Track outbound shipment.
      inputParameters:
      - name: delivery_number
        type: string
        description: SAP delivery number.
      - name: sf_order_id
        type: string
        description: Salesforce order ID.
      steps:
      - name: get-delivery
        type: call
        call: sap.get-delivery
        with:
          delivery: '{{delivery_number}}'
      - name: update-order
        type: call
        call: salesforce.update-order
        with:
          order_id: '{{sf_order_id}}'
          tracking: '{{get-delivery.tracking}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_OUTBOUND_DELIVERY_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-delivery
        method: GET
  - type: http
    namespace: salesforce
    baseUri: https://colgatepalmolive.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: sobjects
      path: /sobjects
      operations:
      - name: query
        method: GET

Queries Snowflake for supply chain KPIs including fill rate, OTIF, and inventory turns.

naftiko: '0.5'
info:
  label: Snowflake Supply Chain KPI Query
  description: Queries Snowflake for supply chain KPIs including fill rate, OTIF, and inventory turns.
  tags:
  - supply-chain
  - analytics
  - snowflake
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: sc-analytics
    port: 8080
    tools:
    - name: query-sc-kpis
      description: Query supply chain KPIs from Snowflake.
      inputParameters:
      - name: region
        type: string
        description: Region code.
      - name: period
        type: string
        description: Period.
      call: snowflake.execute-query
      with:
        warehouse: SC_ANALYTICS_WH
        query: SELECT fill_rate, otif FROM sc_kpis WHERE region='{{region}}'
      outputParameters:
      - name: fill_rate
        type: string
        mapping: $.data[0].fill_rate
      - name: otif
        type: string
        mapping: $.data[0].otif
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST

Checks packaging sustainability from SAP BOM, Snowflake compliance data, and creates Jira tasks.

naftiko: '0.5'
info:
  label: Packaging Sustainability Compliance Check
  description: Checks packaging sustainability from SAP BOM, Snowflake compliance data, and creates Jira tasks.
  tags:
  - sustainability
  - quality
  - sap
  - snowflake
  - jira
capability:
  exposes:
  - type: mcp
    namespace: sustainability
    port: 8080
    tools:
    - name: check-packaging
      description: Verify packaging sustainability compliance.
      inputParameters:
      - name: material_number
        type: string
        description: Material number.
      - name: plant_code
        type: string
        description: Plant code.
      steps:
      - name: get-bom
        type: call
        call: sap.get-bom
        with:
          material: '{{material_number}}'
          plant: '{{plant_code}}'
      - name: check
        type: call
        call: snowflake.execute-query
        with:
          warehouse: SUSTAINABILITY_WH
          query: SELECT recyclable_pct FROM packaging WHERE material IN ({{get-bom.components}})
      - name: create-task
        type: call
        call: jira.create-issue
        with:
          project_key: SUSTAIN
          summary: 'Packaging: {{material_number}}'
  consumes:
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_BILL_OF_MATERIAL_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-bom
        method: GET
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: jira
    baseUri: https://colgatepalmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST

Calculates a customer health score from Salesforce case history and product usage data, then updates the account record for proactive retention management.

naftiko: '0.5'
info:
  label: Salesforce Customer Health Score Updater
  description: Calculates a customer health score from Salesforce case history and product usage data, then updates the account record for proactive retention management.
  tags:
  - crm
  - customer-success
  - salesforce
  - reporting
capability:
  exposes:
  - type: mcp
    namespace: customer-success
    port: 8080
    tools:
    - name: update-health-score
      description: Given a Salesforce account ID, retrieve open cases and usage data, compute a health score, and update the account record with the latest score.
      inputParameters:
      - name: account_id
        in: body
        type: string
        description: The Salesforce account record ID.
      steps:
      - name: get-account-cases
        type: call
        call: salesforce.get-account-cases
        with:
          accountId: '{{account_id}}'
      - name: update-account
        type: call
        call: salesforce-update.update-account
        with:
          accountId: '{{account_id}}'
          healthScore: '{{get-account-cases.healthIndicator}}'
  consumes:
  - type: http
    namespace: salesforce
    baseUri: https://colgate-palmolive.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: cases
      path: /sobjects/Account/{{accountId}}/Cases
      inputParameters:
      - name: accountId
        in: path
      operations:
      - name: get-account-cases
        method: GET
  - type: http
    namespace: salesforce-update
    baseUri: https://colgate-palmolive.my.salesforce.com/services/data/v58.0
    authentication:
      type: bearer
      token: $secrets.salesforce_token
    resources:
    - name: accounts
      path: /sobjects/Account/{{accountId}}
      inputParameters:
      - name: accountId
        in: path
      operations:
      - name: update-account
        method: PATCH

Uses Anthropic Claude to summarize product compliance documents stored in SharePoint and posts the summary to the relevant product team channel in Microsoft Teams.

naftiko: '0.5'
info:
  label: Intelligent Document Summarization
  description: Uses Anthropic Claude to summarize product compliance documents stored in SharePoint and posts the summary to the relevant product team channel in Microsoft Teams.
  tags:
  - ai
  - automation
  - anthropic
  - sharepoint
  - microsoft-teams
  - document-management
capability:
  exposes:
  - type: mcp
    namespace: ai-docs
    port: 8080
    tools:
    - name: summarize-compliance-document
      description: Given a SharePoint file path and target Teams channel, retrieve the document content, send it to Claude for summarization, and post the summary to the Teams channel.
      inputParameters:
      - name: site_id
        in: body
        type: string
        description: The SharePoint site ID containing the document.
      - name: file_path
        in: body
        type: string
        description: The relative file path in SharePoint.
      - name: teams_channel_id
        in: body
        type: string
        description: The Teams channel ID to post the summary to.
      steps:
      - name: get-document
        type: call
        call: sharepoint.get-file-content
        with:
          siteId: '{{site_id}}'
          filePath: '{{file_path}}'
      - name: summarize
        type: call
        call: anthropic.create-message
        with:
          model: claude-3-5-sonnet-20241022
          content: 'Summarize this compliance document in 3-5 key bullet points: {{get-document.content}}'
      - name: post-summary
        type: call
        call: msteams.post-channel-message
        with:
          channelId: '{{teams_channel_id}}'
          message: 'Document summary for {{file_path}}:

            {{summarize.content}}'
  consumes:
  - type: http
    namespace: sharepoint
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: files
      path: /sites/{{siteId}}/drive/root:{{filePath}}:/content
      inputParameters:
      - name: siteId
        in: path
      - name: filePath
        in: path
      operations:
      - name: get-file-content
        method: GET
  - type: http
    namespace: anthropic
    baseUri: https://api.anthropic.com/v1
    authentication:
      type: apikey
      key: x-api-key
      value: $secrets.anthropic_api_key
      placement: header
    resources:
    - name: messages
      path: /messages
      operations:
      - name: create-message
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

Coordinates a product launch by publishing content to LinkedIn and retrieving early engagement metrics to share with the brand team in Microsoft Teams.

naftiko: '0.5'
info:
  label: Product Launch Social Media Coordinator
  description: Coordinates a product launch by publishing content to LinkedIn and retrieving early engagement metrics to share with the brand team in Microsoft Teams.
  tags:
  - marketing
  - social
  - linkedin
  - microsoft-teams
  - product-launch
capability:
  exposes:
  - type: mcp
    namespace: product-launch
    port: 8080
    tools:
    - name: publish-launch-content
      description: Given a LinkedIn organization ID and post content, publish the launch post and then retrieve initial engagement metrics, posting the result to the brand Teams channel.
      inputParameters:
      - name: org_id
        in: body
        type: string
        description: The LinkedIn organization ID for Colgate-Palmolive.
      - name: post_content
        in: body
        type: string
        description: The content text for the LinkedIn post.
      steps:
      - name: publish-post
        type: call
        call: linkedin.create-post
        with:
          organizationId: '{{org_id}}'
          text: '{{post_content}}'
      - name: notify-brand-team
        type: call
        call: msteams.post-channel-message
        with:
          channelId: brand-team
          message: 'Product launch post published on LinkedIn. Post ID: {{publish-post.id}}.'
  consumes:
  - type: http
    namespace: linkedin
    baseUri: https://api.linkedin.com/v2
    authentication:
      type: bearer
      token: $secrets.linkedin_token
    resources:
    - name: shares
      path: /ugcPosts
      operations:
      - name: create-post
        method: POST
  - type: http
    namespace: msteams
    baseUri: https://graph.microsoft.com/v1.0
    authentication:
      type: bearer
      token: $secrets.msgraph_token
    resources:
    - name: channel-messages
      path: /teams/channels/{{channelId}}/messages
      inputParameters:
      - name: channelId
        in: path
      operations:
      - name: post-channel-message
        method: POST

Optimizes scheduling from Snowflake demand, SAP capacity, and Jira schedule proposals.

naftiko: '0.5'
info:
  label: Production Scheduling Optimizer
  description: Optimizes scheduling from Snowflake demand, SAP capacity, and Jira schedule proposals.
  tags:
  - manufacturing
  - supply-chain
  - snowflake
  - sap
  - jira
capability:
  exposes:
  - type: mcp
    namespace: production-planning
    port: 8080
    tools:
    - name: optimize-schedule
      description: Optimize production scheduling.
      inputParameters:
      - name: plant_code
        type: string
        description: Plant code.
      - name: period
        type: string
        description: Period.
      steps:
      - name: get-demand
        type: call
        call: snowflake.execute-query
        with:
          warehouse: DEMAND_WH
          query: SELECT sku, units FROM demand WHERE plant='{{plant_code}}'
      - name: get-capacity
        type: call
        call: sap.get-capacity
        with:
          plant: '{{plant_code}}'
      - name: create-schedule
        type: call
        call: jira.create-issue
        with:
          project_key: PROD
          summary: 'Schedule: {{plant_code}} {{period}}'
  consumes:
  - type: http
    namespace: snowflake
    baseUri: https://colgatepalmolive.snowflakecomputing.com/api/v2
    authentication:
      type: bearer
      token: $secrets.snowflake_token
    resources:
    - name: statements
      path: /statements
      operations:
      - name: execute-query
        method: POST
  - type: http
    namespace: sap
    baseUri: https://colgatepalmolive-s4.sap.com/sap/opu/odata/sap/API_PRODUCTION_ORDER_2_SRV
    authentication:
      type: basic
      username: $secrets.sap_user
      password: $secrets.sap_password
    resources:
    - name: resource
      path: /data
      operations:
      - name: get-capacity
        method: GET
  - type: http
    namespace: jira
    baseUri: https://colgatepalmolive.atlassian.net/rest/api/3
    authentication:
      type: basic
      username: $secrets.jira_user
      password: $secrets.jira_api_token
    resources:
    - name: issues
      path: /issue
      operations:
      - name: create-issue
        method: POST