Skip to content

MCP in both directions

Admin

The Model Context Protocol (MCP) is an open interface between AI and tools. CompanyWizard uses it in both directions — it consumes external tools and exposes its own knowledge base as a tool.

Two directions: on the left, local/external MCP servers bring tools into CompanyWizard; on the right, CompanyWizard exposes its knowledge base as an MCP server for external clients (RBAC-protected). Two directions: on the left, local/external MCP servers bring tools into CompanyWizard; on the right, CompanyWizard exposes its knowledge base as an MCP server for external clients (RBAC-protected).

CompanyWizard connects to MCP servers that provide additional tools — database queries, API integrations, file operations. In the chat the AI calls these automatically when needed. Connecting them is described in Connect an MCP server.

Outbound: exposing your own knowledge base

Section titled “Outbound: exposing your own knowledge base”

In the other direction, CompanyWizard can be an MCP server itself: external MCP-capable clients (e.g. coding assistants or other AI tools) thereby access your knowledge base in a controlled way — reading and targeted writing through clearly defined tools.

Crucial: this access is RBAC-protected too — the same role, department and confidentiality rules apply as in the app (RBAC & confidentiality levels). So an external client never sees more than its stored identity is allowed to.

  • One knowledge base, many tools: your knowledge base becomes the shared source — inside and out.
  • A standard instead of a silo: MCP is vendor-independent; you are not tied to a single tool.