Flow Studio
MCP Server Registry
The IMCPServerRegistry — how MCP servers are discovered, registered by server ID, and their tool catalogs are resolved for node palette population.
IMCPServerRegistry
public interface IMCPServerRegistry
{
IMCPServerDefinition GetServer(string serverId);
bool TryGetServer(string serverId, out IMCPServerDefinition server);
IReadOnlyCollection<string> RegisteredServerIds { get; }
Task<IReadOnlyList<MCPToolSchema>> GetToolsAsync(
string serverId, CancellationToken ct = default);
}
public interface IMCPServerDefinition
{
string ServerId { get; }
string DisplayName { get; }
MCPTransportType TransportType { get; } // Http | StdIo | SSE
string EndpointUrl { get; }
int CredentialId { get; } // for auth
int TimeoutSeconds { get; }
}Built-in MCP Servers
| Server ID | Purpose | Tools |
|---|---|---|
bfai-document-ai | Document analysis and extraction | analyze-document, extract-entities, classify-document |
bfai-risk-ai | Risk scoring and anomaly detection | score-risk, detect-anomaly, explain-risk |
bfai-nlp | Natural language processing | summarize, classify-sentiment, translate, extract-keywords |
octopus-tools | Octopus agent tool bridge | Dynamic — tools registered by Octopus agents at runtime |
Health Check
GET /api/mcp/servers/bfai-document-ai/health
{
"serverId": "bfai-document-ai",
"status": "healthy",
"toolCount": 3,
"lastCheckedAt": "2026-05-25T10:00:00Z"
}