Open architecture
Open in both directions.
The knowledge base is reachable from the outside — and external tools are reachable from the inside. Both over MCP, the Model Context Protocol.
AI tools are usually a dead end
Most AI applications are closed: data in, answers out. You can neither maintain the knowledge base from the outside nor plug in your own tools.
So the AI stops at the edge of the product — and your existing systems stay locked out.
One MCP server, both directions
Outward, CompanyWizard exposes its own MCP server: read and maintain the knowledge base directly from Claude, Claude Code or any MCP client.
Inward, you embed local MCP servers (beta) and turn internal systems into AI tools — fully local on the desktop. New capabilities arrive as skills via ZIP upload, hot-reloadable.
Two directions, one protocol
-
Outward — your own MCP server
Your knowledge base is readable and maintainable from Claude, Claude Code or any MCP client.
-
Inward — local MCP servers (beta)
Your own tools and internal systems become AI tools — local on the desktop.
-
Extend — skills via ZIP
Upload new capabilities as a ZIP, hot-reloadable, without a restart.
Self-built stack or integrated cockpit?
| Criterion | Self-built tool stack | CompanyWizard (integrated + open) |
|---|---|---|
| Setup | Selecting, connecting, wiring many parts | Ready to use, one interface |
| Learning curve | Own logic per tool | One logic for everything |
| Maintenance & updates | Many versions, brittle chains | Centrally maintained |
| Security & governance | Scattered access and data paths | One login, one privacy pipeline |
| Depth per single feature | Potentially higher (specialist tools) | Solid breadth, not always the peak |
| Extensibility | Free, but your own work | Via MCP, no DIY integration |
| Data sovereignty / portability | Varies per tool | Obsidian-compatible Markdown |
| Reachability from outside | Must be built yourself | Knowledge base reachable via MCP |
What this means for you
- The knowledge base is maintainable from outside — via any MCP client.
- Embed internal systems as AI tools (beta), local on the desktop.
- Skills via ZIP, hot-reloadable — extensible without a restart.
- No knowledge-base lock-in: it stays reachable with standard clients.
Honestly: the limits
-
Breadth does not always beat specialist depth.
An integrated tool rarely reaches the depth of a focused specialist product. If you need the absolute maximum in a single discipline, a dedicated tool serves you better there.
-
"Open" does not mean "boundless".
External tools run over the MCP interface and thus still through CompanyWizard as the hub. You gain flexibility but remain bound to the scope of that interface. Features marked (beta) are beta features: they may change, be restricted or be discontinued. If one is discontinued or substantially restricted, we announce this at least 30 days in advance. Details are set out in section 3a of the service description.
-
Obsidian compatibility is not a full clone.
Content is portable as Markdown with frontmatter and links. Not every plugin behaviour maps one to one, and system-level data such as the vector index is not part of the vault you take with you.
-
An integrated system is also a single point.
A hub simplifies a lot but has to fit your needs. You rely on one hub instead of many independent parts — that is strength and responsibility at once.
Sounds right for your organisation?
In a 30-minute demo we show the concept on your concrete use case — no obligation, with concrete suggestions at the end.