MCP and Claude integration in BeKnow

    The MCP server brings brand memory inside the AI you already use. Your AI stops starting from zero every session — and there's no key to buy.

    What you can do

    Open the session with a briefing

    Data it produces
    What changed and what's worth doing now
    Where you see it
    MCP client, at start

    Query brand knowledge

    Data it produces
    Positioning, products, tone and already published content
    Where you see it
    Chat in the MCP client

    Follow the content plan

    Data it produces
    Next pieces with priority and progress state
    Where you see it
    Content plan, synced

    Write with the right context

    Data it produces
    Drafts that respect Brand DNA and existing content
    Where you see it
    MCP client

    Update BeKnow from the chat

    Data it produces
    Content status and notes written by the AI into the workspace
    Where you see it
    Memory and content plan

    Use the client you prefer

    Data it produces
    Claude, Cursor or any MCP-compatible client
    Where you see it
    Settings → MCP

    How to connect it

    1. 1

      Open MCP settings

      In BeKnow go to Settings → Integrations and open the MCP section.

    2. 2

      Copy the configuration

      Copy the server address and the token generated for your workspace.

    3. 3

      Paste it in your client

      Add the server to the MCP configuration of Claude, Cursor or your client and restart the session.

    Settings → Integrations · MCP

    MCP server URL
    ••••••••••••••••••••
    Workspace token
    ••••••••••••••••••••
    The token is workspace-scoped: regenerate it and connected clients must be re-authorised.

    What happens without the MCP connection

    BeKnow stays fully usable in the browser: what changes is that your AI can't see brand memory.

    • No briefing when a session opens
    • You paste context into the chat by hand
    • The content plan doesn't update from the conversation

    Cost

    The MCP server is included, free plan too. Conversation token cost stays with the AI client you use, billed by its own provider.

    Frequently asked questions

    What is MCP?

    Model Context Protocol is the standard an AI client uses to connect to external sources. BeKnow exposes brand memory as an MCP server, so the AI can read and update it.

    Does it only work with Claude?

    No. Claude is the most common client, but the same configuration works with any MCP-compatible client, Cursor included.

    Do I need OpenRouter for MCP?

    No. MCP uses the model of the client you already pay for. OpenRouter powers the analysis BeKnow runs on your behalf.

    Can the AI write into BeKnow?

    Yes: it can update content status, add notes and work on the content plan, always in the workspace bound to the token.

    Is it included in the free plan?

    Yes. The free plan includes one workspace with memory, MCP and Google Search Console.

    How BeKnow connects to your stack

    Bring your own keys and keep full control of data, costs, and AI models. No forced tiers, no hidden inference fees.