Skip to content

Set up a connector from the chat

What it does

You write or dictate, for example, "Connect Todoist". For services that connect in one step, the assistant answers with a card in the chat. You choose Connect, sign in at the service, return to the same chat, and the assistant continues with your request. It cannot sign in for you: the service's own sign-in and consent page always comes first, and for services that do not connect in one step the assistant points you to the Connectors page instead.

How to ask

Each request below was tried in the chat on qwen3.8-27b, in English and in German, with the wording shown. The card appeared every time for these requests. Other models may word their answers differently.

  1. Ask for the service by name. Write "Connect Todoist." The assistant answers with a card titled Connect Todoist. The card shows "Connects to" and the server address, a short description, "Then I can, for example:" with two example actions, and a Connect button.
  2. Connect a service and continue with your task in one message. Write "Connect DeepWiki, then use it to summarise the repository facebook/react in two sentences." After you choose Connect on the card and return, the app sends one message "DeepWiki is now connected. Please continue with my request." and the assistant carries on with the original task if the service responds. If DeepWiki is already connected and offered to the assistant on this turn, it uses it directly and no card appears.
  3. Say what you want to do. Write "Please connect Notion so you can search my pages."
  4. Set it up and ask in one go. Write "Set up DeepWiki for me, then tell me what the repository facebook/react is about." The assistant starts the connection first and answers the rest once you are connected. In our tests this wording produced the card in 3 of 3 tries for each of Notion, Linear, Sentry, DeepWiki, GitMCP, Context7 and Microsoft Learn, in English and in German.
  5. Dictate it. Write or dictate "hey can you set up linear for me please". Dictation is a normal chat message, so spoken and typed requests work the same way.

What happens after you ask:

  1. The card appears in the chat. It stays there when you reload the page.
  2. Choose Connect. Nothing is created until you do. A service that needs no sign-in connects and returns straight to the chat. For the others the browser opens the service's own sign-in and consent page, where you approve the access.
  3. You return to the same chat. In the mobile app the sign-in opens in the system browser sheet, and closing it after approval brings you back to the chat. The card shows "Todoist is connected." (with the name of your service) and the assistant continues with your request.

Tips

  • Write "Connect" or "Set up" and the name of the service. Both wordings called the connector tool every time in our tests, also when you add a task after it, as in "Set up DeepWiki for me, then tell me what the repository facebook/react is about."
  • On the Myra models of the chat, a message that starts with such a request ("Connect Todoist.", "Connect DeepWiki, then use it to ...", "Please set up Linear", "Connect DeepWiki and summarise facebook/react") always makes the assistant start the connection, so the card appears (unless the service is already connected, then there is no second card); the assistant does not have to decide to do so. Starting the message with a verb like "Connect", "Set up" or "Verbinde" and the service name matters; wordings with other word orders, such as "Can you set Linear up for me", still usually work but are left to the assistant: "Add Notion to my table" or "How do I connect Todoist?" is treated as a normal message.
  • If you write "Connect" with a name that is not in the directory, for example a misspelled one, the assistant tells you that the directory has no such connector and points you to the Connectors page. It does not show a card.
  • A question that only mentions a service, such as "Give me three tips for organising tasks in Todoist.", does not open a card. Ask to connect or set it up when you want one.
  • Add what you want to do after the connection, as in "Connect DeepWiki, then use it to ...". The assistant then continues with it once the connection is made.
  • If the assistant answers in another language than yours, ask again or say which language you want.
  • To see what a chat can use, open the tools menu. A connector that is connected but not ticked there is not used by the chat.

Limits

  • Only services that connect in one step get a card: Todoist, Notion, Linear, Sentry, Atlassian, Confluence, Runway, DeepWiki, Context7, GitMCP and Microsoft Learn. For every other service in the directory (for example GitHub, Gmail, Slack, Asana, Google Drive, Microsoft SharePoint and OneDrive, Salesforce) there is no card: the assistant points you to the Connectors page, where you add it with the setup details it needs (a token, an OAuth client set up by an administrator, or for SharePoint and OneDrive your Entra tenant ID). See Connect SharePoint, GitHub and other tools.
  • Only people who are allowed to create connectors can set one up from the chat. For everyone else the assistant has no such function: you get no card and no link. Ask a colleague who can create connectors, or an administrator.
  • Every entry of the directory is open to everyone who is allowed to create connectors; no administrator has to enable it first.
  • The sign-in and consent page of the service cannot be skipped or shown inside the chat. You never type a password or token into the chat.
  • A chat uses at most 8 connectors. If 8 are already selected, or the new one would come after the first 8, the card says "This chat already uses the maximum of 8 connectors, so Todoist is not among its tools. Open the tools menu, deselect one and select Todoist to use it here." or "Todoist is not selected for this chat. Open the tools menu and select it." The connector is still connected, but the chat does not continue on its own. After a reload of the page this hint may be gone; the tools menu always shows what the chat uses.
  • Separately from the 8 per chat, each person can have only a limited number of connectors. When you reach it, a note in the chat says "You have reached the maximum number of connectors. Remove one you no longer need and try again."
  • One card per answer.
  • This works in the chat of the web app. It does not work through the API, in the Playground or in agents.
  • Connectors cannot be used with Google Gemini, Vertex AI, AWS Bedrock and Perplexity models. Pick a model from another provider.
  • Every one-step service is run by a third-party provider outside Myra, most of them based in the US. The card shows the server address it connects to, and what the assistant reads or writes there is held by that provider under its own terms. Runway is the service whose processing in the US is documented (see Data sources).
  • In the Android app the sign-in page opens outside the app and you do not return to the chat automatically. Use a browser for this step.
  • If you ask for a service that is not in the directory, the assistant may say so, but its wording varies. Add such a service by its URL with New connector.

When something goes wrong

You get no card.

  • The assistant gives a link to the Connectors page instead: the service does not connect in one step. Follow the link and add it there.
  • You get neither a card nor a link: you are probably not allowed to create connectors. Ask someone who can, or an administrator.
  • The service is not in the directory: add it by its URL with New connector under Settings → Connections → MCP Connectors (administrators) or My MCP Connectors.
  • The assistant says the connector exists but it cannot use it here: it is not among this chat's tools, or the project does not allow it. Select it in the tools menu, or open the linked entry and check the project. If its login has expired and the service connects in one step, the card appears again: choose Connect and sign in again. For other services, reconnect on the linked entry.

The card shows a note after you chose Connect. Choose Try again for these. Some of the same notes can also appear as a note in the chat instead of on the card:

  • "Sign-in was cancelled. Click Connect to try again." Choose Try again.
  • "Connection expired — please reconnect." or "Couldn't save the connection. Please try again."
  • "The connection couldn't be completed right now. Please try connecting again." or "Connecting failed." If it keeps failing, check My MCP Connectors.
  • "You can't connect this connector." Try again; if it stays, ask an administrator.
  • "Sign-in for this connector is still being set up. Try again in a moment."
  • "The connector's server couldn't be reached to set up sign-in. Try again later."
  • "Too many connection attempts. Wait a few minutes and try again."

The service refused the automatic sign-in setup. An administrator has to add the connector under Settings → Connections → MCP Connectors with the client ID and secret of an OAuth app. The notes read:

  • "Sign-in for this connector couldn't be set up. Try again, or ask an administrator to enter its OAuth client details."
  • "This service doesn't allow automatic sign-in setup. Ask an administrator to register an OAuth app for it and enter its client ID and secret."
  • "The service refused the automatic sign-in registration. Ask an administrator to register an OAuth app for it and enter its client ID and secret."
  • "This connector's server doesn't publish its sign-in settings, so sign-in can't be set up automatically. Ask an administrator to enter its OAuth settings."
  • "This connector's sign-in endpoints don't use HTTPS, so they can't be trusted. Ask an administrator to check the connector's server address."
  • "This connector's server or sign-in endpoints are on an internal address that can't be reached, so it can't be set up automatically. Ask an administrator to set up this connector."
  • "This connector's OAuth configuration is invalid. Contact an admin."

Other notes on the card.

  • "This connector no longer exists or isn't available to you." The connector was removed or is no longer available to you. Ask again in the chat for a new card.
  • "Sign-in was not finished. Connect to continue." You reloaded the page before the sign-in ended. Choose Try again.
  • "Your connectors could not be loaded right now." Reload the page or try again later.

A note in the chat, not on the card.

  • "We could not confirm that connection. Check My connectors." Open My MCP Connectors and look at the status.
  • "You have reached the maximum number of connectors. Remove one you no longer need and try again." Remove a connector under My MCP Connectors.
  • "This connector no longer exists or isn't available to you." The service is no longer offered in the directory. Add it by its URL with New connector instead.

More on the card.

  • A card has a Remove button only when a half-created connector of yours exists; it takes that connector away again.
  • You are connected, but the assistant says the service cannot be reached: the service itself may be down. Send your request again later.
  • The sign-in does not return in the Android app: use a browser.