Ikizen runs an MCP server. Point Claude Code, Codex, Cursor or any other MCP client at it, and you can tell your agent to block a site for the afternoon, add a goal, or log a set of pull-ups without opening Ikizen.
Agents work on your synced setup, so agent access is part of the paid plan, next to sync and the companion app.
In the extension, open Settings > Agents and create a token. Leave “Allow changes” on if the agent should edit your setup, off if it should only read. The token is shown once, with the setup lines below already filled in. You can revoke it there at any time.
Claude Code
claude mcp add --transport http ikizen https://api.ikizen.app/mcp \ --header "Authorization: Bearer ikz_..."
Codex
export IKIZEN_TOKEN=ikz_... codex mcp add ikizen --url https://api.ikizen.app/mcp --bearer-token-env-var IKIZEN_TOKEN
Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ikizen": {
"url": "https://api.ikizen.app/mcp",
"headers": { "Authorization": "Bearer ikz_..." }
}
}
}Any other client that speaks MCP over HTTP works the same way: the URL above, with the token as a bearer header.
Apps that add MCP servers as custom connectors sign you in instead of asking for a token. Add a connector with the URL https://api.ikizen.app/mcp, sign in with your Ikizen account when asked, and choose whether to allow changes. The connection then appears in Settings > Agents, where you can disconnect it.
Changes reach your browser the next time you open a new tab (an open dashboard updates straight away) and your phone on its next refresh.
By default an agent cannot make any site easier to reach. Removing a block, shortening its hours, softening its bypass or switching a protection off is refused, and the agent is told to send you to the extension. A block your agent can be talked out of at 11pm is no block.
If you want your agent to handle that too, turn on “Let agents loosen blocks” in Settings > Agents. It applies at once, and you can turn it off again the same way. An agent cannot change this switch.
Tokens start with ikz_ and are stored only as a hash, so we cannot show one again. A token reaches your Ikizen setup and nothing else: not your password, not your account, and not the GitHub, Bitbucket or Todoist keys your widgets use. Connector sign-ins renew themselves hourly and stop working the moment you disconnect them. Deleting your account deletes its tokens.