1. Get an API key
From Account > API keys create a key starting with `aide_live_…`. The secret is shown once — store it somewhere safe.
Create an API keyModel Context Protocol
Cursor, Claude Desktop, and any other MCP client can launch AIDE scans, read scores, and surface remediation tasks right beside your code. Same API key, same 200+ checks, zero context-switching.
Free accounts cannot connect to MCP. Once you upgrade, the same API key authenticates both REST and MCP traffic.
From Account > API keys create a key starting with `aide_live_…`. The secret is shown once — store it somewhere safe.
Create an API keyAdd the server config below to Cursor, Claude Desktop, or your own agent. Send the API key in the Authorization header.
Cursor configuration · ~/.cursor/mcp.json
{
"mcpServers": {
"aide": {
"url": "https://mcp.aide.tr/mcp",
"headers": {
"Authorization": "Bearer aide_live_yourkey_here"
}
}
}
}Claude Desktop configuration · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"aide": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.aide.tr/mcp"],
"env": {
"AUTH_HEADER": "Bearer aide_live_yourkey_here"
}
}
}
}Verify the connection with cURL
curl https://mcp.aide.tr/mcp \
-H "Authorization: Bearer aide_live_yourkey_here" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Once connected the agent gets `scan_url`, `get_scan`, `get_leaderboard`, and friends as tools. Try a natural prompt like "scan aide.tr in AIDE and summarise the three worst issues".
Eight MCP tools, all bound to the same scopes as the REST API.
Start a new AIDE scan for the given URL (optional profile + SEO inputs).
Fetch score, badge, check details, and remediation list for a scan_id.
Block until the scan reaches a terminal state, then return the final summary.
List your recent scans, filterable by status and domain.
Return the top N domains in a sector from the AIDE leaderboard.
Diff two scans on score, category, and per-check status.
Resolve a single check id (e.g. DISC-001) to its weight + description.
Explain a specific failing check in a scan with a Turkish + English remediation hint.
Every request is signed with `Authorization: Bearer aide_…`. The key is bound to your account; quotas + scopes are enforced server-side. If a key leaks, rotate it from Account > API keys.
Pro: 100 scans + 10,000 API calls per month. Business: 500 scans + 50,000 API calls. Enterprise: custom. 429s should be retried with exponential backoff.
OAuth 2.1 client registration (per MCP 2025-06-18) is on the roadmap. For now MCP only accepts Bearer API keys.