Model Context Protocol server

Cronometer for Poke

A small bridge that lets Poke read your Cronometer nutrition log. It speaks MCP over Server-Sent Events, so you connect it once and ask Poke about any day’s calories and nutrients.

SSE endpoint
/api/mcp

Connect it to Poke

  1. 1

    Copy the SSE endpoint

    Grab the /api/mcp URL above. That single URL is everything Poke needs to talk to this server.

  2. 2

    Add it as an MCP server in Poke

    In Poke's integrations, add a new MCP connection and paste the endpoint as an SSE server. Poke opens the stream and discovers the available tools automatically.

  3. 3

    Ask about a day

    Try “What did my Cronometer log show on 2026-06-20?” Poke calls get_daily_summary and reads back the totals.

Available tool

get_daily_summary

Fetches the Cronometer daily nutrition summary - calories, macros, and micronutrient totals - for a single date.

Argument
datestring, required

The day to fetch, formatted as YYYY-MM-DD (for example, 2026-06-20).

Server setup

This server reads your Cronometer data using an API token held entirely on the server. Set it in the deployment environment before connecting:

CRONOMETER_API_KEY

Sent as a Bearer token on every request to the Cronometer API. It is never exposed to Poke or the browser.