Back to Browse
Free
Server data from the Official MCP Registry
Laviya AI Orchestration MCP runtime for IDE and agent integrations.
About
Laviya AI Orchestration MCP runtime for IDE and agent integrations.
What You'll Need
Set these up before or after installing:
Laviya API key used for MCP runtime authentication.Required
Environment variable: LAVIYA_API_KEY
Optional base URL override for the Laviya API endpoint.
Environment variable: LAVIYA_BASE_URL
Optional agent UID override for execution orchestration.
Environment variable: LAVIYA_AGENT_UID
Optional log level override (debug|info|warn|error).
Environment variable: LAVIYA_LOG_LEVEL
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-kartegagithub-laviya-agent-skills": {
"env": {
"LAVIYA_API_KEY": "your-laviya-api-key-here",
"LAVIYA_BASE_URL": "your-laviya-base-url-here",
"LAVIYA_AGENT_UID": "your-laviya-agent-uid-here",
"LAVIYA_LOG_LEVEL": "your-laviya-log-level-here"
},
"args": [
"-y",
"laviya-mcp-server"
],
"command": "npx"
}
}
}Security Report
5.2
Moderate5.2Moderate RiskThis Laviya MCP server shows good security practices with proper authentication via API keys, comprehensive input validation using Zod schemas, and appropriate error handling. The server requires LAVIYA_API_KEY authentication and follows security best practices for a developer tools integration. Minor findings include broad exception handling and some logging concerns, but these are typical for legitimate development tools and don't significantly impact security. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
Scanned 7 files · 7 findings
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
Reviews
No reviews yet
Be the first to review this server!