Put your pipeline and your plan inside every assistant.
REST APIs and webhooks for the code you write. MCP connectors for Claude, ChatGPT and the bots your team already runs.
Every page is also available as Markdown for AI coding tools.
- OpenAPI specs for both APIs
- Webhooks for both products
- MCP connectors with OAuth 2.1
Works with the tools your team already uses
Claude
ChatGPT
Zapier
n8n
Make
Grok bots
OpenClaw botsClaude Code
Cursor
VS CodeYour own codeHow it fits together
Every assistant and every script reaches the same two products.
Signal and GPS sit in the middle. Whatever you work in connects to them one of two ways.
- MCP connectorFor assistants. Each person signs in with OAuth 2.1, the assistant acts as them, and changes are previewed first.
- REST API and webhooksFor code. An API key with scopes acts as the workspace or organization.
ClaudeChatGPTZapierGrok botsn8nOpenClawCursor
Automation
Set it up once. Then it runs itself.
Three automations teams build first. Pick one and watch each step run.
Use cases
Works with the assistants and bots you already use.
A guide for each: what it can do, how to set it up, and how to keep it safe.
Claude
Add both connectors in about a minute each, then ask for your Morning Brief or what is off track in the plan.
MCP connectorRead the guideChatGPT
Turn on Developer mode, add the connectors, and ChatGPT reads and updates Signal and GPS as you.
MCP connectorRead the guideGrok bots
Give a bot on the xAI API your pipeline and plan, through function calling or the connector.
REST API or MCPRead the guideOpenClaw bots
Sign an always-on Clawbot in with OAuth so it can brief you, prep meetings and chase check-ins.
MCP connectorRead the guideZapier, Make, n8n and your code
Call the REST APIs from your stack or your automation tool, and listen for webhooks.
REST APIRead the guidePlayground
Test it before you ship it.
Every check says whether it will work, and what to change if it won't.
Prompt library
Don't know what to ask? Start with these.
Copy-and-paste prompts for both products, each with the tools it uses.
Who to call first
Who are my 10 hottest prospect contacts right now? For the top 3, explain why each one scored so high and suggest an opening line for the call.
What's off track
What's off track in our plan? List each Goal and Objective that's behind, who owns it, and how far off target it is.
One morning brief
Give me one morning brief. From Signal: what to do first and which Deals are at risk. From GPS: what I should focus on this week and what is off track in the plan. Keep it to one screen.
Two products
Pick a product, then pick a way in.
The CRM for sales and marketing teams: Accounts, Contacts, prospect contacts, Deals, Actions, Bookings, Campaigns and analytics.
MCP connector URL
https://crm.empiraa.app/mcp
The business operating system where teams set Goals, track the Objectives that measure them, and run the Actions and meetings that move them.
MCP connector URL
https://plan.empiraa.app/mcpBuilt for developers
The details that save you an afternoon.
One OpenAPI file per API
Generate a client, load it into your API tool, or browse every endpoint in the explorer.
Preview before every change
Assistants show what will change first. Most changes can be undone for 7 days.
Search everything
Pages, endpoints and all 161 connector tools, from any page.
API or MCP?
Two ways in, built for different jobs.
| REST API | MCP connector | |
|---|---|---|
| Use it for | Integrations, syncs, scripts and internal tools you write | Working in Signal or GPS from an AI assistant |
| Sign-in | An API key | The person signs in with OAuth and approves the connection |
| Who it acts as | The workspace or organization that owns the key | The person who connected |
| Changes | Direct calls | Confirmed by the person in their assistant app, attributed to them, and undoable for 7 days where the product allows |
Questions
The answers developers ask for first.
Should I use the REST API or the MCP connector?
Use the REST API when your own code or an automation tool makes the calls. Use the MCP connector when a person works in Signal or GPS from an AI assistant such as Claude or ChatGPT.
Do I need an API key for the connector?
No. Each person signs in with their own Signal or GPS account and approves the connection.
Will an assistant change things without asking?
Changes are shown first. In Signal, every change is previewed as a card and your assistant app asks before applying it. In GPS, batches are previewed first.
My agent needs a restart every time the token rotates. How do I avoid that?
Keep the tokens in one store owned by a small broker, and have each agent ask it for the current access token at call time. Headless agents and token refresh has the pattern.
Start building