Skip to main content
The Conectores (Connectors) shelf carries the tools Morada has already prepared for you. When the tool your team uses is not there, and its vendor offers an address for connecting AI assistants, you can add it yourself: paste the address, Morada OS lists what that tool knows how to do, and the assistant starts using it in conversations, always asking for your confirmation first. It is the same move as installing a new app on your phone, with one important difference: the app in the store went through a review, and this address went through none. The product interface is currently in Portuguese, so Morada OS labels below are shown as they appear on screen, with English translations in parentheses.

​
Who this is for

You already have the tool

The vendor of the tool you use offers an address for connecting AI assistants. Their documentation usually calls it an MCP server.

You trust the vendor

A custom connector reaches a service Morada has not reviewed. Only add addresses from vendors your company already uses and knows.
For IT teams: each person adds their own custom connectors, and they are visible only to whoever added them. Morada OS accepts only public addresses starting with https://, refuses addresses inside the company network, and every action of a custom connector goes through a confirmation from the person in the chat. There is no automatic routine, schedule, or background sync.

​
Before you start

You need two pieces of information, and both come from the tool’s vendor, not from Morada:

The server address

An address starting with https://, something like https://example.com/mcp. Look in the vendor’s documentation for “MCP”, “connect to an AI assistant” or “AI integration”.

The key, if there is one

Some servers answer without asking for anything. Others ask for an access key, which you generate in the vendor’s own panel, or a sign-in to your account.
Not sure whether the service offers this? Ask the vendor’s support whether they have an MCP server and what the address is. If the answer is no, a custom connector will not help.

​
How to connect

1

Open the connectors

In the Morada OS side menu, click Conectores (Connectors).There are two ways in: the Adicionar (Add) button at the top right, which opens a menu with Adicionar conector personalizado (Add custom connector), and the dashed card with the same name at the end of your connector list.Morada OS connectors shelf, with the Add button at the top and the dashed Add custom connector card at the end of the list
2

Fill in the address

Nome (Name): what you want to call this connector. It is the name that shows on the card and in search.Endereço do servidor (Server address): paste the address the vendor gave you, starting with https://.Descrição (opcional) (Description, optional): one line about what it is for. It helps you remember later, and it helps search find it.The Add custom connector dialog, with the Name, Server address and Description fields and the three authorization options
3

Say how the server asks for authorization

Under Como o servidor pede autorização (How the server asks for authorization), pick the option the vendor pointed to:Picking Chave de acesso also reveals the Nome do cabeçalho (Header name) field. The vendor says which one to use. When in doubt, leave Authorization, which is the most common.
4

Read the notice and confirm

Above the button, a box carries the notice that applies to every custom connector: Morada does not verify these servers, and the server receives the data you authorize on each use.Click Adicionar (Add).
5

Finish the authorization, when there is one

A server with Sem autenticação is connected already. In the other two cases the card waits: with Chave de acesso, Morada OS shows the Informe a chave de acesso (Enter the access key) screen for you to paste the key; with Login no serviço, it opens the vendor’s sign-in page.The key is stored encrypted and is never shown again anywhere. To replace it, click Desvincular (Unlink) on the connector’s page: the Chave de acesso (Access key) field comes back and you paste the new one. The connector stays on your shelf the whole time.
6

Ready to use

The connector shows up under Conectados por você (Connected by you), with the Personalizado (Custom) tag and the number of tools the server offers. Once you have at least one, the shelf gains the Só os meus (Only mine) filter.Shelf with the custom connector already connected, carrying the Custom tag, and the Only mine filter in the filter bar

​
What happens after you connect

A custom connector runs under a rule of its own, stricter than the one for shelf connectors: every tool asks for your confirmation in the chat, every time. On the connectors Morada prepared, a query that changes nothing runs directly and only the actions that write wait for your click. Not here: since nobody reviewed the server, Morada OS does not trust what it says about its own tools, and treats all of them as actions. You stay in control of every step, at the cost of one extra click. In practice: whenever the assistant needs one of the connector’s tools, an approval card shows up in the chat with what it is about to do, and nothing happens before your click. That per-use confirmation is what protects you when the service changes on the other side. The card shows the tool as it stands at that moment, so a change the vendor made never runs unseen.
This applies to custom connectors only. HubSpot, Google Workspace, Microsoft 365 and the other shelf connectors keep their usual behavior: queries run directly, writes wait for your approval.

​
Blocking a tool you do not want

Open Conectores (Connectors) and click your connector’s card. The page lists everything that server offers, with a pill on each tool: The custom connector's page, with the confirmation notice and the tool list carrying the Ask first pill
  • Perguntar antes (Ask first): Morada OS asks for your confirmation in the chat before using that tool. It is how they all start, and there is no way to leave any of them running on its own.
  • Nunca (Never): the tool becomes unavailable. The assistant neither uses it nor asks about it.
Use Aplicar a todas (Apply to all) to change the whole list at once, for example to block the connector without removing it.

​
How to remove it

The connector’s page has two exits, and they do different things:
1

Desvincular (Unlink)

Ends your connection and deletes the key or the sign-in that Morada OS stored. The connector stays on your shelf, disconnected, ready for you to connect again.
2

Remover conector (Remove connector)

Takes the connector off your shelf for good. The confirmation says: “Apagamos suas permissões e a credencial deste servidor. Você pode adicionar de novo depois.” (We delete your permissions and this server’s credential. You can add it again later.) Click Remover (Remove) to finish.
Both settle the Morada OS side. If you generated a key in the vendor’s panel, delete it there too: while it exists, it keeps working for whoever holds it.

​
What Morada OS does and does not do

What it does

Stores your key encrypted and sends it only to that server. Asks for your confirmation before every action. Shows on screen, before your click, exactly what is about to be sent.

What it does not do

It does not verify the server you pasted. It does not hand your conversations to the server: it receives only what you authorize on each use. It does not use the tool unless you ask.
The connection is yours and nobody else’s: the connector you add shows up for you alone, and every colleague who wants the same tool adds their own. There is no background routine either: the assistant touches that server only inside a conversation you started.

​
Messages you may see

(We could not use that address. Check the URL and try again.) This is the answer for any address Morada OS will not take: a typo, an address that does not start with https://, or an address inside a private network, which it refuses for security. Check the address against the vendor’s documentation, character by character, and try again.
(Check the address: that server name does not exist.) The server name carries a character that cannot exist in an address, such as a comma or an underscore. It is usually left over from a copy and paste that took the sentence’s punctuation along.
(This server is already available in the catalog. Connect through the official card.) The tool you tried to paste is already on the shelf, prepared by Morada. Use its official card: it comes with an icon, a description, and the direct-read behavior a custom connector does not have. The link to open it appears right under the message.
(You have already added this server.) That address is already on your shelf, possibly under another name. Look for it in the connector search.
(Invalid key for this server. Check it and try again.) The server answered that it does not recognize the key. Since the key was refused, the connection never came into being and the Chave de acesso (Access key) field is still on screen: generate or copy the key again in the vendor’s panel and paste it there. It is also worth checking that the Nome do cabeçalho (Header name) is the one the vendor asked for.
(This server requires authentication this connector does not provide.) You picked an authorization option different from the one the server expects, for example Sem autenticação (No authentication) on a server that asks for a sign-in. Remove the connector and add it again choosing Chave de acesso (Access key) or Login no serviço (Sign in to the service).
(We could not connect to the MCP server. Check the URL and try again.) The address is valid, but nobody answered. It may be the vendor’s server being down, or an address that changed. Try later and, if it persists, confirm the address with the vendor.
(You have reached the custom connector limit.) There is a cap on custom connectors per person. Remove one you no longer use to make room.
(Too many attempts in a row. Wait a moment.) There were too many connection attempts in a short time. Wait a few moments and try again.

​
Next steps

All integrations

The tools Morada has already prepared, with the walkthrough for each one.

Security and privacy

What the assistant sees, what it never does on its own, and who sees what.