Connect what your team already uses
Mantaq reads from 55 sources, from Google Search Console and Analytics to the wikis, drives and trackers your team already runs on. Answers cite the systems your work lives in, so nobody has to export anything first.
Search Console and Analytics, read only
Connect a Google account once and name it after the client it belongs to. Everyone in the workspace can then ask about it by that name, and nobody has to share a login.
webmasters.readonlyReadanalytics.readonlyReaduserinfo.emailReadRead only, by construction. The permissions Mantaq asks Google for carry no ability to write, so there is no write path to disable. Mantaq cannot create, edit or delete anything in a connected account, and it cannot see any property that account could not already see. An administrator can unlink at any time, which deletes the stored credential immediately.
Every source Mantaq can read
Search Console and Analytics are Mantaq's own integration. The other 53 are grouped the way they appear when an administrator adds one. Highlighted names are the ones teams reach for most.
Connected once, current after that
An administrator connects a source and decides who can reach it. Mantaq keeps the content current and answers from what it finds there.
An admin connects it
Connecting is an administrator action, and the credential is stored by Mantaq rather than handed around the team. Mantaq can only ever read what the connecting account could already read.
Access is set per source
Each connected source is either available to the whole workspace or restricted to specific groups. Someone who cannot reach a source cannot get answers drawn from it.
Content stays current
Sources are re-indexed on a schedule, so an answer reflects what a document says now rather than the copy somebody downloaded last quarter.
Answers say where they came from
Every answer cites the documents behind it. If a figure looks wrong, you can open the source it was taken from instead of arguing with the model.
Disconnect and it stops
Removing a connector ends Mantaq's access to it. For Google accounts the stored credential is deleted immediately, and access can also be revoked from the Google account itself.
Not every system has a connector
Most companies run something the catalogue has never heard of. Three routes cover it, and none of them need a new release from us.
Upload files directly
Drop documents and spreadsheets straight into a workspace when the material does not live in a connected system at all.
Point it at a web page
Any page Mantaq can reach can be read, which covers public documentation, price lists and published research.
Bring your own API
Mantaq talks to internal systems through MCP, the same mechanism the Google Search Console and Analytics integration uses. If your team can expose an endpoint, agents can call it.
Start with one source
Connect the system your team argues about most, and ask it something you already know the answer to.