Connect Basin to Copilot Studio

Basin is a connector that lets your AI assistants and other people's assistants work from one shared library, across different tools and different companies. Setting it up in Copilot Studio takes a few minutes.

Plan requirements and settings paths last checked 8 September 2026

Before you start

Basin is added to an agent as a Model Context Protocol tool. Three things have to be true first:

Generative orchestration is on for the agent. Microsoft states this as a requirement for MCP, not a recommendation.
You have rights to add tools and edit the agent in your environment.
MCP access runs over Power Platform connectors, so any data policy governing those governs Basin too.

Copilot Studio supports Streamable HTTP only — it dropped SSE after August 2025 — and Basin serves Streamable HTTP. Dynamic discovery does the OAuth work, so there is no client ID or secret to paste.

Sign in happens as you connect

You do not need an account first. Connecting creates one: you enter your email, Basin sends a code, and you are in. The code expires in 10 minutes.

Open the MCP wizard

On your agent's Tools page, select Add a tool, then New tool, then Model Context Protocol. The MCP onboarding wizard opens.

Full steps: Microsoft's MCP setup guide →

Describe the server

Fill in Server name, Server description and Server URL. Write the description carefully: the agent's orchestrator reads it to decide whether to call Basin at all.

Endpointhttps://mcp.getbasin.co/mcp

Choose OAuth 2.0, then Dynamic discovery

Basin supports dynamic client registration with discovery, so Copilot Studio finds the authorisation and token endpoints and registers itself. There is no client ID or secret to paste. Select Create, then Next.

Create the connection

On the Add tool dialog, choose Create a new connection and sign in to Basin, then select Add to agent.

Set the standing instruction

Add one line to the agent's instructions, so it checks Basin rather than answering from whatever is already in the conversation.

Check Basin at the start of every conversation.

Without it the assistant may not think to look. It answers from whatever is already in front of it, which is confident and sometimes wrong, and reads like Basin not working. Basin is a live connector, not a document inside the agent. If the assistant says something is not in Basin, tell it to check before believing that.

Check the connection

Check Basin and tell me which spaces I can access.

A successful response from Basin confirms the connection. If your library is empty, that’s fine—your next step is to save a project.

If it did not work

Selecting Model Context Protocol only opens documentation.The wizard is not available to you. Microsoft documents a second path — a custom connector built from an OpenAPI file in Power Apps — but it does not do dynamic discovery, so the OAuth setup is manual.

The agent never calls Basin.Check generative orchestration is on, and rewrite the server description. The orchestrator chooses tools from that text, so a vague description reads as nothing to call.

If Basin isn’t showing upCheck that sign-in completed and Basin is enabled for this conversation. Try a new conversation or reload the tool, then ask it to check Basin again. Follow your tool’s guide if its settings differ.

Connected, but the project is missing?Ask your assistant to read Basin directly. Check that the earlier conversation saved a file, that both tools use the same Basin account and that this account has access to the space.

Can read, but can’t save?Check that you have editing access to the space. A read-only invitation lets your assistant read the shared work.

Get setup help · hello@getbasin.co

Put it to work.

Save a real project brief, then open a new conversation and ask your assistant to retrieve it.

Try your first project Choose another assistant