Kernax
Pricing → For Teams → CLI → Security → Docs → Blog →
Request Beta Access →
Docs / Configuration / MCP Servers

MCP Servers

Connect external databases, APIs, CLI tools, and web services to your Kernax agent using the open Model Context Protocol.

The Model Context Protocol

The Model Context Protocol (MCP) is an open industry standard that enables AI models to safely interact with external tools, databases, APIs, and developer environments through standardized client-server interfaces.

Kernax features full native support for MCP as a first-class client. Instead of writing brittle custom API integrations, you can plug in any community or enterprise MCP server in seconds.

Configuring .kernax/mcp.json

Kernax automatically discovers MCP servers declared in your workspace's .kernax/mcp.json or global user directory (~/.kernax/mcp.json):

.kernax/mcp.json
{
  "mcpServers": {
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres", "postgresql://localhost/mydb"]
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxxxxxxxxxxx"
      }
    }
  }
}

1-Click Pre-Configured Servers

In the Kernax Settings menu (or by typing @mcp in chat), you can enable popular enterprise servers with zero manual configuration:

Server Transport Capabilities Provided
PostgreSQL stdio Inspect schemas, explain queries, query live tables, audit indexes
GitHub stdio Create pull requests, read issues, inspect remote git diffs
Brave Search stdio Execute real-time web lookups for updated framework documentation
Figma SSE / HTTP Extract component design tokens and generate pixel-perfect React code
Memory stdio Knowledge graph persistence across multi-day engineering sessions

Custom stdio & SSE Transports

Kernax supports both local subprocess (stdio) and remote streaming (Server-Sent Events / SSE) transports:

Was this page helpful?
Esc