Answered

MCP Server access in a Copilot for Microsoft 365 Agent created in Studio is not functioning

(0) Share

Report

Posted on by AO-16040727-0

I am using an "Open Brain" MCP Server designed by Nate b Jones - which is an open source thing you build yourself based on - NateBJones-Projects/OB1: Open Brain — The infrastructure layer for your thinking. One database, one AI gateway, one chat channel — any AI plugs in. No middleware, no SaaS.

I have got it working perfectly in ChatGPT / Perplexity Pro / Open Webui. It's purpose is to act as a single memory source across all LLM / GPT instances accessible from coding etc and be a single source of truth for projects / memories / thoughts etc.

However - when I built an agent to use this in Copilot Studio - using the "Copilot for Microsoft 365 Agent" method - as I want to access this agent in MS Copilot and Teams (I have the premium licence for office 365 copilot) it connects - I see the tools

Its connecting to Supabase for the tool refresh fine
"headers": [
{
"accept": "application/json,text/event-stream",
"accept_encoding": "gzip, br",
"connection": "Keep-Alive",
"content_length": "48",
"cookie": null,
"host": "uxxxx.supabase.co",
"user_agent": "CopilotStudio PowerFx/1.99.0-local",
"x_client_info": null
}

But when I try and use any function from inside the Teams or the Agent Chat it can't access the server

or in Teams

Categories:

Model context protocol

I have the same question (0)

All responses (7)

Answers (1)

Sort by

Suggested answer

MichaelFP 2,001 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

How do you the the connection of this MCP, se to use the Auhtor (Maker) connection, instead of to use the User connection on the chat. You can set that on the Details of the tool on the copilot studio

-----------------------------
If my answer helped you, please give me a thumbs up (👍).
If solve your question please mark as answer ✔️. This is help the community.
If you want talk with me just tag me @MichaelFP

Was this reply helpful? Yes No
Verified answer

Prasad-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!
Your OB1 (Open Brain) API works in ChatGPT and other frontends because those requests come from your browser or local environment, which your Supabase API allows. However, when you use the agent in Copilot Studio or Teams, the requests come from Microsoft’s cloud servers. If your Supabase API’s CORS settings or authentication do not allow requests from Microsoft domains (like teams.microsoft.com or copilot.microsoft.com), the calls will fail.

What to do:

Update your Supabase project’s CORS settings to allow requests from Microsoft Teams and Copilot domains.

Make sure your API authentication method (API keys, tokens, etc.) works for requests coming from cloud environments, not just your local machine.

Check your Supabase logs to confirm if requests from Teams/Copilot are reaching your server.

This should let your agent access OB1 from within Teams and Copilot Studio.

Was this reply helpful? Yes No
AO-16040727-0 7 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi

It's currently set like this -

In each instance - Teams and Copilot Chat - I had to manually connected the first time I used it - and it came back as connected.

Was this reply helpful? Yes No
AO-16040727-0 7 on at

Like
a
(0)

Report
Copy link

Link copied!

@MichaelFP I have tried to see the option to use Maker-provided credentials - but I only get End User as an option

Was this reply helpful? Yes No
Prasad-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi AO-16040727-0 could you please check your Supabase logs to see whether the requests are reaching the API and whether they're being rejected due to CORS, authentication, or network restrictions? That will help determine whether the issue is with the connection configuration or with the MCP server itself.

Was this reply helpful? Yes No
Suggested answer

MichaelFP 2,001 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

@AO-16040727-0 you are using as end user credential, for MCP supabase it not supported integrated auth with Microsoft. So you need to create the connection during the setup e set as maker credential

Was this reply helpful? Yes No
AO-16040727-0 7 on at

Like
a
(0)

Report
Copy link

Link copied!

Hey all - I fixed it back in APril by rewriting my Supabase edge connector to allow a different kind of Auth- and then logging in Copilot via that method.

Just out of interest -
Never had any options to choose - just the fixed one.

Was this reply helpful? Yes No