csa-mcp-servers

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is csa-mcp-servers?

The csa-mcp-servers project is a repository that consolidates several MCP (Managed Cloud Provider) servers used by the Cloud Security Alliance (CSA) for easier access and management.

how to use csa-mcp-servers?

To use csa-mcp-servers, clone the repository from GitHub and follow the documentation provided within the repo to set up and manage the MCP servers.

key features of csa-mcp-servers?

  • Centralized access to multiple MCP servers
  • Simplified management and deployment of cloud security resources
  • Regular updates and maintenance from the CSA team

use cases of csa-mcp-servers?

  1. Streamlining cloud security operations for organizations.
  2. Facilitating the deployment of security measures across multiple cloud environments.
  3. Providing a single point of reference for managing cloud security resources.

FAQ from csa-mcp-servers?

  • What is the purpose of the csa-mcp-servers repository?

The repository serves to provide a centralized location for managing and accessing the MCP servers utilized by the CSA.

  • How can I contribute to the csa-mcp-servers project?

Contributions can be made by submitting pull requests on GitHub with improvements or additional features.

  • Is there any documentation available?

Yes, detailed documentation is available within the repository to assist users in setting up and managing the servers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
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)

20 hours ago
Gpt Scrambler

2 days ago