← Knowledge center

Connecting an AI assistant

Point Claude or another assistant at your workspace using the built-in tool surface.

Northpoint ships an MCP server — the open standard (Model Context Protocol) that AI assistants like Claude use to work with real tools. Point an assistant at your workspace and it can read your book and do real work in it, under your account and your permissions.

What an assistant can do

The tool surface spans the same surfaces you use, around sixty tools in all:

  • Contacts — search, create, update, and manage notes.
  • Deals — list and inspect files, create and update them, move stages, manage parties and notes, pull analytics.
  • Tasks — create, update, complete, and snooze — including in bulk by query ("snooze everything on the Maple St file by a week").
  • Deal checklists and task packs — add and update plan items, manage reusable packs.
  • Imports and Today — drive a people import end to end, or read the Today queue and your performance numbers.

Resolver tools let the assistant work from plain language — "the Hendersons' buy side" resolves to the actual deal before anything runs.

Safe by default

Every write tool is confirmation-gated: asked to change something, the server first returns a preview of what would happen, and the change only executes when the assistant confirms it — so a well-behaved client shows you the plan before the action. The assistant operates inside your workspace with your role's permissions and sees exactly what you can see, nothing more.

Turning it on

MCP access is off until enabled. Workspace owners will find the switch in Settings → Workspace (Workspace MCP override); it also requires MCP access to be enabled for the Northpoint instance. While it's off, the server refuses every connection for the workspace.

Connecting an assistant

The server speaks MCP over Streamable HTTP at https://app.northpointcrm.com/api/mcp and authenticates with your Northpoint sign-in token as a bearer token — the same credentials plane as the web and iOS apps, so there's no separate API key to manage or leak. Today that makes connecting a technical exercise (an MCP-capable client plus your access token); a guided connect flow with per-assistant tokens is on the roadmap, and this article will walk through it when it ships.