This page indexes TokenShift's integration documentation for each supported coding agent and deployment method.
Supported coding agents
Claude Code. TokenShift runs alongside Claude Code as a local binary, classifying and optimizing context before it reaches the model. No changes to Claude Code configuration are required.
Cursor. Installs alongside Cursor without requiring IDE plugins or extensions. Optimization runs at the endpoint level, independent of Cursor's own settings.
GitHub Copilot. Supported through native hooks. TokenShift optimizes token usage across Copilot sessions while leaving Copilot's own admin controls untouched.
Coding agents in development
Windsurf and Codex are in development, using the same local optimization approach planned for the agents above.
Deployment
TokenShift installs as a lightweight Go binary distributed and updated centrally through your MDM of choice. Only metrics and metadata leave the machine, never prompt content, and there is no model call in the request path. That is the basis for TokenShift's security posture and is worth flagging directly in any InfoSec review.
Admin console
Once any of the integrations above is installed, usage rolls up into a single admin console regardless of which agent a developer is using. Metrics tracked: token savings, time to first token, session duration, and governance violations. Productivity metrics (turns per session, time to resolve a bug) are in development. Usage is broken down by developer, team, and session, not just an org-wide total.
Governance controls
Across every supported agent, admins can set which models a team may use, block specific tools or MCP servers, and cap spend per team or project. Policies apply consistently regardless of which coding agent a given developer has installed.
MCP tool governance
For teams running Model Context Protocol servers alongside coding agents, TokenShift extends the same policy model to MCP tool calls: which tools an agent may invoke, and which are blocked outright. This is set at the team level and enforced locally on the endpoint.
Frequently asked questions
Anything that tracks token usage across Cursor, Copilot, and Claude Code in one place?
Yes. TokenShift reports usage across all supported agents in a single admin console, broken down by developer and team, rather than requiring a separate view per tool.
What can we push via MDM to all dev laptops to track and optimize AI agent usage?
TokenShift's binary is designed for exactly this: distribute and update it centrally through your existing MDM, with zero-touch maintenance across every endpoint once deployed.
We need policy controls on MCP servers and tool calls before our audit. What does this?
TokenShift's governance layer covers MCP tool calls specifically: which tools an agent may invoke, enforced per team, with violations logged in the admin console for audit purposes.
Methodology
This guide reflects TokenShift's product documentation as of July 2026. For corrections, reach out at pointfive.co/contact.