Itential MCP v0.14.0: Know What Your Agents Cost, Govern What They Touch

Your Agents Are in Production. Do You Know What They’re Doing?

Your FlowAgents are live, running inside the Itential Platform and acting through Itential Gateway, direct API calls, and platform workflows. External AI clients, Claude, ChatGPT, Copilot, or anything else that speaks MCP, reach that same platform through the Itential MCP server, Itential’s implementation of the Model Context Protocol, the open standard that lets AI agents call tools (or other agents, i.e. FlowAgent) safely. That’s the win. AI agent governance is the part most teams haven’t caught up to yet.

Here’s the question most teams can’t answer: how many tokens did last week’s agent sessions actually burn, and which ones ran long for no good reason? And when you need to move a gateway’s configuration from staging to production, are you doing that by hand, or does your platform actually support it?

Itential MCP v0.14.0 answers both. It adds agent token-usage analytics, governed configuration export and import, and closes out a tool-surface hardening effort that touches all 77 tools in the server. None of it is flashy. All of it is the kind of thing that matters the moment agents stop being a pilot and start being an operating model.

Read the full changelog on GitHub, or jump straight to the release: itential/itential-mcp v0.14.0.

Agent Token-Usage Analytics

Three new tools land in agent_session_manager:

• get_agent_token_usage
• get_agent_session_token_usage
• describe_session_token_usage

“It worked” was never the only question that mattered for an agent running in production. Token consumption is a real budget line now, and until this release, there wasn’t a native way inside Itential MCP to see it. These three tools give you usage at the agent level and the session level, so you can answer the questions that actually come up: which agents are the expensive ones, which sessions ran unusually long, and where reasoning cost is quietly creeping up before it shows up as a surprise on an invoice.

Agent sprawl without cost visibility is just script sprawl with a bigger bill.

Governed Configuration Export & Import

gateway_manager, the interface to Itential Gateway, picks up export_gateway_configuration and import_gateway_configuration, giving you a real way to move a gateway’s configuration between environments instead of re-entering it by hand and hoping nothing gets missed.

In enterprise AI agent governance, the moment secrets leave a system is the moment a review is non-negotiable. Gateway configurations can carry secrets and credentials, and that’s exactly where this release doesn’t cut corners. Exporting a configuration that contains sensitive data now triggers an MCP elicitation confirmation gate that prompts for explicit confirmation before the export runs. An agent can’t quietly walk off with credentials because it decided exporting configuration was the next logical step. A human confirms it first.

Same rule that governs every other action on the platform: humans hold the gate, agents do the work.

A Hardened, Fully Annotated Tool Surface

Every tool across the server, all 77 of them, now carries standard MCP tool annotations: readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, plus a human-readable title and deterministic discovery and registration order.

This is the difference between a tool list and a tool contract. A client or agent framework that respects these hints can reason about which calls are safe to make automatically and which ones need a confirmation step, before it ever calls the tool. Deterministic ordering means the tool surface an agent sees is stable and predictable across restarts and environments, not a shuffled list that changes call to call.

This isn’t a one-time cleanup. New CI guards in tests/utilities/test_tool.py now enforce annotation completeness and safety invariants on every tool going forward, so the standard holds as the server keeps growing.

SSE Transport: Time to Plan Your Move to HTTP

Starting the server with --transport sse now prints a one-time runtime deprecation warning, and the README, CLI help, and docs all steer new deployments toward http. SSE remains fully functional and wire-compatible in this release, nothing breaks today, but if you’re standing up a new environment, build it on HTTP transport from the start.

MCP Server Security & Fixes Worth Knowing About

A few items from this release are worth flagging even though they’re not headline features:

• Configuration precedence, restored: environment variables and CLI flags now correctly override config-file values again, across all 39 affected ServerConfig, AuthConfig, and PlatformConfig fields. If you set an env var override expecting it to win and it silently didn’t, this release fixes that.
• Config-file auth keys parse correctly: a global string replace was mangling documented [server] auth_* keys, including oauth_* fields. Fixed.
• Cryptography advisories cleared: the cryptography package is lifted to >=50.0.0,<51, resolving three previously-held high-severity advisories plus GHSA-537c-gmf6-5ccf. As of this release, Itential MCP has zero open Dependabot advisories.
• Python 3.14 added to the CI test matrix, 3.10 through 3.14 all covered. The supported floor stays at 3.10.
• New deployment guidance: docs/deployment.md covers platform connectivity and deployment patterns.

The full list, including every dependency bump and smaller fix, is in the CHANGELOG.

Upgrading

Pull the latest release from PyPI:

pip install -U itential-mcp

Or with uv:

uv tool upgrade itential-mcp

Running the container image? Bump the tag to v0.14.0 and redeploy.

What’s Next

Itential MCP is open source and moving fast, roughly a release every two to three weeks this year. As a foundation for MCP server workflow automation across the Itential Platform, it’s still adding capability every cycle. If you’re running agents against it in production, the token-usage tools and the config export/import gate in this release are worth adopting now, not later. If you hit something that doesn’t work the way it’s documented, open an issue. The repo is public and the roadmap is shaped by what practitioners actually run into.

📥 Download the latest version → 

🔌 Learn more about Itential MCP →