About Petra Security
Read-only Petra Security MCP: M365 compromise incidents, failed attacks, posture, tenants, usage
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm -e PETRA_API_KEY -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/petra-mcp:v1.0.0PETRA_API_KEYSecretPetra Security API key, created by a Petra Admin under Settings > API Keys at app.petrasecurity.com. Shown only once at creation.MCP_TRANSPORTTransport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.AUTH_MODESecretCredential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.LOG_LEVELLog verbosity: debug, info, warn, errorLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
ghcr.io/wyre-ai/petra-mcp:v1.0.0stdioTools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.