> ## Documentation Index
> Fetch the complete documentation index at: https://docs.northernlogic.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connection types

> Use the web, desktop viewer, local files, or a remote MCP client.

| Your situation                            | Best starting point                                               | Local knowledge files?       |
| ----------------------------------------- | ----------------------------------------------------------------- | ---------------------------- |
| Read, edit, or administer in a browser    | [Web app](https://knowledge.northernlogic.ai)                     | No                           |
| Prefer a desktop window and tray controls | [Desktop viewer](/connections/desktop)                            | Only after pairing a replica |
| Your AI tool or editor can access disk    | [Local sync](/connections/local-sync)                             | Yes, for assigned vaults     |
| Your AI client cannot use a local folder  | [Remote MCP](/connections/remote-mcp)                             | No                           |
| Run a headless machine or service         | [Local sync](/connections/local-sync) and [CLI](/connections/cli) | Yes                          |

## A browser does not need a connection record

Sign in and work in the app. Browser sessions use your human identity and do not
create a machine in Connections.

## One replica can serve several local tools

Pair the machine once. File-capable tools on that machine can read the same
authorized Markdown. Use **Add this harness** to install instructions in another
tool without creating a second replica or resetting the first.

Install the desktop app if you want its viewer and tray controls. It adopts the
prompt-installed local replica; installing the app alone does not start
synchronization.

## Give remote clients their own connection

A remote MCP client accesses cloud knowledge through
`https://mcp.northernlogic.ai/mcp`. Its connection has read/write grants, not a
local-sync state. Prefer a separate connection per remote client so you can
identify and revoke it independently.

## Check access before connecting

Choose the intended workspace, connection owner, and vaults. Team vaults start
unselected. A connection cannot exceed the owner's vault role; a write request
can fail even when the tool was configured to request writing.

[Manage connections](/connections/manage) explains changing scope, rotating
credentials, and removing a device.

## Try a guided setup

Start with [Connect your AI tool](/getting-started/connect-ai), then use the
[Claude Code](/connections/claude-code) or [Hermes Agent](/connections/hermes)
guide. [Compatibility](/connections/compatibility) records what has been
checked.