Stockpile Reports MCP · Setup

Connect your account to
your AI assistant.

A one-time setup connects Stockpile Reports® to Claude, ChatGPT, Gemini, Microsoft Copilot, and more. Sign in once, approve access, and start asking about your stockpiles in plain language.

Choose your assistant What you'll need

Before you start

Setup takes a couple of minutes. You'll need three things and one address.

  • A Stockpile Reports Business account. The connection is available to Business customers. If your account is Personal or Professional, you won't be able to sign in. Talk to us about moving to Business.
  • Your Stockpile Reports email and password. The same login you use for the Web Application or SR Measure. There's no API key to copy; you sign in through your browser.
  • An AI assistant that supports remote connectors. This guide covers Claude (web, Desktop, and Cowork), Claude Code, ChatGPT, Google's Antigravity CLI (which replaced the Gemini CLI), and Microsoft Copilot Studio. Most other 2025-or-later assistants that can connect to a remote (HTTP) server work the same way.

Connection address

https://mcp.stockpilereports.com/mcp
How sign-in works. When you add the connection, your assistant opens a Stockpile Reports sign-in window in your browser. You sign in with your email and password, then select Allow once, on a page headed Allow access?. No network changes or VPN are needed.

Choose your assistant

Jump to the steps for the tool you use.

Claude Web, Desktop & Cowork Claude Code Command line & IDE ChatGPT Web Google Antigravity Command line Microsoft Copilot Copilot Studio

Using a different assistant? Most others that support a remote (HTTP) MCP connection with sign-in work the same way: add a custom connector, paste the connection address above, and sign in.

Claude

Claude (web, Desktop & Cowork)#

Add the connection once from the Connectors screen. It's then available across Claude on the web, the desktop app, and Cowork.

  1. Open Customize → Connectors. On the web, go straight to claude.ai/customize/connectors; in the desktop app, open Customize from the sidebar (Settings → Connectors now just points you there).
  2. Select Add, at the top right of the Connectors screen. It's the same button on the web and in the desktop app. The Add custom connector panel opens; there are two steps.
  3. On step 1, fill in:
    • Name Stockpile Reports
    • Remote MCP server URL https://mcp.stockpilereports.com/mcp
    Then select Continue.
  4. Step 2 looks more involved than it is: change nothing. Claude reads these off the server and marks them Detected:
    • Authentication Always required
    • OAuth client No client IDClaude registers one with Stockpile Reports automatically.
    Nothing else on that screen needs your attention: leave Managed authorization, Additional request headers and Advanced as they are.
  5. Select Add to create the connector. A Stockpile Reports sign-in window opens. Sign in with your email and password, then select Allow. Stockpile Reports then appears in your connector list under Customize → Connectors.
  6. Start a chat and ask one of the example questions.
The one thing not to change on step 2. Claude marks Use Anthropic's hosted client metadata as Recommended. That's general advice about connectors, and it isn't the right choice here. Stockpile Reports uses the option Claude has already selected for you, so leave it as it is.
Already connected somewhere in your company? Claude allows one connector per server address across a whole team, so if a colleague has already added Stockpile Reports you'll see "A connector with this URL already exists in your organization" and should use the existing one rather than adding your own. You still sign in as yourself the first time you use it, and you see only your own data.
Using the Claude mobile app? You can add the connection there too. The steps above describe the web version, so the screens won't match exactly. Adding it once on any of them makes it available on all of them, so if you have a computer to hand that's the easier route.
Stop the per-tool approval prompts. The first time Claude uses the connection, it asks permission before each tool. To skip the repeated prompts, open Customize → Connectors → Stockpile Reports and, under Tool permissions, set the Read-only tools group to Always allow. Claude puts a tool in that group only when the connection marks it read-only, and Stockpile Reports marks every tool that just looks up data, so anything else still asks first. The one tool that isn't a lookup sends us your feedback, and Claude keeps it in a separate group.
On a Team or Enterprise plan? Only an admin can add the connection, and it's added for the whole team. Admins do it from Settings → Organization → Connectors, and remove it from the same place; removing it there removes it for everyone, so check with your team first. Nothing else needs an admin: each person signs in with their own login, and switching off the per-tool prompts is a personal setting, described above.

Anthropic's own setup docs: Get started with custom connectors using remote MCP.

Claude

Claude Code (command line & IDE)#

Add the connection with one command, then sign in from inside a session.

You may already have it. If you added Stockpile Reports in Claude using the steps above, it's in Claude Code already: connections from your Claude account load automatically when you're signed in with that account. Run claude mcp list first and look for a Stockpile Reports line labelled claude.ai. If it's there and says Connected, you're done, and you can go straight to the example questions. Adding it again would only create a duplicate.
  1. In your terminal, run:
    claude mcp add --transport http stockpile-reports https://mcp.stockpilereports.com/mcp --scope user
  2. Start Claude Code with claude, then run /mcp, choose stockpile-reports, and select Authenticate. A Stockpile Reports sign-in window opens in your browser. Sign in with your email and password, then select Allow.
  3. Confirm it's connected with claude mcp list, which shows the connection with a Connected status. To see the individual tools, run /mcp in a session and select stockpile-reports.
  4. In your session, ask one of the example questions.
Scope. --scope user makes the connection available in every project on your machine. Leave it off and the connection is added for the project you're in and nothing else. There is also --scope project, which does the opposite of limiting it: that one writes a .mcp.json into the project, which everyone who clones it picks up. The same setup works in the Claude Code extensions for VS Code and JetBrains.

Anthropic's own setup docs: Connect to MCP servers.

ChatGPT

ChatGPT (web)#

Custom connections in ChatGPT are set up on the web (chatgpt.com) with Developer mode turned on. On a shared Business, Enterprise, or Edu workspace, a workspace owner enables the feature first. A paid plan is not required; this works on a free ChatGPT account.

  1. On chatgpt.com, open Settings → Plugins and select Developer mode, then turn it on. The switch itself lives under Settings → Security and login, and the Plugins entry just jumps you there.
  2. Open Plugins in the left sidebar and select the + button at the top right, beside the search box. A New Plugin panel opens.
  3. Fill in the details:
    • Name Stockpile Reports
    • Description Look up sites, piles (stockpiles), products (the material in a pile), bunkers, and volume and weight/tonnage measurements in your Stockpile Reports account, to answer questions about current inventory.Optional.
    • Connection Leave this set to Server URLThe other choice, Tunnel, is for a server running on your own machine.
    • Server URL https://mcp.stockpilereports.com/mcp
    • Authentication OAuthAlready selected. Leave Advanced OAuth settings alone; ChatGPT reads what it needs from the server.
  4. Tick I understand and want to continue under the risk warning. Create stays greyed out until you do.
  5. Select Create. A Stockpile Reports sign-in page opens straight away, in the same tab. Sign in with your email and password, then select Allow. ChatGPT returns to the Plugins page and reports Stockpile Reports is now connected.
  6. Start a chat and ask one of the example questions.
"Plugins", "apps" or "connectors"? All three name the same thing. OpenAI has renamed this feature more than once, and the names have not all caught up with each other: the menus now say Plugins, while page addresses and the occasional error message still say connector. Follow the position of the item rather than its label.
Developer mode warns about "elevated risk". That's expected. ChatGPT shows that warning for every connection it hasn't reviewed itself, whoever built it, and it's the only route to a custom connection today. It says nothing about Stockpile Reports specifically. What the connection can actually do is in What your assistant can and can't see below.

OpenAI's own setup docs: Developer mode and MCP apps in ChatGPT.

Google Antigravity

Google Antigravity (command line)#

Add the connection with one command, then sign in from inside a session. Antigravity CLI is Google's terminal assistant, and it replaced the Gemini CLI in June 2026.

  1. Install the Antigravity CLI, then run agy once and sign in with your Google Account. A work account is fine.
  2. In your terminal, run:
    agy mcp add stockpile-reports https://mcp.stockpilereports.com/mcp
  3. Start agy, run /mcp, and select stockpile-reports. Until you sign in it is marked [Auth Needed], with an Unauthorized error beside it. That is expected. agy mcp list won't tell you either way; it shows what you have configured, not whether it's connected.
  4. Select Authenticate. A Stockpile Reports sign-in window opens in your browser. Sign in with your email and password, then select Allow. Google shows you an authorization code: copy it, paste it at the terminal prompt, and press Enter. The terminal reports Authentication successful!
  5. In your session, ask one of the example questions.
Still using the Gemini CLI? Google stopped serving it for personal accounts on June 18, 2026, replacing it with Antigravity CLI. It keeps working if your organization has a Gemini Code Assist Standard or Enterprise license, or a paid API key. There the command is gemini mcp add --transport http stockpile-reports https://mcp.stockpilereports.com/mcp, and you sign in with /mcp auth stockpile-reports. On any other account, use the steps above.
What about the Gemini web and mobile apps? Google offers a way to add a custom MCP server there, under Settings → Connected Apps. It needs a personal Google Account rather than a work or school one, plus Gemini Spark access and a few other conditions Google lists here. We haven't tested Stockpile Reports on it. For a work account, the steps above are the route that works.
No browser on that machine? This still works over a remote connection. The Authenticate step prints the sign-in address, so you can open it in a browser anywhere, and the code you paste back is what completes it.

Google's own setup docs: MCP in Antigravity CLI.

Microsoft Copilot

Microsoft Copilot (Copilot Studio)#

Copilot connects through Copilot Studio, where Stockpile Reports is added as a tool on an agent. It's a few more steps than the other assistants, and the right path for organizations standardized on Copilot.

Setup happens in three parts, and you may only need the first. One person, usually whoever administers Copilot Studio, registers Stockpile Reports once for the whole organization (Part 1). Colleagues who want to build their own agent then skip most of the work (Part 2). And if you'd rather your team simply used the agent you built, without opening Copilot Studio at all, that's Part 3.

Part 1: Register Stockpile Reports (once per organization)#

  1. Open Copilot Studio and check which environment you're in. The link opens your default one, and the name isn't shown anywhere on the page: the switcher is a small icon near the bottom-left, and hovering over it tells you where you are. Make a note of the environment you build in, because your colleagues will need it in Part 2.
  2. Open Agents in the left sidebar and select the agent you want to connect. To start a new one instead, select New agent and give it a name. You can leave the instructions empty and the model as it is; neither affects the connection.
  3. In the panel on the right, select + next to Tools. In the Add a tool dialog, select + Add, then Model Context Protocol (MCP).
  4. Fill in the Add MCP server form:
    • Server name Stockpile Reports
    • Server description Look up sites, piles (stockpiles), products (the material in a pile), bunkers, and volume and weight/tonnage measurements in your Stockpile Reports account, to answer questions about current inventory.Required. Copilot uses it to decide when to call the connection.
    • Server URL https://mcp.stockpilereports.com/mcp
    • Authentication OAuth 2.0
    • Configuration type Dynamic (with discovery)Appears once you choose OAuth 2.0, already selected. Leave it as it is.
  5. Select Add. Copilot reads the server and shows the Select a connection dialog, with the connection listed as Not connected.
  6. Open the dropdown to the right of the Stockpile Reports connection, choose Create new connection, then select Create.
  7. A Stockpile Reports sign-in window opens in a separate browser window. Sign in with your email and password, then select Allow. Watch for that window: it can open behind your main one, or be stopped by a pop-up blocker.
  8. Back in the Select a connection dialog, the connection now shows a green check. Select Add, then save your agent using the disk icon at the top right.
  9. Open the Preview tab at the top of the page and ask one of the example questions. The first time your agent uses the connection in a conversation, Copilot shows a Permission Required card naming the action it wants to run. Select Allow.
If your team will use this agent, read Part 3's note on Authentication mode before you finish. It decides whether each colleague sees their own Stockpile Reports data or yours, and it is the most consequential setting in this guide. Part 1 alone does not raise it.

Part 2: For everyone else#

Once Part 1 is done, Stockpile Reports is available to anyone building an agent in the same Copilot Studio environment. There's no server URL to paste and nothing to configure. Two things do have to be true, though.

You need to be in the same environment the person in Part 1 used. Copilot Studio opens your default environment, so if Part 1 happened somewhere else, the search in step 3 quietly finds nothing. And you need permission to build agents there. If Copilot Studio moves you to a different environment when you try to open that one, that's the permission you're missing, and your Copilot Studio admin can grant it.

  1. Open Copilot Studio and switch to the environment where Part 1 was done. The switcher is a small icon near the bottom-left, and hovering over it tells you where you are.
  2. Open Agents in the left sidebar and select your agent, or select New agent and give it a name. The instructions and the model can stay as they are. Then select + next to Tools.
  3. In the Add a tool dialog, choose the Model Context Protocol (MCP) tab and search for Stockpile Reports. That tab lists Microsoft's own servers until you search, so don't expect to see it before then. Select it.
  4. In the Select a connection dialog: if you've connected before, your existing connection is already chosen and you can go straight to the next step. If not, open the dropdown to the right of the Stockpile Reports connection, choose Create new connection, then sign in with your own Stockpile Reports email and password and select Allow.
  5. Select Add, then save your agent.
  6. Open the Preview tab at the top of the page and ask one of the example questions. Select Allow on the Permission Required card the first time, and the answer follows below it.

Part 3: Let your team use the agent you built#

Parts 1 and 2 give an agent to whoever builds it. Part 3 hands your agent to colleagues who never open Copilot Studio. They use it from Microsoft 365 Copilot like any other agent.

First, decide whose Stockpile Reports data your team will see. In your agent, open the Stockpile Reports tool (the dialog is titled Edit MCP server) and scroll past the list of tools to Authentication mode. It's the most important setting in that dialog.

User (recommended): each colleague signs in with their own Stockpile Reports login and sees their own sites and piles. If your account uses organizations, each person keeps the access you've given them. Costs them a one-time sign-in, described below.

Maker: nobody signs in, and every colleague's questions run through your Stockpile Reports account and return your data. This is the easier setting, which is exactly why it's worth choosing deliberately: if your account uses organizations, it bypasses that scoping entirely. Sensible for a shared team login, wrong if people are meant to see different things.

If you built the agent#

  1. In Copilot Studio, open your agent. In the panel on the right, select + next to Channels, then choose Teams + Microsoft 365.
  2. Leave Microsoft 365 Copilot and Microsoft Teams selected and choose Add channel. Take a moment here. Copilot Studio says this choice can't be changed after publishing.
  3. Publish your agent.
  4. Select Share. It's offered on the panel that appears once publishing finishes, and remains available from your agent afterwards. Add the colleagues or groups who should use it, and select Share.
  5. The Agent shared successfully panel has a Copy link button with an arrow beside it. The button names a destination (it may read Copy link (Microsoft Teams)), so open the arrow and choose Microsoft 365 Copilot. That copies the install link your colleagues need. Nothing confirms the copy. No message appears and the button keeps its old label, so paste it somewhere to check. It should start https://m365.cloud.microsoft/chat/?titleId=.
  6. In a separate browser tab, give them permission in the Power Platform admin center. Sharing the agent does not do this, and without it they cannot connect. Go to admin.powerplatform.microsoft.com, select Manage in the left sidebar and then Environments, and open the environment your agent is in. Under the Access card, select See all beneath Users. Find your colleague in the list and open their summary panel. Choose Manage roles, then Basic User, and Save. A Role assignment confirmation dialog then lists every role they will hold and asks again; select Save a second time, or nothing is granted. Not in the list? Select Add user, enter their work email address, and give them Basic User there. A colleague you have just added to Microsoft 365 may not appear on this page right away; adding them yourself creates them immediately.
  7. Send them the install link, along with the steps to follow: If someone shared this agent with you is linkable directly.
Why step 6, and why that role? Sharing an agent does not give your colleague permission to use its connections, and nothing warns you. Without the right security role they reach the connection screen and get “Connector information unavailable. We are unable to load the connector information. Please try again later.” It never succeeds, however long they wait. Choose Basic User, not Environment Maker. Environment Maker sounds like the more capable choice, and it is the one Microsoft's own agent-sharing documentation points at, but it lets someone read only the connectors they own themselves, so it fails on the connector you built and produces that same error. Basic User can read any connector in the environment and carries no authoring rights, so it is both the choice that works and the smaller one. If your agent is in your tenant's default Power Platform environment, you can skip step 6. Everyone there already has it.
Sharing alone isn't enough. You have to send the link. A shared agent doesn't appear in your colleagues' Copilot agent list, and searching for it by name finds nothing. Don't assume they'll be notified; send them the link yourself. Once they've added it and reloaded the page, it lives in their Copilot sidebar under Agents, which is where they go to use it again.
Don't send them the “Set up connections” link from the Share menu. The Copy link menu also offers Set up connections, and it looks like the right thing to send, but that link opens a page that never finishes loading for someone using the agent. Your colleagues reach the connection screen by asking a question and using the Connection Required card, as in the steps below.
The per-tool switches in Edit MCP server look off when they aren't. That dialog lists the individual tools above Authentication mode, and an enabled switch is rendered in grey. Grey is just how they look, not a sign anything is disabled. If your agent is answering questions, the tools are on. Don't try to fix them.

If someone shared this agent with you#

  1. Open the link you were sent. If you're prompted to sign in, use your work Microsoft account, the one you use for Microsoft 365. Then select Add. If you don't have a link, ask whoever set up the agent: a shared agent can't be found by searching.
  2. If Add opened the agent's chat for you, ask your question there, for example How many active piles do we have? If it didn't, open the agent from the sidebar under Agents first, refreshing the page if it isn't there yet. Then ask your question.
  3. Copilot replies with a Connection Required card, which can take up to half a minute to appear. Select Set up connection.
  4. On the Manage your connections page, the Stockpile Reports row offers Connect or Review, depending on its state. Select whichever you have. On the Create or pick connections screen, open the dropdown to the right of the Stockpile Reports connection and choose Create new connection; if one is already selected, don't accept it unless you created it. Keep this tab open, because nothing in Copilot leads back to this page.
  5. A Connect to Stockpile Reports dialog opens. Enter a Display name so you can tell this connection apart later, such as your own name or email address, then select Create. If the dialog is titled Connect to {{connectorName}}, that's an unfilled Microsoft template rather than a sign anything is wrong.
  6. Sign in to Stockpile Reports with your own email and password and select Allow. The sign-in may open behind your current window. A green check appears beside the connection; select Submit, and the row reads Connected.
  7. Back on the chat tab, select Retry, then Allow on the Permission Required card. The card stays on screen and the answer appears below it, up to half a minute later. Don't select Allow a second time.

Steps 3 to 6 happen once; the connection is yours from then on. The Allow card in step 7 may appear again in a later conversation.

If you see “Unable to sign in. Please try again.” Two causes, and the second is easy to miss. Are you in a private browsing window? In Safari, private browsing stops the connection being saved: you sign in, approve, and get this message anyway, however many times you retry. Use a normal window. Otherwise the usual cause is that the sign-in window never finished, because it opened behind another window or a pop-up blocker stopped it: select Create again and complete the sign-in when the window appears. Your Stockpile Reports password is never entered into Copilot itself; it only ever goes into that Stockpile Reports window.
Each person needs their own Stockpile Reports login, as long as Authentication mode is set to User. On that setting, connections are personal: your agent reads the data you can see, and sharing an agent with a colleague does not share your connection; they sign in as themselves and see their own sites and piles. On Maker, the opposite is true and everyone reads your data through your login. See Part 3.
Use the Model Context Protocol tool type, not a custom connector. Adding Stockpile Reports as a generic (Swagger/OpenAPI) custom connector won't work: the connection registers itself and issues no fixed client ID or secret to paste. The Dynamic (with discovery) option above is built for exactly this.
Microsoft 365 Copilot chat can't add the connection itself. Custom MCP connections are set up in Copilot Studio. Build the agent there, then publish it for your team to use from Copilot. That's Part 3, and your colleagues never need to open Copilot Studio themselves.
Licensing. Copilot Studio runs on the Microsoft Power Platform: the person building the agent needs a Copilot Studio environment with generative AI features enabled, and MCP connections use a premium connector (agent usage is metered in Copilot Credits). Your Power Platform admin can confirm what's enabled. Colleagues who only use a shared agent (Part 3) don't need a Copilot Studio license, and in our testing didn't need a Microsoft 365 Copilot license either. Microsoft 365 Business Standard was enough. If you're told you must buy a seat per person just to use the agent, it's worth checking.

Microsoft's own setup docs: Connect your agent to an existing MCP server covers Part 1, and Share agents with other users and makers covers Part 3.

What you can ask

Once connected, ask in plain language. Answers come back grounded in your own verified measurements, not guesses. Here are a few to get you started.

  • What's my total tonnage of #57 stone across all sites right now?
  • List my sites and how many active piles are at each one.
  • Show me the most recent measurement for the salt pile at my north yard.
  • Which products are set up at my Denver yard, and what conversion factors do they use?
  • How has the measured volume of that pile changed over the last three months?
  • Which piles did we measure by drone last month?
  • Who has access to my account, and what role does each person have?

What your assistant can and can't see

The connection is read-only and tied to your own account, so you stay in control.

  • Read-only. Your assistant can look up your sites, products, piles, bunkers, measurements, and users. It can't change anything, take new measurements, or delete data.
  • Scoped to your account. It sees only data in your Stockpile Reports account. If your account uses organizations, it sees only the parts you can already see in the Web Application.
  • Your sign-in, your control. You connect with your own credentials and approve access once. You can disconnect at any time from your assistant's connector settings.
One exception, and it's worth knowing about. In Microsoft Copilot Studio, an agent's Authentication mode can be set to Maker, which makes everyone's questions run through the account of whoever built the agent rather than their own. On that setting the two points above describe the builder's access, not each person's, including organization scoping. Everywhere else in this guide, and on Copilot's default User setting, your sign-in is your own. See Part 3.

Troubleshooting

A few things that come up during setup.

It says I can't sign in, or that a Business subscription is required.

The connection is available to Stockpile Reports Business accounts. If your account is Personal or Professional, reach out and we'll help you move to a Business plan.

The sign-in window didn't open, or it was blocked.

Allow pop-ups for your assistant and try again. If a tab opened but looks stuck, close it and re-trigger the connection. In Claude Code or the Antigravity CLI you can re-run the authenticate step.

Do I need an API key?

No. You sign in with the same Stockpile Reports email and password you use for the Web Application. There's nothing to copy or paste besides the connection address.

My account uses single sign-on (SSO).

SSO sign-in for the connection isn't available yet. For now, continue to use the Web Application; we'll let you know when SSO is supported.

My assistant has no way to add a connector.

It needs to support remote (HTTP) Model Context Protocol connections. Most assistants released in 2025 or later do. If yours doesn't, use one of the assistants in this guide.

I was asked to sign in again.

That's expected after a long stretch without using the connection, or if you've signed out. Just sign in again and select Allow; your data stays protected behind your login.

In ChatGPT, it asks permission every single time it looks something up.

Connections added to ChatGPT before September 5, 2026 are affected. ChatGPT reads the list of things a connection can do once, when you add it, and never refreshes it. Stockpile Reports now tells your assistant which of its tools only read data, so those stop asking; a connection added before that change is still working from the old list and asks every time. Remove the connection and add it again (Settings → Plugins → Stockpile Reports → … → Delete, then the steps above) and the prompts stop. Nothing else is wrong with it, so there's no hurry if the prompts don't bother you. The same is worth knowing generally: if a connection behaves as though it's missing something the server has since gained, re-adding it is the fix.

Retry keeps showing “Connection Required” even though the row says Connected.

The row shows that a connection exists, not that the agent can use it. An incognito window in Chrome is the quickest thing to try, setting the connection up again there: in our testing that cleared it at once where a normal window would not. Don't use a Safari private window for this, which fails in a different way: the connection is never saved and the sign-in reports “Unable to sign in. Please try again.” A normal Safari window is fine. If it doesn't help, the agent's tool binding may have gone stale: open the agent in Copilot Studio and Publish it again, leaving Authentication mode alone.

My colleague sees “Your organization has prevented this agent from being installed.”

They haven't been shared the agent. Sending them the install link isn't enough on its own: sharing decides whether they can install it, and the security role decides whether they can connect it, so the two fail at different points. Open your agent in Copilot Studio, select Share, add them, and have them reload the install link. A reload is enough; they don't need to sign out. If they get past the install card and then see “Connector information unavailable,” that's the other gate, below.

My colleague sees “Connector information unavailable.”

They don't have the right security role in your Power Platform environment yet. The message says “Please try again later,” but waiting never helps. Give them Basic User (Part 3, step 6). Environment Maker is not enough, and produces this exact screen: it lets someone read only the connectors they own, not the one you built.

A colleague says the Copilot agent replies but never answers with data.

First, check that they waited. The Connection Required card takes up to half a minute to appear and shows “Lining things up…” until it does, and someone who gives up at ten seconds sees a reply that just stops. If they did wait, they almost certainly haven't connected yet. The giveaway is a reply like “I'll look that up” with nothing after it, or “the request wasn't approved.” Ask them to send a question, then use the Connection Required card that appears (Part 3, What your colleagues do). If they were sent a Set up connections link that never finishes loading, that's the wrong link; the card is the way in. If no card appears at all (no Connection Required, no Permission Required, just a reply that trails off), open the agent in Copilot Studio and Publish it again, leaving Authentication mode alone. That re-establishes the link between the agent and its tools, and the cards come back. It is worth trying whenever the agent behaves as though the connection is not there, including the Retry loop above, though it does not always help.

Still stuck?

Email support@stockpilereports.com and tell us which assistant you're connecting and where it stopped. A screenshot of the error helps.