Code Agents: Installation and Configuration

This article walks through installing Quality Clouds Code Agent from the ServiceNow Store and configuring your instance so the agent can connect to Quality Clouds.

Before installing, confirm your instance has:

  • Now Assist license (Pro Plus / Enterprise Plus)
  • Required plugins:
    • Now Assist AI Agents
    • Now Assist for Platform
    • Model Context Protocol Client
    • AI Agents Platform Use Case
  • AI Search active in the instance
  • The Now Assist panel activated
  • The Now Assist panel assistant activated
  • Now Assist in Virtual Agent activated (default)

 

No additional system table permissions are needed.

Configuration steps #

  1. Install the application from the ServiceNow Store.



  2. Generate an API key in the Quality Clouds admin Portal. Follow this article for more information on how to generate it

    1. API KEY Section QC Admin Portal

    2. Add New Key

    3. Fill in the Name, Cloud (ServiceNow), Channel (ServiceNow App), Instance, and Developer

    4. Generate and Copy the Key

  3. Once copied, in ServiceNow, navigate to Integration Hub > Connections & Credentials > Connections, open the QCMCPServer connection, and paste the key into the API Key field. Create a new connection if one doesn’t already exist.



 

Security recommendations #

We strongly recommend enabling Now Assist Guardian for built-in AI security guardrails and continuous monitoring of AI interactions.

Navigation path: Now Assist AI Agents > Settings > Now Assist Guardian

Once enabled, configure:

  • Prompt injection protection — detects prompt injection attempts before they execute. Choose to log the attempt, or block and log it.
  • Offensive content detection — monitors AI-generated content in conversational experiences for potentially offensive or inappropriate material.
  • Sensitive data handling — automatically masks PII and other confidential data so it doesn’t appear in AI prompts or responses. See ServiceNow’s Now Assist Guardian documentation for advanced configuration.

 

Connecting to external systems #

The Quality Clouds Autofix Agent and Quality Clouds Build Agent use an MCP client to connect to the Quality Clouds MCP server to run code Livechecks and retrieve Quality Clouds best practices.

 

Connection and credential #

  1. The connection and credential alias for the MCP is included with the app: Integration Hub > Connections & Credentials > Connection and Credential Aliases > QCMCPServer_1770119813526.

  2. In the Connections related list, look for the record 574f589aebfa7a14c2d1f4a8cad0cdc2. Create a new connection if it doesn’t exist, with:
    • Name: QCMCPServer_1770119813526
    • Credential: QCMCPServer_1770119813526
    • Connection alias: x_qucl_quality_c_0.QCMCPServer_1770119813526
    • Active: true
    • Connection URL: https://mcp.qualityclouds.com/mcp

  3. If the credential QCMCPServer_1770119813526 doesn’t exist, create it with:
    • Name: QCMCPServer_1770119813526
    • Active: true
    • Applies to: ALL MID servers
    • API Key Prefix: Bearer
    • API Key: the API key generated in the Quality Clouds admin portal

 

Dedicated integration user #

  1. Create a new internal user with the admin role — this is the user the agent uses to create and edit configuration elements in the instance.

  2. Create a new Basic Auth profile using that user’s credentials.

  3. Set the profile as the Basic Auth profile for the QC AI Agents REST message.

 

Demo data #

MCP connection and credential records are included with the app as demo data.

 

Testing the configuration #

Once configuration is complete, confirm everything is working end to end:

  1. Open Now Assist and start a conversation with the Quality Clouds Livecheck Agent.

  2. Trigger a Livecheck for a known configuration element, e.g. “Trigger a Livecheck for the Incident Auto-Close Business Rule”, and confirm the agent returns a structured list of findings with severity and description.

  3. Ask for best practice details on one of the findings, e.g. “Show me the best practices for the issues found on the User Sync Script Include”, and confirm remediation guidance is returned.

  4. Request a write-off for a finding, e.g. “Request a write-off for issue X on the Asset Audit SI Script Include”, and confirm the write-off request is created in Quality Clouds.

 

If any step fails, re-check the API key, the REST Message auth profile, and the MCP connection and credential above.

Support #

For help, contact the Quality Clouds Support team at help@qualityclouds.com.

 

Related articles #

Was it helpful ?