Kerno Portal MCP
Connect your coding agent to the Kerno portal and ask it about coverage, runs and audits.
The Kerno Portal MCP server lets your coding agent read the same figures the portal shows. Ask it about coverage, test runs and audits without leaving your editor.
It is a separate server from the Kerno MCP that runs on your machine. Kerno MCP drives testing in a repository. The Portal MCP reads your organization's results from the portal, and every tool on it is read-only.
Connect
The server URL is:
https://mcp.kerno.io/mcpThe portal gives the same setup under Settings → MCP Server.
claude mcp add --transport http kerno-dashboard https://mcp.kerno.io/mcpAdd to ~/.cursor/mcp.json:
{
"mcpServers": {
"kerno-dashboard": {
"url": "https://mcp.kerno.io/mcp"
}
}
}Add to .vscode/mcp.json:
{
"servers": {
"kerno-dashboard": {
"type": "http",
"url": "https://mcp.kerno.io/mcp"
}
}
}Any other MCP client that supports remote servers over HTTP works the same way.
Approve access
The first time your agent connects, it opens your browser to sign in to Kerno and approve the client. The approval page lists what the client can read:
Your test coverage and entry points.
Your test runs and their results.
Your repositories and their sync state.
Your code audit history.
The client can read every organization you belong to. It can't change anything, see billing, or manage members. The portal asks for approval again each time a client connects.
You need to belong to an organization before you can approve a client.
Use an API key
For a script or a CI job with no browser, pass an API key as a bearer token:
Create the key in the portal under Settings → API Key. A key belongs to one organization, so tools called with it read that organization, and you can leave organizationId out.
Tools
Signed in through the browser, pass organizationId to every tool except list_organizations. Call list_organizations first to find it.
Coverage figures read the default branch, and stay empty until the Kerno GitHub Action has synced it. Run figures count the newest branch each repository last ran on, across the IDE, the CLI, MCP and CI.
list_organizations
The organizations this credential can read.
None.
list_repositories
Every repository Kerno knows about, with flow and entry point coverage, run count and last run. Repositories that have never run are listed as awaiting.
organizationId, period
get_overview
The six figures on the portal's Analytics page, with the previous period for comparison.
organizationId, period, gitRepo
list_entry_points
Every entry point Kerno discovered, and whether it's covered.
organizationId, gitRepo
list_flows
Every user flow Kerno discovered, and whether it's covered.
organizationId, gitRepo
list_runs
Completed runs, newest first.
organizationId, gitRepo, withDiffsOnly, from, size
get_run
One run in full, as the Runs page shows it.
organizationId, runId (required)
list_audit_repositories
Repositories with a kerno audit run stored.
organizationId
get_audit
The latest audit of a repository, with the metric catalog and the run's values.
organizationId, gitRepo (required), plugin
get_audit_series
One audit metric across the window the audit covered.
organizationId, runId (required), metricKey
get_audit_quality
The repository's Quality score for Period B against Period A, with its three pillars and grade.
organizationId, gitRepo (required), periodA, periodB
Arguments
organizationId
string
Organization to read. Required when signed in through the browser. An API key is bound to its organization, so it can be left out.
period
7d, 30d or 90d
Window the figures cover. Defaults to 30d.
gitRepo
string
Repository, as owner/name. Optional on coverage and run tools, where it narrows the result to one repository.
withDiffsOnly
boolean
Only runs that found a difference. Defaults to false.
from
integer
Offset into the list of runs. Defaults to 0.
size
integer
How many runs to return, from 1 to 100. Defaults to 20.
runId
string
A run id. For get_audit_series, the audit run id from get_audit.
plugin
string
Only this audit plugin's metrics, such as complexity.
metricKey
string
The audit metric to read. Leave it out for every series in the run.
periodA, periodB
string
Periods as YYYY-MM-DD..YYYY-MM-DD. Send both or neither. Period A must end before Period B starts. Without them, the tool uses the same default periods as the portal.
A repository with no audit returns an empty result with a reason, so your agent can tell you to run kerno audit there.
Example prompts
"Which of my repositories have the lowest entry point coverage?"
"Show me the runs from the last week that found a difference."
"What's the audit quality score for owner/repo, and which pillar moved most?"
"How did the rework rate change month by month in the latest audit of owner/repo?"
See Kerno Audit and Portal overview.
Last updated