Claude Code Policy: Write Managed Settings Fast
Read More
Enterprise Connectors
NEUS logo. NEUS MCP server connector.

NEUS MCP Server

NEUS hosted MCP: verifiers, proofs, verify flows, agents. Always call neus_context first.

ToolsTools
12
Last updatedLast Updated
Jun 14, 2026
CategoryCategory
All
Install with Willow
Claude
Install
✓Enterprise-grade security
✓SSO & authentication ready
✓Full governance & audit logs

What is the NEUS MCP Server?

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

Willow ships the NEUS 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 NEUS is being used by every AI agent in your stack.

Tools

Tool

neus_context

NEUS MCP session home: current mode, signed-in profile context, verifier summary, reuse-first workflow, tools, and safety rules. Call once at session start.
Tool

neus_verifiers_catalog

Full verifier directory with JSON schemas. Use after neus_context when payloads need exact fields beyond the summary.
Tool

neus_proofs_check

Checks whether existing Proof Receipts satisfy required checks. Eligibility only; never creates proofs. Omit wallet when signed in to use the session profile wallet.
Tool

neus_verify

Creates or continues verification only when Profile access, wallet, and signing already satisfy NEUS for this verifier. Check existing receipts first.
Tool

neus_verify_or_guide

Trust autopilot: reuse existing Proof Receipts when eligible, otherwise return the single next step (continue in MCP or open hosted verify). Omit walletAddress when signed in.
Tool

neus_proofs_get

Reads proof records, tags, delegated agent reads, Profile summary fields, and live proof state. Use returned proof records as receipt references.
Tool

neus_me

Refresh signed-in Profile context, or look up a public Profile by wallet/DID.
Tool

neus_agent_link

Readiness check for an agent wallet: returns linked when identity and access receipts exist. When setup is missing and the caller is authenticated, call neus_agent_create next — browser is fallback only.
Tool

neus_agent_create

Creates agent identity and access receipts. Uses the authenticated session first (no browser when the profile can authorize). Falls back to hosted verify only when session cannot complete. Confirm with neus_agent_link when done.
Tool

neus_secret_create

Store an env-style secret as an encrypted proof. Creates an ownership-basic proof with secret-storage tags. Values are AES-256-GCM sealed and never returned in plaintext via MCP.
1–10 of 12 tools
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 NEUS 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-neus": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/neus"
    }
  }
}

Cursor

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

Claude Code

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

n8n

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

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

Enterprise Governance for NEUS

Willow adds the layer NEUS 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.

NEUS MCP Server FAQ

What is the NEUS MCP server?

The NEUS MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write NEUS 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 NEUS MCP server different from the official one?

The official NEUS 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 NEUS 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 NEUS 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 NEUS, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which NEUS 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 NEUS 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 NEUS MCP locally, you'll see it.

What does the NEUS 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 NEUS 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.

Willow vs ArchestraWillow vs CloudflareWillow vs MetaMCPWillow vs ObotWillow vs MintMCPWillow vs Runlayer

Related MCP Servers

100Hires logo. 100Hires MCP server connector.

100Hires

verified

100Hires MCP server. 131 governed tools.

4bots logo. 4bots MCP server connector.

4bots

verified

4bots MCP server. 9 governed tools.

Aeo logo. Aeo MCP server connector.

Aeo

verified

Aeo MCP server. 2 governed tools.

Affinity logo. Affinity MCP server connector.

Affinity

verified

Affinity MCP server. 10 governed tools.

Your agents are already in the wild.

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

Get Started
Get started
Book a Demo
NEUS MCP Server: Connect AI Agents to NEUS Securely | Willow