How Wix scaled AI-native work to 5,000 employees with Willow
Read More
Enterprise Connectors
Notion SCIM Admin logo. Notion SCIM Admin MCP server connector.

Notion SCIM Admin MCP Server

List Notion Enterprise workspace members (email, role, and active status) and deactivate a member via SCIM. Guests are not included. Requires an Enterprise SCIM token, not a regular Notion integration.

ToolsTools
3
✓Enterprise-grade security
✓SSO & authentication ready
✓Full governance & audit logs

What is the Notion SCIM Admin MCP Server?

The Notion SCIM Admin MCP server gives AI agents structured, permission-aware access to Notion SCIM Admin through the Model Context Protocol. With 3 pre-built actions, agents can read, create, and update Notion SCIM Admin data on behalf of authorized users.

Willow ships the Notion SCIM Admin MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Notion SCIM Admin is being used by every AI agent in your stack.

Tools

Tool

List Users

List Notion workspace members via SCIM. Returns email, name, active status, and workspace role. Guests are not included. Page with startIndex (1-based) and count (max 100).
Tool

Get User

Retrieve one Notion workspace member by SCIM user id (UUID). Guests are not available through SCIM.
Tool

Deactivate User

Remove a member from the Notion workspace by setting SCIM active to false. The Notion account itself is not deleted. The owner who created this SCIM token cannot be removed. Guests cannot be managed via SCIM.
Customize tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

ReviewEdit descriptions
ConfigureChange arguments
ApproveSelect tools
Create NewAdd tool

Set Up Your Notion SCIM Admin MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "willow-notion-scim-admin": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/notion-scim-admin"
    }
  }
}

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "willow-notion-scim-admin": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/notion-scim-admin"
    }
  }
}

Claude Code

CLI
claude mcp add willow-notion-scim-admin --transport http https://<org>.mcp-s.com/mcp/mcp/notion-scim-admin

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/notion-scim-admin",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Notion SCIM Admin

Willow adds the layer Notion SCIM Admin and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Notion SCIM Admin MCP Server FAQ

What is the Notion SCIM Admin MCP server?

The Notion SCIM Admin MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Notion SCIM Admin data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Notion SCIM Admin MCP server different from the official one?

The official Notion SCIM Admin MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Notion SCIM Admin MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Notion SCIM Admin MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Notion SCIM Admin, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Notion SCIM Admin actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Notion SCIM Admin MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Notion SCIM Admin MCP locally, you'll see it.

What does the Notion SCIM Admin MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Notion SCIM Admin MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.