by johnneerdael
Integrate with Netskope to automate private access, app config, policy creation, and diagnostics via API for secure, eff
★ 6
GitHub stars
Manages Netskope Private Access infrastructure through automated publisher deployment, app configuration, policy creation, and network diagnostics.
Netskope is a community-built MCP server published by johnneerdael that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate with Netskope to automate private access, app config, policy creation, and diagnostics via API for secure, eff It is categorized under auth security.
You can install Netskope in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Netskope is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Netskope has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
I recommend Netskope for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Netskope is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We wired Netskope into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We evaluated Netskope against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: Netskope surfaces stars and publisher context so we could sanity-check maintenance before adopting.
I recommend Netskope for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Netskope surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We evaluated Netskope against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Netskope is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 65
A comprehensive Model Context Protocol (MCP) server for managing Netskope Private Access (NPA) infrastructure through AI-powered automation.
This project includes extensive documentation organized for easy navigation:
👉 Start with the Complete Documentation - Overview and navigation guide
| Category | Description | Link |
|---|---|---|
| 🏗️ Architecture | Server design and patterns | Server Architecture |
| 🛠️ Tools Reference | Complete tool documentation | Publisher Tools, Private App Tools, Policy Tools |
| 🔄 Workflows | Common automation patterns | Common Workflows |
| 💼 Real Examples | Complete use cases | Real-World Examples |
The MCP server provides 84 specialized tools across 10 categories:
| Category | Tools | Primary Use Cases |
|---|---|---|
| Publishers | 9 tools | Infrastructure deployment and management |
| Private Apps | 15 tools | Application lifecycle and configuration |
| Local Brokers | 7 tools | Network connectivity and routing |
| Policy Management | 6 tools | Access control and security rules |
| SCIM Integration | 5 tools | Identity and user management |
| Upgrade Profiles | 7 tools | Automated maintenance scheduling |
| Steering | 3 tools | Traffic routing and associations |
| Alerts | 2 tools | Event monitoring and notifications |
| Search | 2 tools | Resource discovery and querying |
| Validation | 2 tools | Configuration compliance |
AI Response: Executes comprehensive deployment workflow
AI Response: Emergency security response workflow
AI Response: Automated compliance assessment
Environment Setup
export NETSKOPE_BASE_URL="https://your-tenant.goskope.com"
export NETSKOPE_TOKEN="your-api-token"
Install and Run
npm install
npm run build
npm start
Connect via MCP Client
{
"mcpServers": {
"netskope-npa": {
"command": "node",
"args": ["/path/to/ns-private-access-mcp/build/index.js"],
"env": {
"NETSKOPE_BASE_URL": "https://your-tenant.goskope.com",
"NETSKOPE_TOKEN": "your-api-token"
}
}
}
}
npm install @johnneerdael/ns-private-access-mcp
git clone https://github.com/johnneerdael/ns-private-access-mcp.git
cd ns-private-access-mcp
npm install
npm run build
Tools are designed to work together through well-defined interfaces:
// Example: Creating a private app with validation and tagging
1. validateName() -> Check app name compliance
2. searchPublishers() -> Find target publisher
3. createPrivateApp() -> Create the application
4. createPrivateAppTags() -> Add organizational tags
5. updatePublisherAssociation() -> Associate with publishers
Every tool uses Zod schemas for type safety and validation:
const createAppSchema = z.object({
app_name: z.string().min(1).max(64),
host: z.string().url(),
protocols: z.array(protocolSchema),
clientless_access: z.boolean()
});
Built-in patterns for handling common issues:
This MCP server transforms complex Netskope NPA management into simple, AI-driven conversations.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.