Documentation Index
Fetch the complete documentation index at: https://docs.pleri.ai/llms.txt
Use this file to discover all available pages before exploring further.
I now speak Model Context Protocol (MCP) — which means you can plug me directly into the AI tools your team already uses. Ask me about cloud risks, findings, and security posture right from your editor or AI assistant, without ever switching tabs.
What you’ll need
Before connecting an AI client, grab two things:
A Plerion API token
Head to Settings → API Keys in the Plerion dashboard and create a new API key.Your token will look like: plerion_tak_...Treat your API key like a password. Don’t commit it to source control or share it in chat.
Your MCP endpoint URL
My MCP server runs at:https://{region}.api.plerion.com/pleri/mcp
{region} with your account region — typically au, us, or eu. If you’re not sure, check the URL you use to access the Plerion dashboard.
Connect your AI client
Claude Code
Claude Desktop
Cursor
VS Code
Windsurf
Zed
Claude Code supports remote HTTP MCP servers natively. The quickest way is the CLI:claude mcp add --transport http pleri \
https://{region}.api.plerion.com/pleri/mcp \
--header "Authorization: Bearer plerion_tak_your_key_here"
.mcp.json file (create it in your repo root if it doesn’t exist):{
"mcpServers": {
"pleri": {
"type": "http",
"url": "https://{region}.api.plerion.com/pleri/mcp",
"headers": {
"Authorization": "Bearer plerion_tak_your_key_here"
}
}
}
}
~/.claude.json with the same structure under mcpServers.Run claude mcp list to confirm Pleri is connected, and claude mcp get pleri to inspect the config.
Claude Desktop connects to remote MCP servers via mcp-remote (Node.js required).1. Open your config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:
%APPDATA%\Claude\claude_desktop_config.json
2. Add the Pleri MCP server:{
"mcpServers": {
"pleri": {
"command": "npx",
"args": [
"mcp-remote@latest",
"https://{region}.api.plerion.com/pleri/mcp",
"--header",
"Authorization: Bearer ${PLERION_API_KEY}"
],
"env": {
"PLERION_API_KEY": "plerion_tak_your_key_here"
}
}
}
}
Cursor has native HTTP MCP support — no wrapper needed.1. Open your MCP config:
- Global:
~/.cursor/mcp.json
- Project-scoped:
.cursor/mcp.json in your repo root
Or go to Settings → Tools & Integrations → Add Custom MCP.2. Add the Pleri MCP server:{
"mcpServers": {
"pleri": {
"url": "https://{region}.api.plerion.com/pleri/mcp",
"headers": {
"Authorization": "Bearer ${PLERION_API_KEY}"
},
"env": {
"PLERION_API_KEY": "plerion_tak_your_key_here"
}
}
}
}
Supported via GitHub Copilot (native HTTP) or the Cline extension.GitHub Copilot — open or create .vscode/mcp.json in your workspace:{
"servers": {
"pleri": {
"type": "http",
"url": "https://{region}.api.plerion.com/pleri/mcp",
"headers": {
"Authorization": "Bearer plerion_tak_your_key_here"
}
}
}
}
{
"mcpServers": {
"pleri": {
"type": "streamableHttp",
"url": "https://{region}.api.plerion.com/pleri/mcp",
"headers": {
"Authorization": "Bearer plerion_tak_your_key_here"
}
}
}
}
VS Code can auto-discover MCP servers from Claude Desktop if you’ve already set it up there. Enable chat.mcp.discovery.enabled in VS Code settings.
1. Open your MCP config:
- macOS:
~/.codeium/windsurf/mcp_config.json
- Windows:
%USERPROFILE%\.codeium\windsurf\mcp_config.json
2. Add the Pleri MCP server:{
"mcpServers": {
"pleri": {
"serverUrl": "https://{region}.api.plerion.com/pleri/mcp",
"headers": {
"Authorization": "Bearer ${env:PLERION_API_KEY}"
}
}
}
}
PLERION_API_KEY in your shell environment, or paste your token directly in place of ${env:PLERION_API_KEY}.Windsurf auto-restarts the context server after config changes — no editor restart needed. Zed uses mcp-remote as a bridge for HTTP servers (Node.js required).1. Open Zed settings (Cmd+,) and add to your settings.json:{
"context_servers": {
"pleri": {
"source": "custom",
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://{region}.api.plerion.com/pleri/mcp",
"--header",
"Authorization: Bearer ${PLERION_API_KEY}"
],
"env": {
"PLERION_API_KEY": "plerion_tak_your_key_here"
}
}
}
}
What you can ask me
Once connected, just talk to me naturally in your AI client. Here are some things I can help with:
-
“What are our top cloud security risks right now?”
I’ll pull live findings from your Plerion environment and explain what needs attention most.
-
“Are there any critical findings in our AWS account?”
I’ll surface high-severity issues, explain the risk, and suggest next steps.
-
“Show me recent security posture changes.”
I’ll summarise what’s improved, what’s new, and what the team should look at.
-
“Help me write a fix for this misconfigured S3 bucket.”
I’ll combine context from your cloud environment with the code in your editor.
-
“What compliance gaps do we have for SOC 2?”
I’ll map current findings to your compliance framework and flag what’s missing.
For the richest experience — where I can take action, file tickets, and work autonomously — use me via
Slack or the
Chrome extension. MCP is perfect for bringing my cloud security context right into your AI workflow.
