DevTools Documentation
API Keys
Cloud logging, MCP integrations, frontend tooling, and SSH workflows for production DevTools teams.
MCP Access
Cloud Logger
Frontend Tools
SSH Ready
API Keys
- Open Account Settings.
- Create an API key in the API Keys section.
- Store it in a secrets manager and load it at runtime only.
How Keys Are Used
| Use Case | Required Headers | Notes |
|---|---|---|
| Resource Log Ingest | X-API-Key |
Identity is resolved from the URL path. |
| Unified MCP | X-API-Key + X-User-Username (recommended) |
Scopes tools to the authenticated DevTools user. |
| GitHub MCP | X-API-Key + X-User-Username |
Requires connected GitHub account for delegated access flows. |
Auth Examples (Python / curl)
import requests
response = requests.post(
'https://mcp.alshival.ai/mcp/',
headers={
'Content-Type': 'application/json',
'X-API-Key': 'your_api_key',
'X-User-Username': 'your_username',
},
json={
'jsonrpc': '2.0',
'id': '1',
'method': 'tools/list',
'params': {},
},
timeout=15,
)
print(response.status_code, response.text)
curl -sS https://mcp.alshival.ai/mcp/ \
-H "Content-Type: application/json" \
-H "X-API-Key: $ALSHIVAL_API_KEY" \
-H "X-User-Username: $ALSHIVAL_USERNAME" \
-d '{"jsonrpc":"2.0","id":"1","method":"tools/list","params":{}}'
Security Requirements
- Never commit API keys to source control.
- Create one key per deployed service for isolated rotation.
- Rotate immediately if any key is exposed.
- Prefer
X-User-Usernamefor user-scoped MCP calls.