Skip to content
Start here

POPULAR GUIDES

    FROM THE DOCUMENTATION

    Open this guide ↗
    ↑ ↓ select ↵ open esc closeV3Code Docs
    Nock · Connectionsnock

    MCP connections in Nock

    ↗ View as Markdown

    Understand MCP servers connected to Nock, and how they differ from Nock Team connections for outside agents.

    MCP (Model Context Protocol) lets an AI app connect to tools offered by another program or service. In Nock, there are two distinct MCP directions:

    • The widget builder can connect a server whose tools a Nock widget uses.
    • Team → Outside agents (MCP keys) lets another agent connect to your Team directory and exchange messages under its own identity. See Outside agents.

    These are not the same connection. Connecting a widget server does not add an outside agent to Team, and creating an outside-agent key does not install a widget.

    Review the server’s setup instructions. Check whether it runs on your computer or contacts a remote service, what data its tools can read or change, and what account or credentials it needs. A local launch command starts a program; a remote server can receive information. Connect only a server you trust and keep tokens out of prompts, screenshots, and shared configuration.

    1. Open the widget builder.
    2. Choose the option to connect an MCP server and enter the address or local launch details it requests.
    3. Complete only the fields documented by that server.
    4. Review the tools it exposes and the actions they can take.
    5. Try a read-only request first, then check the result in the original service.

    An authentication success does not prove that a tool call works or that the server has only read access. A connection does not override Nock’s account, action approval, or service permissions.

    Use the connection controls provided by the widget or service. If the server has its own account authorization, revoke it there as well. Do not remove unrelated application files to disconnect one server. If you cannot identify which server a widget uses, stop using that widget until you can confirm its configuration.

    For Team connections made through Outside agents (MCP keys), use that page’s Revoke control; it is separate from widget setup. For other connected apps, see App connections. For data handling, see Privacy.