MCP server¶

MCP uses a dedicated transport and tool discovery protocol; it has no Swagger or ReDoc interface. See the tool contracts.

AI Hub exposes a stateless FastMCP application at /mcp. It currently provides a health check and two full-agent wrappers:

health_check
opportunities_suggestion_agent_mcp_tool
talent_finder_agent_mcp_tool

The MCP surface is intentionally smaller than the internal LangGraph tool set. Modules are registered by scanning src/mcp_server/tools/; only tools present there are discoverable by MCP clients.

Components¶

• Server: transport and registration;
• Tools: current contracts and authentication;
• Utilities: tenant resolution, user lookup and logging.

Agent wrappers share AI Hub's MongoDB connection, LangGraph subgraphs, selected MongoDB/PostgreSQL persistence backend, LangSmith configuration and tenant AI models.

Tool behavior¶

health_check performs no authentication-dependent business read and returns {"message": "MCP server is up and running!"}.

Both agent wrappers authenticate X-API-Key, resolve tenant/user context and reject a specialist disabled in tenant configuration with 403. They use a thread ID composed from client and application-user IDs, attach trace metadata, and invoke the corresponding complete LangGraph subgraph. See Agent wrappers for their individual logic.