Connect other MCP clients to Collabiro
Collabiro speaks standard MCP, so any client that supports remote servers can connect. You can also build your own agent or run the stdio server.
Any remote MCP client
Collabiro works with any client that supports remote MCP servers over Streamable HTTP, such as Perplexity, Windsurf, Zed, Goose or your own agent built with an MCP SDK.
- Add a custom MCP server with the URL
https://collabiro.com/mcp. - If the client supports OAuth, sign in. Collabiro supports dynamic client registration, so most clients need nothing else.
- If it asks for a client ID and secret, copy the redirect URI it shows, create a client in Settings → AI tools / MCP → Other, and paste the ID and secret back.
- If it asks for an API key or header, create a personal access token and send it as
Authorization: Bearer vo_pat_….
The common JSON shape for header-based clients:
{
"mcpServers": {
"collabiro": {
"url": "https://collabiro.com/mcp",
"headers": { "Authorization": "Bearer vo_pat_your_token" }
}
}
}Build your own agent in C#
With the official ModelContextProtocol NuGet package:
using ModelContextProtocol.Client;
var transport = new HttpClientTransport(new HttpClientTransportOptions
{
Endpoint = new Uri("https://collabiro.com/mcp"),
AdditionalHeaders = new Dictionary<string, string>
{
["Authorization"] = "Bearer " + Environment.GetEnvironmentVariable("COLLABIRO_TOKEN")
}
});
await using var client = await McpClient.CreateAsync(transport);
foreach (var tool in await client.ListToolsAsync())
Console.WriteLine($"{tool.Name}: {tool.Description}");
var result = await client.CallToolAsync("list_channels", new Dictionary<string, object?>());Class names differ slightly between SDK versions; check the package's README for the version you install.
Run the stdio server from source
Collabiro's repository also contains a small stdio MCP server (src/VirtualOffice.Mcp) that calls the REST API with a company API key. Use it with clients that only support local servers, or when you self-host Collabiro. It needs the .NET 10 SDK and offers the same five tools.
dotnet build src/VirtualOffice.Mcp| Variable | Meaning |
|---|---|
VIRTUALOFFICE_API_KEY | Company API key (required). VO_API_KEY also works. |
VIRTUALOFFICE_API_URL | API origin, for example https://collabiro.com. Defaults to http://localhost:5237. |
{
"mcpServers": {
"collabiro": {
"command": "dotnet",
"args": ["run", "--project", "/absolute/path/to/vOffice/src/VirtualOffice.Mcp", "--no-build"],
"env": {
"VIRTUALOFFICE_API_URL": "https://collabiro.com",
"VIRTUALOFFICE_API_KEY": "vo_xxxxxxxx_your_key"
}
}
}
}The server logs to stderr so it never corrupts the stdio protocol stream.
Try it
Ask other MCP clients: “Use Collabiro to list our channels, then summarize the last 20 messages in #general.” The first call may ask you to approve the tool.
Other clients
See the tool reference and troubleshooting on the MCP overview.
Questions
Does Collabiro support dynamic client registration?
Yes. POST /oauth/register creates a public client. Redirect URIs must be https, or http on localhost, 127.0.0.1 or ::1.
Which credential does the stdio server use?
A company API key, set in VIRTUALOFFICE_API_KEY. It calls the REST API at VIRTUALOFFICE_API_URL.
Last updated 20 November 2026. Something missing or wrong? Tell us.