Give your own agents what Certant knows

Claude Code and other MCP clients can ask your knowledgebases, query your data and run your agents, under a key you issue.

Included on Business and Enterprise plans and every dedicated and sovereign deployment.

Claude Code, connected to CertantExample

Which of our projects mention cyanobacteria? Then run the portfolio agent and tell me what changed.

set_knowledgebase ask_knowledgebase run_agent get_agent_run
Reply

Fourteen projects mention cyanobacteria, the latest in 2022. The portfolio agent ran and added two new reports to the research dashboard.

Project 1190 · page 9 Agent run completed

Each tool call runs under the key Claude Code was given.

What it opens up

Work from the agent you use

Your agent connects to Certant and gets tools for each part of the platform. It sees one group of tools at a time and switches group when the job changes, which keeps the list short enough to use well.

Ask your knowledgebases

Questions come back answered from your documents, with the page each part came from.

ask_knowledgebasesearch_knowledgebasefind_text
Query live data

Strata turns the tables in your documents and feeds into data your agent can explore and query in plain English.

Explore modequery_data
Build and run agents

Your agent can lay out a workflow with the Agent Builder's nodes, test it, save it and run it.

test_runsave_workflowrun_agent
Set watches on your data

Monitors check your data for thresholds and gaps and start the action you chose when one trips.

Monitors and actions mode
Load and manage documents

Upload documents, check how processing is going and run connector syncs on a schedule.

upload_documentget_ingest_statusrun_sync_now
Check usage and credits

Bring your usage and credit balance into the conversation before a big job starts.

get_usageget_credit_balance
Keys and approvals

Decide what each agent may do

Every connection uses a key that a person issued, with scopes that say what it may touch. Anything that changes live data waits for a person to approve it.

Scoped keys. A key opens only the routes its scopes allow, and a read-only key can read and nothing more. You can revoke a key at any time.
Approval for live changes. Draft changes go to a branch. Changes to live data, or anything with an effect outside Certant, wait in the approvals queue until a person signs them off.
Calls run as a person. Each call runs as the user who owns the key and is metered to their account, so you can see who asked for what.
ApprovalsExample
Waiting for approval

Turn on the monitor "New report with no attachment" and email the library team when it trips.

Asked by Claude Code, using a developer's key
Scope Strata draft
Effect Sends email outside Certant
ApproveDecline

Nothing changes in live data until someone presses Approve.

Built in

The AI FDE uses the same tools

The AI FDE is the assistant inside Certant. It calls the same tools as the MCP server, from inside the platform, under a short-lived key that drafts changes and sends live ones for approval.

On a sovereign deployment the FDE runs on open models on your own GPUs, Qwen3.6 35B or GPT-OSS 120B. The assistant, its tools and your data all stay on your hardware, air-gapped if you need it.

Its model list is limited to open models you can host yourself, which keeps its work inside your environment.

See the AI FDE

Two ways to reach the same tools
Inside Certant, on your models
AI FDE Certant tools Your knowledge and data
Your own agent, over MCP
Claude Code Certant MCP server Certant tools

Both clients pass the same key, scope and approval checks.

For your IT team

What your engineers will ask about

SettingDetail
ClientsClaude Code, Hermes, OpenClaw, NemoClaw and any other MCP client.
Transportstdio, generally available, with one container per session. SSE in beta for remote agents.
DirectionInbound only. Your agent connects in, and the server holds no OpenAI or Anthropic credentials.
KeysPer-user keys, stored as a hash. Scopes cover workflow authoring, running and admin, read-only access, and Strata read, draft and commit.
Tool groupsTwelve modes: six for Strata and agent building, and six for knowledge, chatbots, agent operations, data sources, dashboards and account. The agent sees the current mode's tools unless you list them all.
ResultsEvery tool returns the same JSON shape: a summary, the data, and errors that each carry a hint for fixing the call.
VersioningThe server image is pinned to your platform release.
ExtrasWorkflow and Strata primers as MCP resources, and skill bundles that Claude Code loads directly.
Questions

Before you connect an agent

Which plans include the MCP server?

The Business and Enterprise plans, and every dedicated and sovereign deployment. The Free trial, Starter and Pro plans use Certant through its own interface.

What does my agent's model provider see?

Your agent's provider sees what your agent asks Certant and what comes back, as with any other tool the agent uses. Give the key only the scopes and knowledgebases the job needs.

Can it all run inside our network?

The MCP server and the AI FDE can. On a sovereign deployment both run inside your network, and the FDE uses your own models. An outside agent such as Claude Code still needs its own connection to its model provider.

How do we connect Claude Code?

Create a scoped key under Settings, then add the Certant server to Claude Code's MCP configuration. The server runs as a container pinned to your platform version.

Connect your agent to Certant

Book a demo and see Claude Code work with a knowledgebase built from your own documents.

Certant Cloud, your cloud, or fully air-gapped.

What a tool returnsExample
{
  "ok": true,
  "tool": "ask_knowledgebase",
  "summary": "Answered from 3 documents",
  "errors": [],
  "data": {
    "answer": "Three projects measured blooms…",
    "citations": [
      { "document": "Project 1047 final report",
        "page": 31 }
    ]
  }
}