Connect your tools

This is your Vaucai using outside tools for you. Tell it what to connect and it takes you through it. From then on it uses them inside the same chat, with no dashboards and no technical steps.

An MCP server

MCP (Model Context Protocol) is a common socket: an open standard for an app to offer its functions to an AI. If a tool you use exposes an MCP server, connect it and your Vaucai gains its functions. There are two ways to authorise, depending on how the server works:

• With your account, if the server uses "sign in with…" (OAuth), like the Higgsfield, Linear or Notion connectors. Say "connect Higgsfield" with its address: it works out on its own how it authenticates, gives you a link and you authorise in the browser. Access renews itself.
• With an access token, if the app gives you one: "connect my MCP server https://…" and paste it when asked.
• Either way the credentials are stored encrypted and never shown again; your Vaucai never sees them. The address must be https.
• You can limit which of the server's tools stay available, instead of all of them.
• Check with "which MCP servers do I have?" and remove one with "disconnect the MCP server X". You can have up to 20 connected, and in each message your Vaucai carries up to 40 of their tools.

Any REST API

Almost every professional app (a CRM, your invoicing) has an API, the door other programs use to talk to it. Connect it and your Vaucai learns to use it, without waiting for them to publish an MCP server. There are two ways to describe it, depending on what the app has:

• With its OpenAPI (formerly Swagger): most publish that descriptor with everything they can do. Say "connect the Holded API" with the address of its OpenAPI.
• By hand, if they do not publish one: describe the operations you care about (what each does and with what data) and its base address. That way you can connect APIs with no descriptor too.

To authenticate, the API may ask for a key. You paste it as a message: it is stored encrypted, your message is deleted and your Vaucai never sees it.

Or it may ask for OAuth2, the "sign in with…" of the big providers (Google, Salesforce, HubSpot). There your Vaucai gives you a link to authorise in the browser, and renews access on its own.

From then on, ask for things by talking: "list my latest Holded invoices". Check with "which APIs do I have connected?" and remove one with "disconnect Holded". Up to 20 connections.

Reading is instant; changing always needs your say-so

Reads happen straight away. When an action is going to change something (create, modify or delete), it shows you a summary of what it is about to send. And it only goes ahead if you confirm with a button. That applies equally to the APIs you connect and to MCP servers.

Your key never appears in that view. The calls are made by our server with your encrypted credential, pinned to your tool's domain and never anywhere else.

Worth knowing

• Your Vaucai carries the tools of your connected servers in every message, and that takes up room. Hence the cap: if you connect a lot, keep active the ones you actually use. The same goes for REST APIs, with the first 80 operations of the set.
• If a server is down or its access has expired, your Vaucai keeps answering you without it. It tells you when you go to use it, and it will never claim it used something it could not.
• We do not continuously monitor the health of every server you connect.