Your risk, today.
- "What's my riskiest attack path?"get_attack_paths
- "Which critical Issues are due this week?"get_issues
- "Write the Terraform for Issue 412."get_fix
- "What can reach customer-data?"get_inventory
Alye / Discover with Alye
Discover with Alye. Answers where you already work.
Ask about your cloud risk and your AI spend from Claude, Cursor, GitHub Copilot or Codex. I answer from your live Alye data, explain what it means, and draft the change for you to review.
ClaudeCursorGitHub CopilotCodex
Cursor · acme-infraalye connected
What changed since yesterday's scan?
alye · get_scan_changes
One new attack path and two closed. The new one: internet → web-server → web-role → customer-data, because web-server started allowing IMDSv1 after Tuesday's AMI update.Your port 22 fix is verified. Want the Terraform change for web-server?
Yes, and how much did support's AI spend move this week?
alye · get_fix · get_llm_spend
I added metadata_options to main.tf for you to review. Support is up 38% since Tuesday, from $412 to $568 a day, after the longer system prompt in v2.4.
// What you can ask
Plain questions, answers with numbers.
No dashboards to open and no query language to learn. Ask the way you'd ask a colleague.
Your AI spend, explained.
- "Which service doubled its spend?"get_llm_spend
- "What does initech cost us per request?"get_llm_spend
- "Show me the slowest traces in support."get_traces
- "Which alerts fired today?"get_alerts
One teammate for the whole stack.
- "What changed since yesterday?"get_scan_changes
- "Summarise this week for my manager."get_report
- "Is the scan of acme-prod finished?"get_scan_status
- "What should I fix first today?"get_issues
// Tools
Ten read-only tools over your Alye data.
Your editor's assistant picks the right tool for your question. Every tool reads; none of them can change your cloud.
alye · MCP toolshttps://api.alye.ai/mcp
| Tool | Module | Returns |
|---|---|---|
get_attack_paths | Cloud security | Every route from the internet to sensitive data, with each route's weakest link |
get_issues | Cloud security | Issues ranked by reach, with severity, environment and due date |
get_fix | Cloud security | The fix for an Issue as CLI, Terraform, CloudFormation or console steps, filled in |
get_inventory | Cloud security | Resources, what faces the internet, which role they run as and what it can read |
get_scan_status | Cloud security | Progress and results of the latest scan for each cloud account |
get_scan_changes | Cloud security | What opened and closed since the previous scan |
get_llm_spend | LLM observability | Spend by service, feature, model or customer, over any period |
get_traces | LLM observability | Traces for a service or customer, with each call's cost and latency |
get_alerts | LLM observability | Alert rules and what fired, with the cause |
get_report | Both | A summary of open risk and AI spend for a week or month |
// Setup
Connected in two minutes.
- Create an API key in Alye under Setup.
- Add the Alye MCP server to your editor.
- Ask your first question.
// .cursor/mcp.json
{
"mcpServers": {
"alye": {
"url": "https://api.alye.ai/mcp",
"headers": { "Authorization": "Bearer ${ALYE_API_KEY}" }
}
}
}# Claude Code
claude mcp add --transport http alye https://api.alye.ai/mcp \
--header "Authorization: Bearer $ALYE_API_KEY"// .vscode/mcp.json (GitHub Copilot agent mode)
{
"servers": {
"alye": {
"type": "http",
"url": "https://api.alye.ai/mcp",
"headers": { "Authorization": "Bearer ${env:ALYE_API_KEY}" }
}
}
}# Claude app
Settings › Connectors › Add custom connector
Name Alye
URL https://api.alye.ai/mcp// How it works
Your editor asks. I answer from your data.
Your editorClaude · Cursor · Copilot · CodexIts assistant turns your question into a tool call.
Alye MCP serverapi.alye.ai/mcpChecks your API key and runs the read-only tool.
Your Alye organizationScans, Issues, fixes, spendOnly your organization's data, nothing else.
Read-onlytools answer and draft; you apply every change
Your keyan Alye API key you create and can revoke
Your organswers come only from your organization's data
No codeyour source code isn't sent to Alye to answer
// Who uses it
A minute of asking instead of an hour of digging.
Fix without leaving the code.
Ask for the fix, get it as a change to your Terraform, review it and ship it in the same pull request.
Triage the morning in one question.
"What changed overnight?" gives you new paths, closed ones and what's due, before your first meeting.
Answer the cost question on the spot.
When finance asks why AI spend moved, ask me and forward the answer, numbers included.
// Questions
Before you connect.
Something else? Write to sales@alye.ai.
Which editors and assistants work?
Alye
Any MCP client that supports remote servers over HTTP, including Claude, Claude Code, Cursor, GitHub Copilot in VS Code and Codex.
Can it change my cloud?
Alye
No. Every tool is read-only. When you ask for a fix, I draft it for you to review and apply in your own pipeline.
Is my source code sent to Alye?
Alye
No. I receive the tool calls your assistant makes, such as "get the fix for Issue 412", and return your Alye data. Your editor's assistant writes the change in your files.
Who can see what?
Alye
Answers come only from the organization your API key belongs to. Revoke the key in Alye and access stops.
Do I need both modules?
Alye
No. Discover with Alye works with whichever modules you use. Tools for a module you don't use simply return nothing.