Filtered runs a native MCP server, which means you can wire your content library straight into a Microsoft Copilot Studio agent without writing any custom integration code. Once it’s connected, the agent can search your library, pull back specific assets, and shape recommendations around whoever’s asking, all without leaving Copilot. One thing to flag before you start: making an agent available to your whole organisation requires Microsoft 365 admin access. If you don't have that yourself, you'll need someone who does for the later steps in this guide.
Here’s how the connection gets set up, and what you can expect once it’s live.
Adding Filtered as a tool
In Copilot Studio, an MCP connection is added the same way you’d add any other tool. From the agent’s Tools tab, choose to add a Model Context Protocol server, and you’ll be asked for three things: a server name, a description, and the server URL.
Filtered’s MCP endpoint is:
https://app.filtered.com/mcp
Add MCP server dialog
Choosing how it authenticates
Copilot Studio gives you three options for authenticating the connection: none, an API key, or OAuth 2.0. Filtered currently only supports the API key option. You name the header, provide the key, and Copilot Studio handles the rest of the connection from there. That API key is specific to your Filtered organisation, so the agent will only ever see and return content from your own library, not any other customer's.
API key authentication setup
Once the tool’s created, Copilot Studio will prompt you to finish connecting, name the connection, display the tools it has enabled access to, and confirm you’re happy for the agent to use it. From that point on, the agent has a live line into your content library.
What it’s good for
With the connection in place, the agent can take a plain-English request, like being asked to summarise what’s available on a given topic, or to pull together recommendations for someone’s role, and answer it using your real content rather than guessing from general knowledge. Ask it something outside that scope, generating a wholly new format the library doesn’t hold content for, say, and it’ll tell you it doesn’t have what it needs rather than making something up.
Where it can run
Because this all sits inside Copilot Studio, the same agent isn’t limited to one place. Once you’re happy with it, you can publish it to Microsoft 365 and Teams, SharePoint, a Teams phone agent, or further afield, a plain web app, Slack, WhatsApp, Telegram, email, and a handful of others.
Publishing channels
That means the work of connecting Filtered to Copilot happens once, and where people actually reach it afterwards is entirely up to you.
Making the agent visible to everyone in your org
Turning the Microsoft 365 and Teams channel on is only the first part. On its own, it makes the agent available to you and whoever you share it with directly, it doesn’t put it in front of the whole organisation. For that, there’s a separate step worth knowing about.
Inside the Microsoft 365 and Teams channel settings, tick Make agent available in Microsoft 365 Copilot. You’ll see a preview card confirming the agent’s name and description, along with an Availability options button.
Agent preview and availability options
Open availability options and you’ll get three ways to get the agent in front of people: a direct link, a downloadable file, or listing it in the store. The store option has two levels, showing it to your teammates and anyone you’ve shared it with directly, or showing it to everyone in the organisation. That second option is the one that makes the agent genuinely discoverable org-wide, but it comes with a condition attached: it only appears once an admin has approved it.
Availability options panel
Show to everyone in my org option
Choosing “show to everyone in my org” takes you to a submission screen showing the agent’s name, version, and publishing status. If you’re using manual authentication with Azure Active Directory, this is also where you’d find the app ID needed to configure single sign-on. At the bottom is a Submit to org catalog button, clicking it asks you to confirm you’re giving everyone in the org access to the agent.
Submit to org catalog confirmation
Once submitted, it doesn’t go live automatically. An admin has to review and approve it first, from the Microsoft 365 admin centre, under Agents. That screen isn’t especially easy to find on your own, it sits at:
https://admin.cloud.microsoft/?#/agents/all/requested
This isn't just a Filtered thing, it happens with any agent published this way. So if people say they can't see it, check the approval queue first.
One distinction worth knowing: "available" and "installed" mean different things here. Available just means people can find the agent in the Copilot dashboard and install it themselves if they want it, it won't show up there on its own. If you want it sitting on everyone's dashboard without anyone needing to do that, it needs to be installed for them, not just made available.