Copilot studio (Github harness) Business central MCP tools not found when agent is called

(0) Share

Report

Posted on by BÓ-03091131-0

I have been having issues with the business central MCP connection under tools.
When the connection is selected I get the option of selecting inputs and tools but when I try to call the agent and ask questions related to the tables within the tool it gives the following answer.

Response - "I don’t currently have dedicated Microsoft Dynamics 365 Business Central tools or a live Business Central connector available in this chat."

Note: the MCP works with the Standard harness but not Github.

Categories:

Model context protocol

All responses (4)

Answers (0)

Sort by

Suggested answer

Sam_Fawzi 1,079 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @BÓ-03091131-0,

Look at your Tools tab screenshot. The toggle in the header row is on, but all five individual tool toggles below it are off. The header one is select-all state, not an enable. If no individual tools are switched on, nothing is registered and the agent genuinely has no Business Central tools, which is what it is telling you. Enable the specific tools you need, Confirm, then save and republish.
BÓ-03091131-0 4 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Sam_Fawzi
Thanks for the reply, I did try this and get the same error as before. No tools are detected by the agent.
Sam_Fawzi 1,079 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @BÓ-03091131-0

Thanks for checking. Two things then.
First, stop testing by asking the agent what tools it has. Models are unreliable narrators about their own configuration and will often deny having tools that are wired up correctly. Ask for something that requires the tool instead, like listing your top five customers, and see whether it attempts a call. In your first screenshot it loaded search-before-answer rather than reaching for a tool, which is worth watching for again.

Second, your Authentication mode is set to Maker in both screenshots. Try switching it to User and reconnecting. Maker mode should work in the test pane, but MCP registration under a non-standard harness may not resolve the maker connection the same way, and it is a quick thing to rule out.
Also confirm the Inputs tab actually saved. Environment, MCP Server Configuration, and Company are all mandatory, and if any of them did not commit, tool registration can fail without an error.

If none of that changes it, then the harness difference is the answer rather than your configuration. You have already established that the same MCP server works on the Standard harness and not on GitHub, which is clean isolation. I have not worked with the GitHub harness enough to know whether MCP tool registration is supported there yet, so I would raise it with support and ask directly whether MCP servers are expected to work on that harness. Worth posting back here if you get a definitive answer, since I doubt you are the only one hitting it.
Suggested answer

Mohsin Ali 836 on at

Like
a
(1)

Report
Copy link

Link copied!

Hello @BÓ-03091131-0 - To the best of my knowledge, MCP server tools are not intended to be used directly like a chatbot. Instead, you should give the agent a specific task. For example, ask it to list the top 5 companies, create an invoice, or create an order in the corresponding system. The agent can then select the appropriate tool available through the MCP server and use it to perform the requested action.

So in your case, I would provide following prompt to the agent and let the agent use his available tools to perform the actions.

Create a new sales order for customer Contoso Ltd. Add 10 units of item 1000 and 5 units of item 1001. Before creating the order, show me the customer and item details and ask for my confirmation.