> ## 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.

# Remote MCP

> Let a compatible AI client read and edit authorized cloud knowledge without local files.

Remote MCP is useful for clients that cannot access a local Markdown replica.
The production Streamable HTTP endpoint is:

```text theme={null}
https://mcp.northernlogic.ai/mcp
```

The AI client's support for remote MCP and authentication depends on that client
and its plan. Use its current connector settings for the exact setup controls.

## App-first setup

1. Open **Connections** in the intended workspace.
2. Create a **Remote MCP** connection with a recognizable name.
3. Choose the owner and vaults. Team vaults are off until explicitly selected.
4. Add the MCP URL in your client's remote-server settings.
5. If the client supports browser sign-in, complete OAuth with your Northern
   Logic identity. For a static Bearer client, enter the one-time connection key
   from the receipt into its secure credential configuration.
6. Ask the client to run `orient`, search for a known page, and open it. Check
   the connection's last activity in the app.

The receipt's **Copy agent prompt** contains setup details and may include the
one-time key. Treat it as a credential-bearing prompt. Never paste it into
reusable skill files or public documentation.

## What the client can do

Authorized tools can orient, search, list, read, inspect history, write and edit
pages, move, delete, restore, and resolve conflicts. They can also create and
close Follow-ups and propose preferences. Permissions and the connection's
grants apply to every request.

Ask for a read-only check first:

```text theme={null}
Orient to this workspace. Search for our client onboarding checklist,
open the most relevant page, and summarize it with the source path.
Do not change any pages.
```

## How it differs from local sync

MCP has read/write grants and no replica or sync queue. “Never used” means the
endpoint has not received an MCP request; an idle remote client does not need to
send constant heartbeats. Disabling local sync on a vault is not the same as
revoking MCP read/write access.

If a client starts the OAuth flow first, it may create a workspace connection
with Company and Personal access bounded by your role, leaving team vaults off.
Review the resulting scope in Connections.

For a file-capable tool, [local sync](/connections/local-sync) is the preferred
path.

## Client setup guides

[Claude Code](/connections/claude-code) · [Hermes Agent](/connections/hermes) ·
[Compatibility and verification](/connections/compatibility). If your tool
connects but cannot find a page,
[check its source and grants](/help/agent-cannot-find-page).