ServiceNow AI agents should use your product: build on Action Fabric
For vendors with an MCP server, an AI agent or tools that customers want ServiceNow’s agents to call, or that need to act in ServiceNow.
If ServiceNow’s AI agents should call your product, or your agent should act in ServiceNow, build on Action Fabric. Action Fabric is ServiceNow’s MCP client, MCP server and agent-to-agent (A2A) support. List your app as a generative AI app. Plan around three customer-side things: the AI in their ServiceNow package, minimum patch levels, and your estimate of the assists your app will use.
When this plan fits
- You already have an MCP server or an agent API.
- Your customers use ServiceNow’s AI features and want your product inside their agent workflows.
- If your agent only needs to read or write ServiceNow records from outside, check whether ServiceNow’s own MCP server already covers it before you build an app.
What your customers will need licensed
- ServiceNow says “every ServiceNow customer now starts with a complete AI package”, in tiers customers choose from (April 2026). Which AI features your customers have depends on their tier, and AI use is metered in assists.
- For the MCP server console, ServiceNow’s Action Fabric guide lists a “Now Assist SKU for the relevant domain (ITSM, ITOM, etc.)”. Check what your customers’ packages include.
- Now Assist skills exposed through ServiceNow’s MCP server “will consume their usual number of assists when invoked plus 1 assist”, ServiceNow says.
- The Store says: “Partners are required to provide Customers with an estimate of how many assists may be consumed through use of their Apps.”
- When ServiceNow’s agents call your MCP server (the MCP client) or work with your agent (A2A), ServiceNow’s MCP and A2A FAQ gives different prerequisites and assist rules from the MCP server console. Check the path you build on.
- Minimum versions apply: the MCP server console needs “Zurich Patch 9 or Australia Patch 2 as the minimum platform version.”
What you need before you start
- Vendor instances that can run the AI features you build on. ServiceNow says “personal developer instances will include 25 free Build Agent calls” (April 2026), so confirm AI access on your vendor instances before you plan the build.
- Your MCP tools described with the narrowest permissions that work.
- A method for estimating assists per use.
The documents certification needs
Certification reviews your documents as well as your app, and in our experience it’s the part most teams miss. ServiceNow’s certification guide says “Certification has two tracks”: an app review and a listing review.
- For the app review, ServiceNow asks for a “Design Document (for certification team only)”, a “Test Plan with results (for certification team only)” and an “Installation Guide (customer facing)”. Write the design document and test plan on ServiceNow’s templates; it provides a recommended template for the installation guide too.
- For the listing review, your Store listing “consists of marketing documentation, demo videos, and other resources”, and the team inspects it for “Accuracy” and “Adherence to branding guidelines”.
- ServiceNow requires partners to give customers an estimate of how many assists their app may use, so work it out before you write your listing and installation guide.
ServiceNow lists “How well you documented your architecture in your Design Documentation” among the things that decide how long certification takes. The calendar gives the documents a week of their own.
Calendar to a Store listing
ServiceNow’s review typically takes 3–5 weeks, after a week for the certification documents. Design and build depend on the tools you expose, so we size them with you rather than guess.
| Phase | Weeks | Notes |
|---|---|---|
| Design and build | Sized with you | Depends on the tools you expose |
| Certification documents | 1 | Design document, test plan, installation guide and listing |
| ServiceNow certification review | 3–5 | ServiceNow’s typical range; no SLA is published |
Not in ServiceNow’s Build Program yet? Add admission first: in our experience it takes 2–6 weeks, because ServiceNow reviews each application.
The review range is ServiceNow’s: certification “typically requires 3-5 weeks”, and no service level is published. The documents week comes from our own projects.
Certification risks on this path
- Tools that act with broad permissions. Expect security reviewers to ask what an agent can do, not only what it’s meant to do.
- No assists estimate for customers.
- Building against a patch level your customers haven’t reached yet.
After launch
- Maintenance is a release certification for each family release: retest on the new release and submit a revised test plan. ServiceNow’s Upgrade Policy says it “generally releases two new release families per year”. Any change to the app is a recertification, planned as new work. AI features are changing quickly, so retest with each patch as well.
- Update the assists estimate whenever your prompts or tools change.
What your prospect’s security reviewer will ask
- What data your agent can read, and what it can send out of their instance.
- Which actions it can take without a person approving them.
- How the assists cost grows with their usage.
Sources
- Action Fabric: MCP server, MCP client and A2A explained
- Enable MCP and A2A for your agentic workflows (FAQ)
- ServiceNow moves beyond the sidecar AI era (9 April 2026)
- Guide to getting your app certified (KB1270874)
- Top ten failed certification checks
- ServiceNow Store licensing requirements (shown on every listing)
- ServiceNow Upgrade Policy
Review this plan with our team
We’ll check your plan with no commitment: the build path, what your customers will need, and a fixed-scope estimate. Personal reply within 24 business hours.
Review my plancheck_circleFounded by a former ServiceNow certification team member check_circle25+ apps taken through certification check_circleFree project scoping