For the apps you build with AI
You build the app. We host the display. TickrMeter is a ready-made e-ink display for the signals your app produces. Create its layout with your AI coding assistant, then push your data. TickrMeter handles the rendering.
Your code just got a desk job.
Keep building the app you had in mind
You have a working idea: a little status tool, a daily counter, a tracker for something that matters to you. Giving it a physical display can turn into a second project involving a board, display drivers and firmware.
TickrMeter gives you finished display hardware and hosts the display app for you. Your code sends the values; TickrMeter turns them into a screen. Work on the useful part of your app. The electronics already have a home.
Connect. Describe. Preview.
1. Connect your coding assistant
MCP (Model Context Protocol) lets a compatible AI assistant use TickrMeter’s tools. Follow the guide in the TickrMeter app to connect your client and authorize access. The supported flows include clients such as Claude, Cursor and Codex; use the current instructions for yours.
2. Tell it what belongs on your desk
Start with one useful signal and ask for a TickrMeter-hosted display. Your assistant can help create a layout and the code or workflow that supplies its values. You can continue editing a hosted layout in the visual builder.
3. Check it, then choose your TickrMeter
Review the preview, connect the real source and check the values. When you’re happy with the result, choose the device and press Send to TickrMeter. The first time, check the physical screen too. That’s the satisfying bit.
Start with a prompt like this
Create a TickrMeter-hosted display for my app. Show its name, a large status and when the status was last checked. Use clearly labelled sample data in a separate test display for the first preview. Keep the layout editable. Then help me connect the real status source and run its updater in the live setup. Show me the preview before we choose a device.
This is a starting prompt. Your app’s data source, permissions and updater still need to be connected. Your assistant can help with that work.
A few good reasons to look up from your laptop
- Did it ship? Give your deployment or build workflow a visible status.
- Is it working? Display a recent health check from your app or existing monitor.
- Are we getting there? Keep a daily count or progress toward a goal in sight.
- Has the job finished? Let a background process send a completion signal.
These are ideas for custom projects. Pick a source your code can access, then send the values that make the display useful.
Just send the data. We’ll put it on the display.
Once your layout and device are set up, your app, script or automation sends values to TickrMeter. We host the display app and render those values using your saved layout. You don’t need to run a public image server or write custom device firmware for this route.
Keep the updater running wherever your app or automation lives. Once it’s running there, you can close the AI chat and keep the data coming. The hosted quickstart explains how values reach the display.
Use e-ink for information you want to glance at. It shows snapshots, and source updates and physical refreshes have their own timing. Include a last-checked value when freshness matters, and choose data suitable for the documented display privacy model.
Pick your next step
- Connect your AI coding assistant with MCP and create your first editable display.
- Put your app’s build status on your desk with a small data push from your workflow.
- Compare a dev kit and a ready-made display for the project you want to build.
Bring your next idea to the desk
To use the MCP route, you’ll need a TickrMeter, an account, a compatible AI client and a source for your data. Client subscriptions and source-service costs depend on the tools you choose.
Already own a TickrMeter? Open Apps & setups and start a hosted custom display. Prefer to write the integration directly? The developer docs cover the API and other supported routes.