Integrations

Two services over the same sources

The connection keeps people in the assistant they already have, if it supports MCP. The chat is a separate app at an address like ai.vasefirma.cz. Pohoda, the database, email, and files stay where they are. The window, the account, and the price do not.

Two services

Two setups,not one with a choice at the end.

The sources can be similar. From the moment someone asks, it is a different service: a different window, a different account, and a different price.

01

Connection

Assistant on MCP

  1. 01You choose Pohoda, a database, email, or folders. We do not give access to the whole database until you turn it on.
  2. 02We connect them to the assistant you already have. We do not add a new address or a new window.
  3. 03You ask in the assistant you already have. Everyone who asks has their own subscription.

Examples of assistants that can be connected over MCP.

  • Claude
  • ChatGPT
  • Gemini
  • Grok
  • Perplexity
  • Microsoft Copilot
  • Mistral

CZK 4,000 a month

Plus each person's own assistant subscription.

02

Chat

ai.vasefirma.cz

  1. 01You choose Pohoda, a database, email, or folders. You approve the scope.
  2. 02We build the chat on your address. IT prepares the DNS record. We hold the accounts.
  3. 03The team signs in in the browser on a computer and on a phone. One model is included.

CZK 10,000 a month

The model is included. We agree the team size up front. Larger rollouts are priced separately.

Data connectors

Sources each service can take on its own

The catalog is shared. The connection is built for the service you take: either to an assistant on MCP, or into the chat on your address. You approve the scope.

Google Drive

We connect shared drives, spreadsheets, and contract folders where you already keep them. We do not move the files.

OneDrive

Shared libraries in Microsoft 365. We read only the paths you choose.

PostgreSQL

A question in plain language over the tables and views you allow. We do not give open access to the whole database.

Your own REST API

A connection to an internal system, ERP, or CRM through an API you already run.

PDF and Office files

PDF, DOCX, and XLSX. The text goes into the search index. The original stays with you.

Data flow

How data movesto an answer.

The excerpt index is preparation, not a separate service. The question then leaves by one of two paths. The connection sends it to the assistant the person pays for. The chat sends it from the app on your address, and one model is included in that price. Originals stay with you. A new file shows up after the index refreshes.

01 / 05

Source data

01 · Source data

Company data

Pohoda, SQL, email, Google Drive, and a REST API. You approve the access.

Sources

  1. 01Pohoda
  2. 02SQL
  3. 03Email
  4. 04Google Drive
  5. 05REST API

Deployment

The chat has its own address

This applies only to the chat, not to the connection. The app runs at an address like ai.vasefirma.cz. The team signs in in the browser. The connection has no address: people stay in their own assistant.

  • A DNS record for your subdomain
  • Access only for your team
  • We run our layer
Sample address

https://ai.vasefirma.cz

It works in the browser on a computer and a phone, with no installs and no new infrastructure at your site.

For IT and operations

What you prepare for each service

Connection

Assistant on MCP

  • Access to a folder, to Pohoda, or to selected tables
  • An assistant account for everyone who asks
  • No DNS record and no new address

Chat

ai.vasefirma.cz

  • Access to a folder, to Pohoda, or to selected tables
  • A DNS record for your subdomain
  • We hold the accounts and one model. Nothing is installed on computers

Next step

Which service do you want to start with?

The connection, if people stay in their own assistant. The chat on your address, if the team should have one login and one model.

Write a message