When you're done
An agent you build in Microsoft Copilot Studio, and use in Microsoft 365 Copilot or Teams, can work with BrickDb, signed in with each person's own BrickDb account.
The steps
- Add BrickDb as a tool in Copilot Studio
- Send us the redirect URL
- Create the connection and publish the agent
- Microsoft 365 Copilot: a declarative agent
- Disconnect BrickDb
You need a free BrickDb account. The connection works only for registered members who sign in; nothing is available without signing in, not even the catalogue search. If you have no account yet, open your account page and create one on the sign-in page that opens. If you connect without signing in, the agent shows BrickDb as not connected or asks you to sign in, and none of BrickDb's tools can be used.
The agent works with your BrickDb account and your permissions, and nothing more: it sees what you see in BrickDb and can change only what you can change. What you ask it to look up in BrickDb becomes part of your conversation and is sent to Microsoft, which handles it under its own terms. BrickDb sends nothing to Microsoft on its own.
What it can do today:
- search the catalogue and open a set;
- show what a set sells for, with how many sales the figure rests on;
- read your collection, add a copy, change its condition or notes, and remove a copy (removing asks for the set number as confirmation);
- list the parts you own and work out what your collection is worth;
- tell you what a scanned minifigure bag code is, and record what you found in a bag;
- read your own MOCs and the public MOC gallery.
An administrator's account also reaches the tools of the admin area, because the account has that role. More of BrickDb, such as the wishlist, minifigures and photos, follows step by step.
This guide is for Microsoft Copilot Studio, where organisations build their own agents and publish them to Microsoft 365 Copilot and Teams. It needs Copilot Studio in your organisation. We know of no way to add a server of your own to the free Microsoft Copilot app. Everybody who chats with the agent signs in with their own BrickDb account, and the agent then acts with that person's permissions.
Copilot Studio gives every connection its own return address, which BrickDb's sign-in has to allow before anybody can sign in. That is why the second step is a message to us.
Add BrickDb as a tool in Copilot Studio
- Open your agent in Copilot Studio, or create one under Create → New agent.
- Open Tools, choose Add a tool, then New tool and Model Context Protocol.
- Enter the server name
BrickDb, a description of what it is for, and the server URLhttps://mcp.brickdb.net/mcp. - Under Authentication, choose OAuth 2.0 and the type Manual, and enter: client ID
Pin3wgdbREmDTblSI02tEiX40vAOD5hL; client secret empty; authorization URLhttps://auth.brickdb.net/authorize; token URL template and refresh URL bothhttps://auth.brickdb.net/oauth/token; scopesopenid profile email offline_access. - Choose Create. Copilot Studio shows a redirect URL: copy it, then choose Next.
Send us the redirect URL
Send the redirect URL through the support form and say that it is for Copilot Studio. We add it to BrickDb's sign-in and let you know. Until then the sign-in stops on an error page, and nothing is half connected.
Create the connection and publish the agent
- In the Add tool dialogue, choose Create new connection, then Create, and sign in on BrickDb's sign-in page with your BrickDb account.
- Choose Add and configure.
- To use the agent in Microsoft 365 Copilot or Teams, publish it and add the Teams and Microsoft 365 Copilot channel under Channels.
Microsoft's own page: Connect your agent to an existing Model Context Protocol server.
Microsoft 365 Copilot: a declarative agent
If your organisation builds a declarative agent for Microsoft 365 Copilot with an MCP plugin (for example with the Microsoft 365 Agents Toolkit), register OAuth for it with static registration: client ID Pin3wgdbREmDTblSI02tEiX40vAOD5hL, no client secret, PKCE on, authorization URL https://auth.brickdb.net/authorize, token and refresh URL https://auth.brickdb.net/oauth/token, scopes openid profile email offline_access. Its return address is fixed and BrickDb's sign-in already allows it, so you don't need to send us anything: everybody who uses the agent signs in with their own BrickDb account.
Disconnect BrickDb
Remove the BrickDb tool from the agent under Tools and delete its connection in Copilot Studio. The agent can then no longer reach BrickDb with anybody's account.
If the sign-in ends on an error page, or something else does not work, write to us through the support form.