klavis-ai/klavis

Klavis AI: MCP integration platforms that let AI agents use tools reliably at any scale

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 11th, 2026
Created on April 14th, 2025
Open Issues & Pull Requests: 298 (+0)
GitHub issues: Enabled
Number of forks: 556
Total Stargazers: 5,803 (+0)
Total Subscribers: 163 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 35.5 hours
Mean response time: 21.5 days
90th percentile: 96.3 days
Tracked items: 42

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 7% of issues opened in the past year have been closed. Three people close 80% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 29
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 182 days
Stale 30+ days: 25
Stale 90+ days: 21

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 1

Top labels

  • enhancement (5)
  • question (4)
  • ai (1)
  • auth (1)
  • automation (1)
  • bug (1)
  • commits (1)
  • tech-debt (1)

Detailed Description

Klavis is an MCP integration platform that enables AI agents to use tools reliably at any scale.

The platform addresses the challenge of connecting AI agents to external tools and services in a dependable manner. It implements the Model Context Protocol (MCP) standard, which provides a standardized interface for AI agents to discover and invoke tools. The approach allows agents to access a wide range of integrations—including Discord, OAuth2-based services, and custom APIs—through a unified protocol rather than requiring custom code for each tool connection.

Teams building AI agent systems should consider Klavis if they need reliable tool integration across multiple services and want to avoid building custom connectors for each integration. The platform suits projects where agents must interact with external APIs, handle authentication flows, and scale tool usage across many concurrent operations. It is particularly relevant for applications requiring Discord integration or OAuth2-secured services, as these are explicitly supported capabilities.

The project shows strong adoption signals with most open issues originating from external users rather than the core team, indicating real-world deployment. Maintainers respond to new issues and pull requests within a few days. Work in the issue tracker centers on enhancements, user questions, and technical debt, suggesting active development focused on expanding capabilities and addressing user needs while maintaining code quality.