Docs/Connect MCP Clients
Nunc MCP & ConnectorsClaude · ChatGPT · Gemini · Cursor · VS Code

Connect MCP Clients

Register Nunc's remote Streamable HTTP MCP endpoints in your AI client, sign in via OAuth 2.1 + SSO, grant tool permissions in Console, and invoke SaaS or warehouse tools (such as Microsoft Outlook, Salesforce, and Snowflake) behind Guardian PII masking and human write approvals.

1. Choose the MCP endpoint and optional URL filters

Register one or all five endpoints in the same client. Append ?apps=outlook,salesforce to /mcp, ?warehouse=prod_snowflake to /mcp/analytics, or ?workspace=finance-close to /mcp/memory and /mcp/delegate to keep each session scoped to the tools you need.

ServerEndpoint URLTools Exposed
Tools MCPhttps://api.nunc.cloud/mcpConnected SaaS apps (Outlook, Gmail, Slack, Salesforce, Sage Intacct, Jira, GitHub) and paired Sidecar tools. Filter via ?apps=.
Analytics MCPhttps://api.nunc.cloud/mcp/analyticsnunc_analytics_* — schema discovery, AST-validated read-only SQL, Studio report links, and action proposals. Pin via ?warehouse=.
Compute MCPhttps://api.nunc.cloud/mcp/sandboxIsolated Python, Bash, and TypeScript sandbox execution with staged file upload/download.
Memory MCPhttps://api.nunc.cloud/mcp/memorynunc_search_memory, nunc_ingest, nunc_recall_strategies across Public, Company, Workspace, and Agent tiers.
Delegate MCPhttps://api.nunc.cloud/mcp/delegatenunc_delegate, nunc_delegate_<slug>, nunc_delegate_status, nunc_delegate_stop.

2. Add the endpoint to your AI client

Pick your server and client below to copy the exact CLI command or JSON config file:

Connect in under 60 seconds
OAuth 2.1 + company SSO discovery is built in — no API keys to mint or rotate for interactive sessions.
Streamable HTTP · OAuth 2.1
1. Choose Nunc MCP endpoint
2. Choose your AI client

Claude.ai & Claude Desktop

Open Claude Connectors
  1. Open Settings → Connectors → Add Custom Connector in Claude.ai or Claude Desktop.
  2. Paste each URL below and click Connect.
  3. Sign in with your Nunc / company SSO account and select your organization on the consent screen.
Nunc Tools MCP (Connectors & Actions)
https://api.nunc.cloud/mcp
Nunc Memory MCP (Public · Company · Workspace · Agent)
https://api.nunc.cloud/mcp/memory
Nunc Sandbox MCP (Isolated Code Sandbox)
https://api.nunc.cloud/mcp/sandbox
Nunc Delegate MCP (Background Agents & Tasks)
https://api.nunc.cloud/mcp/delegate
Nunc Analytics MCP (Data Studio & Lakehouse)
https://api.nunc.cloud/mcp/analytics

Claude Code CLI

Register the remote HTTP server in Claude Code, then run /mcp inside a session to complete browser SSO:

claude mcp add --transport http nunc "https://api.nunc.cloud/mcp"
claude mcp add --transport http nunc-memory "https://api.nunc.cloud/mcp/memory"
claude mcp add --transport http nunc-sandbox "https://api.nunc.cloud/mcp/sandbox"
claude mcp add --transport http nunc-delegate "https://api.nunc.cloud/mcp/delegate"
claude mcp add --transport http nunc-analytics "https://api.nunc.cloud/mcp/analytics"

Deploying across an organization? See Claude MCP enterprise lock for MDM-managed managed-mcp.json provisioning.

3. Sign in via OAuth 2.1 and link per-user accounts

  1. Automatic OAuth discovery: When Claude Desktop, Claude Code, ChatGPT, Cursor, or VS Code connects to api.nunc.cloud without a static header, Nunc returns OAuth 2.1 Protected Resource Metadata and opens your browser to accounts.nunc.cloud.
  2. Verify corporate SSO & link personal SaaS: Sign in with your corporate identity provider. For per-user connectors such as Microsoft Outlook, Google Drive, or GitHub, link your individual mailbox or account once on the consent screen. Standing OAuth refresh tokens stay encrypted in your Nunc tenant vault — they are never exposed to the AI client.
  3. Headless / CI alternative: For backend scripts or SDK runners without a browser, create a scoped key in Console → Build → Integrations → API Keys and pass Authorization: Bearer nunc_....
Registering Nunc MCP in Claude Desktop and completing the Nunc OAuth 2.1 SSO and Microsoft Outlook authorization flow
Left: Adding https://api.nunc.cloud/mcp?apps=outlook,salesforce in Claude. Right: Nunc OAuth 2.1 SSO consent screen showing linked Microsoft Outlook mailbox and PBAC read/approval scopes.

4. Enable connectors and grant tool access in Console

Why do 0 tools appear at first? Nunc enforces a default-deny policy engine. Even after connecting an integration and signing in from Claude, zero tools are exposed until an administrator grants rules in Console → Organization → Access.
  1. Open Console → Build → Integrations and enable the connector (for example, Microsoft Outlook).
  2. Open Console → Organization → Access and select the target SSO group (for example, group:finance-ops) or individual user.
  3. Set read-only tools (outlook_list_messages, outlook_search_mail) to Allow, set outbound mutations (outlook_send_email, outlook_reply_message) to Gate (Require Approval), and keep destructive actions (outlook_delete_message) set to Deny.
Configuring Microsoft Outlook Allow, Gate, and Deny tool policies in Nunc Console
Nunc Console (Organization › Access › Microsoft Outlook): read tools execute immediately, outbound email replies pause for human click approval, and deletes are blocked.

5. Walkthrough: Reading and replying to Outlook email from Claude

Once connected and permitted, here is what happens at runtime when a user asks Claude to check unread Outlook threads and send a reply:

  1. Read tool executes with inline PII redaction: Claude calls outlook_list_messages. Guardian verifies maya.chen@northstar.io has Allow permission, fetches her unread messages, and replaces sensitive vendor phone and ACH routing numbers with [REDACTED:PHONE] and [REDACTED:ABA] before the response reaches Claude's context window.
  2. Write tool pauses at Guardian Stage 3 Approval Gate: Claude calls outlook_reply_message with the proposed to and body. Because the tool is set to Gate, Nunc holds the call (409 Awaiting Human Approval) and creates a SHA-256 payload-locked approval request.
  3. Human reviews and clicks Approve & Send: Maya inspects the exact recipient, subject, and email body in Nunc (via Console, Studio, or Slack notification) and clicks Approve & Send Email. Nunc transmits the locked payload via Microsoft Graph and writes the approval record to the ISO/IEC 42001 audit ledger.
Claude calling Nunc Outlook MCP tools with inline PII redaction and a Nunc Guardian human write-approval gate
Runtime flow: outlook_list_messages masks vendor PII inline (left), while outlook_reply_message pauses until the user clicks Approve & Send Email in Nunc Guardian (right).

6. Next steps & enterprise rollout

  • How Nunc Configuration Works — Configure warehouse read-only SQL roles, row-level Scope to User rules, and Guardian sensitivity presets.
  • Lock Claude MCP via MDM — Deploy root-owned managed-mcp.json and managed-settings.json so staff workstations connect exclusively through Nunc.
  • Install Nunc Sidecar — Bridge approved local folders and workstation CLIs on macOS or Windows into /mcp.