Nuclino MCP Server

Connect Nuclino to your AI agents with the Nuclino MCP server.

Updated

What is Nuclino MCP?

The Nuclino MCP server is a Model Context Protocol server that connects Nuclino to AI agents and assistants as a set of tools. With it connected, an agent can work with Nuclino (team wiki and knowledge base — docs, notes, and projects in one workspace) directly — instead of you copying data in and out by hand.

It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the Nuclino tools become available to the model.

Connect the Nuclino MCP server

Connect Nuclino MCP to Claude Code

  1. 1

    Add the server

    Use `claude mcp add` with the Nuclino MCP server URL (or its `npx` command), following the official docs.

  2. 2

    Authorize

    Complete authentication (OAuth) so Claude Code can call the server.

  3. 3

    Verify

    Ask Claude to use a Nuclino tool to confirm the connection is live.

Connect Nuclino MCP to Cursor

  1. 1

    Open MCP settings

    In Cursor, go to Settings → MCP → Add new server.

  2. 2

    Add Nuclino

    Provide the Nuclino MCP server URL or command and complete authentication.

  3. 3

    Test

    Reference Nuclino from chat to confirm Cursor can reach the tools.

Sample use cases

A documentation agent updates wiki pages after each product release

It reads the changelog, identifies affected docs, patches the relevant Nuclino pages with new features or changed behavior, and flags pages needing human review.

An onboarding agent builds a personalized reading list for new hires

It searches Nuclino for pages tagged with the new hire's role and team, compiles them into a sequenced onboarding checklist, and shares the list on day one.

A knowledge audit agent scans Nuclino for stale content

It identifies pages not updated in 90+ days, checks whether linked resources are still valid, and creates a maintenance queue for content owners.

A meeting notes agent creates Nuclino pages from transcripts

It extracts action items, decisions, and key points from a meeting recording, creates a structured page in the appropriate workspace, and assigns follow-ups.

A search agent answers employee questions using the Nuclino knowledge base

It searches across workspaces for relevant pages, synthesizes an answer from multiple sources, and links to the original docs for deeper reading.

A template agent standardizes new project documentation

It creates a set of Nuclino pages from project templates (PRD, tech spec, launch checklist) when a new project kicks off, pre-filling known details.

A cross-referencing agent identifies orphaned Nuclino pages

It maps internal links between pages, finds content with zero inbound links, and suggests where to add references or whether the page should be archived.

Using Nuclino MCP with Gamut

On Gamut, the Nuclino MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Nuclino and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.

Frequently asked questions

What is the Nuclino MCP server?

It is a Model Context Protocol server that exposes Nuclino to AI agents as tools so they can work with it (team wiki and knowledge base — docs, notes, and projects in one workspace).

How do I connect the Nuclino MCP server?

Point your MCP client (Claude, Cursor, or Gamut) at the Nuclino MCP server URL and complete authentication (OAuth). See the official documentation for the exact URL and scopes.

Can I use Nuclino MCP with Gamut?

Yes — Gamut supports the Nuclino MCP server, so your agents can use it as a tool in automated, triggered workflows.

Can the Nuclino MCP server search across all workspaces?

Yes. The MCP server can search across all workspaces the API token has access to, returning matching pages with their content and metadata.

Does the Nuclino MCP support rich content like images and tables?

Nuclino pages support Markdown-style content including images, tables, checklists, and embedded files. The MCP server can read and write this content programmatically.

Can an agent manage Nuclino workspace permissions?

Workspace and page-level permissions depend on your Nuclino plan. The MCP server operates within the access level of the configured API token.

How does the Nuclino MCP handle content versioning?

Nuclino tracks page history natively. Agents writing through the MCP create new versions just like manual edits, so changes can be reviewed and reverted in the Nuclino UI.