TestingOps.ai

MCP tools for agents · MCP tool for agents

AWS Knowledge and TestingOps: AWS documentation and regional availability for agents

Connect the AWS Knowledge MCP server and TestingOps agents can check AWS's own documentation and whether a service or feature exists in the region your test environment uses.

  • MCP tool for agents
  • Available
Request a demo AWS Knowledge MCP server
Connection
MCP tool for agents
Writes back
Nothing, its tools only read
Last checked
7 Nov 2026

In short

AWS Knowledge and TestingOps in short

The AWS Knowledge connection is an MCP tool that lets TestingOps agents search and read AWS documentation and check the regional availability of AWS services and features, without a key.

Agents can use it when the system under test runs on AWS, for example to explain an AWS error a run returned or to check whether a feature exists in the test environment's region.

It returns documentation only, so TestingOps opens its tools without an approval step, and AWS applies rate limits to the server.

What it does

What it does for your testing

  1. 1

    Region differences found early

    Input
    A feature your app uses and the region of the test environment
    TestingOps
    Agents can check the feature's regional availability
    Output
    A case flagged as not applicable to that region before it fails there
  2. 2

    AWS errors explained

    Input
    An AWS error code from a failed run, such as a throttling error
    TestingOps
    Agents can search AWS documentation for the error and its causes
    Output
    A likely cause and a documentation reference in the analysis

Step by step

How it works

  1. Pick AWS KnowledgeUnder Integrations → API & MCP, pick AWS Knowledge in Extra tools your agents may use.
  2. Connect without a keySelect Connect; the tools are open to your agents right away, with no approval step.
  3. Agents search or check a regionDuring a task, an agent can search AWS documentation, read a page, list regions or check where a service or feature is available.

AWS Knowledge covers public AWS information. It does not connect to your AWS account and cannot see your resources.

Connect

Setup

  1. In TestingOps, as customer admin, open Integrations → API & MCP and pick AWS Knowledge under Extra tools your agents may use (outgoing, over MCP).
  2. Select Connect.

Documentation: AWS Knowledge MCP server

Where you connect it in TestingOps: Integrations → API & MCP → Extra tools your agents may use → AWS Knowledge

Use cases

Use cases

A feature missing in the test region

Trigger
A case fails only in the test environment's region
Uses
Regional availability data
Agent activity
Can check whether the AWS feature the case relies on is available in that region
Result
A region gap identified instead of a product defect

Throttling during a busy run

Trigger
API steps fail with a throttling error
Uses
AWS documentation for the service's limits
Agent activity
Can look up the documented limits and retry guidance
Result
An analysis that names the limit behind the failures

Sign-in flows on Amazon Cognito

Trigger
A team writes cases for a sign-in flow built on Amazon Cognito
Uses
Cognito documentation
Agent activity
Can read the documented behaviour of the flow, such as token expiry
Result
Cases that check the documented behaviour

Capabilities

Capabilities and limits

What is read

Public AWS documentation and regional availability information

What is produced

Documentation context for agents' test design and analysis; nothing is stored in TestingOps by the tool itself

Where it can write

Nothing. The server returns documentation only.

How it connects

The AWS Knowledge MCP server (https://knowledge-mcp.global.api.aws), without authentication

Account and permissions

  • No AWS account or key
  • Customer admin (or Manage integrations) rights in TestingOps; the tool is visible only to agents working on your organisation's projects

Limits

  • Public information only; it does not see your AWS account or resources
  • AWS states that the server is subject to rate limits
  • Agents running on Grok receive no MCP tools

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team runs its test environment in a newer AWS region. A case for a document-processing feature fails there but passes in the team's other environment.

The agent can check regional availability through AWS Knowledge and finds that the AWS service behind the feature is not offered in that region, so the analysis records a region gap and the team runs the case in the other environment.

Frequently asked questions

Does it connect to our AWS account?

No. It searches public AWS documentation and availability information and does not see your resources.

Do we need AWS credentials?

No. The server needs no authentication, and TestingOps connects without a key.

Are there limits?

AWS states that the server is subject to rate limits; it does not need an account, so there is nothing to raise them with from TestingOps.

Does it need approval?

No. It only returns documentation, so its tools are open to agents on connect.

Next step

Request a demo to see agents use AWS documentation while they analyse runs on AWS-hosted systems.

Request a demoMore mcp tools integrations