Integrations Overview
Clevername connects your AI workflows to external tools and custom servers through the MCP (Model Context Protocol) gateway. This section covers every integration surface.
What is MCP?
The Model Context Protocol (MCP)is an open standard that lets AI models call external tools in a structured, auditable way. Clevername acts as a universal MCP gateway — you install servers once and every model you use (Anthropic, OpenAI, Google) can access them through a single endpoint.
Integration surfaces
- Integration directory — Curated catalog of MCP servers you can install in one click.
- Custom connections — Register your own HTTP MCP servers.
- IDE gateway — Expose all your tools to local IDEs via a single MCP URL and browser login.
- BYOK keys — Bring your own provider API keys for model routing.
Security model
All credentials (API keys, OAuth tokens, MCP server tokens) are encrypted at rest using AES-256-GCM or GCP Secret Manager. Tool access is governed by trust tiers, scoped gateway tokens, and optional Agent Review approval for enterprise deployments.
Integration guides
Browse, search, and install MCP servers from the curated integration directory.
BYOK API KeysAdd your own provider keys for OpenAI, Anthropic, Google, and more.
MCP ConnectionsRegister custom HTTP MCP servers with always-on or plugin injection modes.
IDE GatewaySingle MCP endpoint for Claude Code, VS Code, and Cursor with browser login.
Submitting a ServerSubmit your own MCP server to the integration directory for review and listing.
Config Import / ExportExport your MCP config for IDEs or import from claude_desktop_config.json.
Local LLMs (Ollama, vLLM, llama.cpp)Run models on your own hardware. BYOL keeps prompts on your network with full governance.
Hermes Tool-Call GovernanceGate every native and MCP-sourced tool call a Hermes profile makes through Clevername's guardrail engine.