Integrations: vikingQA works with your tools

Connect once. Control per project.

Connect for the organization

An admin connects a tool once, with the provider’s own sign-in. vikingQA does not ask for a personal password.

Enable per project

Choose which projects use the connection, and which Jira project, Slack channel or repository each one can reach.

Choose what the agent can do

Enable each capability separately, such as “create issue” or “post message”. The agent has no other access.

Custom

Bring your own tool. Roadmap

Your team has tools that no directory lists: an internal test-data service, a feature-flag system, a home-built ticket tracker. Custom MCP servers are on our roadmap: you will connect these tools through a remote MCP server. MCP (Model Context Protocol) is an open standard that lets an AI agent use external tools.

How it will work

Add the server’s URL and authorize it.
vikingQA lists the tools the server offers. Enable the ones the agent can use.
Set this per project. One project’s tools are not available in another.
Each call the agent makes goes through the same permission check as the built-in integrations.

Add MCP server

Roadmap

https://tools.example.com/mcp

Create test dataEnabled

Read feature flagsEnabled

Find test accountsEnabled

Delete test dataOff

Change feature flagsOff

Design preview. The tools and the server are examples.

Works with the tools your team already uses.

Connect once. Control per project.

Connect for the organization

Enable per project

Choose what the agent can do

Bring your own tool. Roadmap

Catch the next bug before your customers do.