Categories › AI & Agents › Multi-agent, orchestration & workflows
Discovery MCP for 11 intelligence domains plus LENS with live tools, routing and endpoints.
Remote server: your requests and data go to brunosan.de. Claude Code: claude mcp add --transport http brunosan-intelligence-concierge https://brunosan.de/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
discover_brunosan — Start here: understand the complete BrunoSan Intelligence network. Returns every intelligence domain, the LENS cross-domain layer, canonicallist_intelligence_domains — List all BrunoSan intelligence authorities. By default this is instant and SSOT-only. Set include_live_tool_counts=true when the agent needsinspect_domain — Open one BrunoSan vertical as a complete capability object. Returns purpose, canonical endpoint, human page, related routing vocabulary, dissearch_capabilities — Search the whole BrunoSan network for what an agent is trying to do. Ranking is deterministic over SSOT descriptions, a documented routing vinspect_tool — Find and inspect one underlying vertical MCP tool. Returns the owning domain, exact live tool description and input schema. This does not explan_intelligence_route — Plan a source-authority route for a complex intelligence goal. The plan is deterministic and names concrete live tools where possible. If seget_connection_info — Return canonical connection details without guessing client-specific config.get_intelligence_status — Check whether each canonical BrunoSan MCP currently initializes and lists tools. This is a capability-plane health check only; it does not eget_access_options — Return current BrunoSan access and pricing from the shared pricing manifest. No price is embedded in this server. Unknown or absent manifestNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.