Pure Storage Model Context Protocol Server

Created By
jboothomasa year ago
A simple MCP server to interact with Pure storage arrays
Overview

what is Pure Storage Model Context Protocol Server?

Pure Storage Model Context Protocol Server is a simple server designed to interact with Pure storage arrays, allowing users to retrieve real-time information from a Pure Storage FlashBlade array.

how to use Pure Storage Model Context Protocol Server?

To use the server, install it by adding the relevant entry to the claude_desktop_config.json file and configure it to run the pure-mcp-server command with the necessary arguments.

key features of Pure Storage Model Context Protocol Server?

  • Modular tool (pure-fb) to process commands and retrieve information about arrays, volumes, and hosts.
  • Real-time data retrieval from Pure Storage FlashBlade arrays.
  • Easy configuration for different operating systems.

use cases of Pure Storage Model Context Protocol Server?

  1. Monitoring storage array performance and health.
  2. Managing volumes and hosts in a Pure Storage environment.
  3. Automating storage management tasks through command processing.

FAQ from Pure Storage Model Context Protocol Server?

  • What is the purpose of the MCP server?

The MCP server is designed to facilitate interaction with Pure storage arrays and provide real-time data retrieval.

  • How do I install the server?

You can install the server by adding the necessary configuration to the claude_desktop_config.json file on your system.

  • Is the server compatible with all operating systems?

Yes, the server can be configured for both MacOS and Windows.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jboothomas
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago