1. Docs
  2. Resources
  3. Deploys & Repos
  4. FAQ, MCP & limits

FAQ, MCP & limits

Answers to common questions about Deploys & Repos, how agents and AI assistants use deploys, and the limits.

4 min read Updated CustomersAdmins

In short

On this page you can

  • Find out whether you need an access token and what it can see.
  • Check which CI systems work and what happens if SmartestQA is unreachable.
  • Learn what Autonomous Agents receive when a deploy succeeds.
  • Look up every length and count limit of repositories and deploys.

How to use it

  1. Filter the questions by your role with the buttons above the list.
  2. Open a question to read the answer and follow its link for the steps.
  3. Check the limits table before you script CI notifications.

Questions and answers#

Do I need an access token?Customers

No. With Deploy notification only you see which version runs where and whether it was tested. A token adds the commits and changed files between versions. See Connection modes.

Can SmartestQA change my repository?Admins

It only reads. A read-only token is enough (which token). The token is stored encrypted and never shown again after you save it. Deleting the repository, or choosing Deploy notification only and saving, removes it.

What can someone do with a leaked deploy token?Admins

Only record fake deploys for that one repository. It opens no other SmartestQA function and no data. Generate a new token; the old one stops working at once.

Which CI systems work?Customers

Any system that can send an HTTP POST: GitHub Actions, GitLab CI and Jenkins have ready-made steps; Azure Pipelines, Bitbucket Pipelines, TeamCity, Argo CD hooks or a deploy script can use the curl tab. See Add the CI step.

Will my deploy fail if SmartestQA is down?Customers

No. The ready-made steps end with || true, so an error in the notification never fails the job. The deploy is simply not recorded; you can send it again later with its deployedAt.

Can tests start automatically after a deploy?Customers

Not from this page. Two ways: let your CI start a pipeline after the notify step, or set up an Autonomous Agent that starts when a deploy succeeds. Either way the run then counts as tested after for that deploy.

Only my web pipeline ran, yet the api deploy shows Tested. Why?Customers

Deploys are matched with pipeline runs by environment and time, not by what the pipeline covers. Any TEST pipeline after the api’s TEST deploy counts. Read the pipeline names under Tests after deploy to see what really ran. See the window.

We have a STAGING environment. Can SmartestQA track it?Customers

Yes for versions, no for test results: add STAGING in the environment mapping and send it from CI. Pipelines run in DEV, TEST or PRP, so STAGING cells show No pipeline environment. If your TEST pipelines target STAGING servers, report those deploys as TEST.

Who can add, change and delete repositories?Admins

Admins and Users with access to the project, on this page. Admins also find the list under Integrations. There is no separate permission for deploys; project access decides. See Roles.

Can one repository be connected to two projects?Admins

Yes. Each project gets its own repository record and its own deploy token, so CI has to notify each project with its own token. Service names only need to be unique within a project.

Our Git server is on the internal network. Will a token work?Admins

Only if the SmartestQA server can reach it. Private addresses (such as 10.x) are allowed; loopback and link-local addresses are not, and redirects are not followed. If it cannot reach the server, use Deploy notification only: CI still reports deploys from inside your network. See Self-hosted servers.

What do Autonomous Agents receive when a deploy succeeds?Admins

The service, environment, commit, previous commit, version, branch and note. With a token they also get up to 50 commit titles, up to 200 changed files, and for GitHub, GitLab and Gitea parts of the code diff of the most changed files (at most 40 files). Files such as .env, keys and certificates are left out, lock files and images are skipped, and values that look like passwords, tokens or API keys are masked. Only agents set to react to deploys use this.

Does this work for mobile and desktop apps?Customers

Yes. A “deploy” is any build you report: an APK uploaded to a test device farm, a desktop installer on a test machine. Send its commit and version from the build job.

For AI assistants (MCP)#

The SmartestQA MCP server has no tool for repositories or deploy records today. An assistant cannot add a repository or read the deploy history; do that on this page. What AI does use is the deploy event: Autonomous Agents that react to deploys receive the change summary described in What do Autonomous Agents receive. Through MCP an assistant can still read the pipeline runs and failures that followed a deploy, with smartest_runs.

Limits#

ItemLimit
Service name40 characters, unique in the project
Display name120 characters
Repository URL, API base URL500 characters
Access token2,000 characters
Default branch, mapped branch, deploy branch200 characters
Environments mapped per repository12
Environment name32 characters
Commit SHA7 to 64 hexadecimal characters
Version · actor · note · build URL120 · 200 · 1,000 · 1,000 characters
Commits / changed files listed per deploy100 / 300
Pipeline runs listed under Tests after deploy10 (newest)
Untested streak countedup to 5 deploys
Deploy history page / period20 rows per load · up to 365 days
Git API wait10 s to connect · 20 s for an answer

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai