Connect with the service's sign-in
Many hosted MCP servers, such as Notion and Atlassian, do not want a token pasted into Cora. They want you to sign in on their page and approve access. This is called OAuth. In Cora you press Connect, approve on the service’s page, and the connection is yours. You then share it with Cora in the missions you choose.
The connection is a personal connection. Nobody else can use it, and Cora uses it only in the missions you share it in. This page uses an invented company, Kestrel Cycles, and a team member, Megan.
What you need
Section titled “What you need”- MCP turned on for the organisation (see Connecting an MCP server). An org admin does that once.
- The address of the server. Notion’s is
https://mcp.notion.com/mcp. Atlassian’s ishttps://mcp.atlassian.com/v1/mcp. The service’s own documentation lists it. - An account on that service. Use one that can see only what Cora needs, because Cora can do what your account can do.
- Connect turned on by the operator. If Just for me, under Add any MCP server, says “Not available yet”, ask the operator.
Connect Notion
Section titled “Connect Notion”- Open Connections on the left rail and press Add any MCP server.
- Choose Just for me, then Connect… in the Account section.
- Type a short name, for example
notion(lower-case letters and digits). Cora puts it in front of the server’s tool names, for examplenotion_search. - Type the server address,
https://mcp.notion.com/mcp. - Cora checks the server and shows one line: the service (
mcp.notion.com), who runs the sign-in (for examplemcp.notion.com), and what it asks for (“Asks for: …” or “The service decides what it asks for”). If the server cannot be used, Cora says why in plain words and nothing is saved. If a different company runs the sign-in (its domain is not the server’s), Cora adds a warning: “This server signs in through. Only continue if you trust it.” Read it before you go on. - Choose Connect. The service’s page opens in a new window. Pick your workspace and approve.
- The window closes by itself and the card says Connected as your account. Finish the sign-in in the same browser you pressed Connect in: Cora hands the answer from the service’s window back to the Cora page you left open, and only that page can finish it. Cora lists the server’s tools and switches them on.
Connect Atlassian
Section titled “Connect Atlassian”The steps are the same. Use the short name atlassian and the address https://mcp.atlassian.com/v1/mcp. On Atlassian’s page choose the site (Jira or Confluence) Cora may use.
Connect TikTok Ads
Section titled “Connect TikTok Ads”TikTok Ads is ready-made: press Connect beside TikTok Ads and the name and address are filled in for you. Cora can only read reports from it. See Connecting TikTok Ads.
Connect Salesforce
Section titled “Connect Salesforce”Salesforce does not let Cora register itself, so your organisation sets up its own sign-in app once: your Salesforce admin makes an External Client App, and a Cora org admin enters its key and secret in the Organisation setup section of Salesforce’s page in Connections. Then press Connect beside Salesforce; the name and your organisation’s address are filled in for you. Cora can only read from it. See Connecting Salesforce.
Meta Ads works the same way, with one difference: your Meta admin makes a Meta app, and a Cora org admin enters only its App ID in the same Organisation setup section of Meta Ads. Meta’s sign-in needs no app secret, so Cora keeps none. Then press Connect beside Meta Ads. Cora can only read reports from it, and Meta ends each sign-in after a few hours. See Connecting Meta Ads.
Share it in a mission
Section titled “Share it in a mission”In the Shared with missions section, choose + Share in a mission, as for Google Analytics. A mission can use one connection of each service. Two people’s Notion connections count as the same kind, because the kind is the server’s address host (mcp.notion.com). If a colleague’s Notion is already shared in the mission, the page says whose it is.
Sharing is your consent: Cora uses the connection in that mission with the access you set on it, and every call is recorded. You set each tool, or each group of tools, to Allowed (no asking), Ask first (an approval card that goes to you, the owner) or Off, once, in the Tool access section of the connection’s page in Connections (D0716). If you would rather be asked before Cora changes anything (creates a page, comments, edits an issue), set the Make changes group to Ask first. A mission only shares or stops sharing the connection; it does not choose tools.
When it says Needs reconnect
Section titled “When it says Needs reconnect”Access can end: you revoked it at the service, the service signed everyone out, or the refresh failed. The card then says Needs reconnect and Cora skips that connection until you act. Choose Reconnect, approve again, and the same connection comes back with the missions it was shared in. A short outage at the service does not cause this: Cora just tries again.
Disconnect
Section titled “Disconnect”Choose Disconnect. Cora asks the service to cancel the access (when the service supports it), deletes the stored tokens and stops using the connection in every mission. If you leave the organisation, the same happens for all your connections.
What stays private
Section titled “What stays private”- The tokens live only in the secrets store and are renewed by the API. Cora’s worker gets the current access token for one step, never the refresh token. The tokens never appear in the database, logs, audit entries or prompts.
- Cora asks only for the access the server says it needs, and shows it to you before you press Connect.
- Cora connects only to public https addresses, through the same safe route as other MCP servers. Private and internal addresses are refused.
- The service’s page is the service’s own. Cora never sees your password.
- Only your own browser can finish a sign-in. When you press Connect, your browser makes a secret that stays on that page and is never saved. Cora’s server keeps only a fingerprint of it. The service’s answer comes back to your browser, and your browser sends it to Cora together with the secret. If someone sends you a link to approve and you open it in a different browser, or they send theirs to you, nothing is connected: the answer lands in the wrong place and cannot be used. Cora’s server never keeps the answer.
- If Cora cannot save a renewed sign-in, it marks the connection Needs reconnect and says why, rather than trying again and again.
When Connect is refused
Section titled “When Connect is refused”- The server does not offer a sign-in Cora can start. Cora can register itself with a service that supports automatic registration. A service that needs a client registered by hand is not supported yet. Ask a team member who is an org admin to add it with a token instead, if it offers one.
- The address is private or not https. Use the public https address.
- Already connected. You can have one connection to each server. Use Reconnect, or Disconnect first.