
π Hosted MCP Service | π³ Self-Hosted Solutions | π Enterprise OAuth
Get instant access to 50+ MCP servers with our managed infrastructure - no setup required:
π Get Free API Key β
pip install klavis
# or
npm install klavis
from klavis import Klavis
klavis = Klavis(api_key="your-free-key")
server = klavis.mcp_server.create_server_instance("GMAIL", "user123")
# Run GitHub MCP Server (no OAuth support)
docker run -p 5000:5000 -e AUTH_DATA='{"access_token":"ghp_your_github_token_here"}' \
ghcr.io/klavis-ai/github-mcp-server:latest
# Run Gmail MCP Server with OAuth
docker run -p 8000:5000 -e KLAVIS_API_KEY=your_key \
ghcr.io/klavis-ai/gmail-mcp-server:latest
For Cursor, use our hosted service URLs directly - no Docker setup needed:
{
"mcpServers": {
"klavis-gmail": {
"url": "https://gmail-mcp-server.klavis.ai/mcp/?instance_id=your-instance"
},
"klavis-github": {
"url": "https://github-mcp-server.klavis.ai/mcp/?instance_id=your-instance"
}
}
}
π‘ Get your personalized configuration instantly:
- π Visit our MCP Servers page β
- Select any service (Gmail, GitHub, Slack, etc.)
- Copy the generated configuration for your tool
- Paste into Claude Desktop config - done!
- π Hosted Service: Production-ready managed infrastructure with 99.9% uptime SLA
- π Enterprise OAuth: Seamless authentication for Google, GitHub, Slack, Salesforce, etc.
- π οΈ 50+ Integrations: CRM, productivity tools, databases, social media, and more
- π Instant Deployment: Zero-config setup for Claude Desktop, VS Code, Cursor
- π’ Enterprise Ready: SOC2 compliant, GDPR ready, with dedicated support
- π Open Source: Full source code available for customization and self-hosting
Perfect for trying out MCP servers or integrating with AI tools like Claude Desktop.
Available Images:
ghcr.io/klavis-ai/{server-name}-mcp-server:latest
- Basic serverghcr.io/klavis-ai/{server-name}-mcp-server:latest
- With OAuth support
π Browse All Docker Images β
# Example: GitHub MCP Server
docker run -p 5000:5000 ghcr.io/klavis-ai/github-mcp-server:latest
# Example: Gmail with OAuth (requires API key)
docker run -it -e KLAVIS_API_KEY=your_key \
ghcr.io/klavis-ai/gmail-mcp-server:latest
Clone and run any MCP server locally (with or without Docker):
git clone https://github.com/klavis-ai/klavis.git
cd klavis/mcp_servers/github
# Option A: Using Docker
docker build -t github-mcp .
docker run -p 5000:5000 github-mcp
# Option B: Run directly (Go example)
go mod download
go run server.go
# Option C: Python servers
cd ../youtube
pip install -r requirements.txt
python server.py
# Option D: Node.js servers
cd ../slack
npm install
npm start
Each server includes detailed setup instructions in its individual README.
Use our managed infrastructure - no Docker required:
pip install klavis # or npm install klavis
Service | Docker Image | OAuth Required | Description |
---|---|---|---|
GitHub | ghcr.io/klavis-ai/github-mcp-server |
β | Repository management, issues, PRs |
Gmail | ghcr.io/klavis-ai/gmail-mcp-server:latest |
β | Email reading, sending, management |
Google Sheets | ghcr.io/klavis-ai/google_sheets-mcp-server:latest |
β | Spreadsheet operations |
YouTube | ghcr.io/klavis-ai/youtube-mcp-server |
β | Video information, search |
Slack | ghcr.io/klavis-ai/slack-mcp-server:latest |
β | Channel management, messaging |
Notion | ghcr.io/klavis-ai/notion-mcp-server:latest |
β | Database and page operations |
Salesforce | ghcr.io/klavis-ai/salesforce-mcp-server:latest |
β | CRM data management |
Postgres | ghcr.io/klavis-ai/postgres-mcp-server |
β | Database operations |
... | ... | ... | ... |
And more! π View All 50+ Servers β | π³ Browse Docker Images β
For existing MCP implementations:
Python
from klavis import Klavis
klavis = Klavis(api_key="your-key")
server = klavis.mcp_server.create_server_instance(
server_name="YOUTUBE",
user_id="user123",
platform_name="MyApp"
)
TypeScript
import { KlavisClient } from 'klavis';
const klavis = new KlavisClient({ apiKey: 'your-key' });
const server = await klavis.mcpServer.createServerInstance({
serverName: "Gmail",
userId: "user123"
});
OpenAI Function Calling
from openai import OpenAI
from klavis import Klavis
klavis = Klavis(api_key="your-key")
openai = OpenAI(api_key="your-openai-key")
# Create server and get tools
server = klavis.mcp_server.create_server_instance("YOUTUBE", "user123")
tools = klavis.mcp_server.list_tools(server.server_url, format="OPENAI")
# Use with OpenAI
response = openai.chat.completions.create(
model="gpt-4o-mini",
messages=[{"role": "user", "content": "Summarize this video: https://..."}],
tools=tools.tools
)
π View Complete Examples β
Perfect for individuals and businesses who want instant access without infrastructure complexity:
- π Instant Setup: Get any MCP server running in 30 seconds
- π OAuth Handled: No complex authentication setup required
- ποΈ No Infrastructure: Everything runs on our secure, scalable cloud
- π Auto-Scaling: From prototype to production seamlessly
- π Always Updated: Latest MCP server versions automatically
- π° Cost-Effective: Pay only for what you use, free tier available
from klavis import Klavis
# Get started with just an API key
klavis = Klavis(api_key="your-free-key")
# Create any MCP server instantly
gmail_server = klavis.mcp_server.create_server_instance(
server_name="GMAIL",
user_id="your-user-id",
platform_name="MyApp"
)
# Server is ready to use immediately
print(f"Gmail MCP server ready: {gmail_server.server_url}")
π Get Free API Key β | π Complete Documentation β
Some servers require OAuth authentication (Google, GitHub, Slack, etc.). OAuth implementation requires significant setup and code complexity:
# Run with OAuth support (requires free API key)
docker run -it -e KLAVIS_API_KEY=your_free_key \
ghcr.io/klavis-ai/gmail-mcp-server:latest
# Follow the displayed URL to authenticate
# Server starts automatically after authentication
Why OAuth needs additional implementation?
- π§ Complex Setup: Each service requires creating OAuth apps with specific redirect URLs, scopes, and credentials
- π Implementation Overhead: OAuth 2.0 flow requires callback handling, token refresh, and secure storage
- π Credential Management: Managing multiple OAuth app secrets across different services
- π Token Lifecycle: Handling token expiration, refresh, and error cases
Our OAuth wrapper simplifies this by handling all the complex OAuth implementation details, so you can focus on using the MCP servers directly.
Alternative: For advanced users, you can implement OAuth yourself by creating apps with each service provider. Check individual server READMEs for technical details.
Resource | Link | Description |
---|---|---|
π Documentation | docs.klavis.ai | Complete guides and API reference |
π¬ Discord | Join Community | Get help and connect with users |
π Issues | GitHub Issues | Report bugs and request features |
π¦ Examples | examples/ | Working examples with popular AI frameworks |
π§ Server Guides | mcp_servers/ | Individual server documentation |
We love contributions! Whether you want to:
- π Report bugs or request features
- π Improve documentation
- π§ Build new MCP servers
- π¨ Enhance existing servers
Check out our Contributing Guide to get started!
MIT License - see LICENSE for details.
π Supercharge AI Applications
Get Free API Key β’ Documentation β’ Discord β’ Examples