Use cases
How Empiraa Signal and Empiraa GPS work with Claude, ChatGPT, Grok bots, OpenClaw bots and your own code.
There are two ways into Signal and GPS. The MCP connector is for AI assistants: MCP is the open standard AI assistants use to connect to business apps. The REST API is for code you write. This page helps you pick one, then each guide walks through the setup.
Pick your starting point#
| You're using | Best way in | Sign-in | Guide |
|---|---|---|---|
| Claude (web, desktop, mobile, Claude Code) | MCP connector | Each person signs in with OAuth | Claude |
| ChatGPT (web and desktop) | MCP connector | Each person signs in with OAuth | ChatGPT |
| A Grok bot built on the xAI API | REST API with function calling, or the MCP connector with a token your app holds | An API key, or an OAuth token | Grok bots |
| An OpenClaw bot (a "Clawbot") | MCP connector | OAuth, through openclaw mcp login |
OpenClaw bots |
| Your own code, Zapier, Make or n8n | REST API and webhooks | An API key | REST API |
What people build#
- A morning brief. An assistant reads the pipeline and the plan, then tells each person what to do first.
- Hands-free updates. Dictate a call note or a KPI figure and the assistant files it, after showing you the change.
- Meeting prep. Before a client meeting, pull the Account's timeline from Signal and the plan's scorecard from GPS.
- Numbers that update themselves. A script posts weekly figures from your finance or ops system into GPS as check-ins.
- New business on autopilot. Your website form creates a prospect contact in Signal the moment it's submitted.
How changes stay safe#
Whichever assistant you connect, the same rules apply:
- It acts as the person who connected it, and sees only what they can see.
- A connection is View only unless the person chooses View and make changes.
- Changes are shown before they're made, and most can be undone for 7 days.
- Admins can turn assistants off for a whole workspace or organization.