Use Yawp inside Claude or ChatGPT.

How do I connect from Claude?

In Claude (web or desktop): Settings → Connectors → Add connector, and give it this URL:

Claude opens a sign-in window; approve the connection and you are done. If you don't have a Yawp account yet, you can create one during that sign-in — finish the short setup at app.getyawp.ai afterwards so your assistant has what it needs.

In Claude Code, one command does the same:

How do I connect from ChatGPT?

In ChatGPT: Settings → Connectors → Add connector (in some workspaces this lives behind developer mode), then paste the same URL:

ChatGPT walks you through the OAuth sign-in. Yawp asks for nothing beyond your Yawp account — no ChatGPT data leaves the conversation except what you explicitly send to your assistant.

What should I try first?

An email errand works the moment you connect — it needs no phone number. Paste this and change the details:

Phone calls need a Yawp phone number first — activate one under Settings → Phone number in the dashboard. Then:

How do approvals work?

Nothing reaches a real person without your say-so. When Yawp drafts a call or an email, it queues the exact thing it wants to do, and the draft waits for you. In ChatGPT — and anywhere else without inline approval forms — you approve by reading an 8-digit approval code from your Yawp dashboard and giving it to the assistant. The code lives only on the dashboard, so a confused (or manipulated) AI can never approve its own work: only you can read it.

In Claude Desktop with an API-key connector, you can enable inline approval instead: the key setting Allow inline approvalon the dashboard's Integrations page shows approve/deny forms right in the conversation — a form only you can click.

Which tools does the connector expose?

Everything is scoped to your workspace; reads are reads, and anything that touches the outside world is gated behind the approvals above.

• run_agenttalk to your assistant in free form
• request_callplace one outbound phone call
• list_pending_callslist calls waiting for your approval
• get_call_statuscheck how a call is going
• wait_for_callwait for a call to finish and get the outcome
• approve_callapprove a queued call (needs your approval code)
• deny_callcancel a queued call
• list_pending_emailslist email drafts waiting for approval
• get_email_statusread the exact draft before it sends
• approve_emailapprove a draft (needs your approval code)
• deny_emaildiscard a draft
• create_taskdelegate a multi-day errand
• confirm_taskconfirm and start an errand
• amend_taskchange a running errand's limits or deadline
• get_task_statuscheck an errand's progress
• list_taskslist your errands
• answer_taskanswer a question the errand raised
• cancel_taskcancel an errand

I'm in multiple workspaces (or have multiple assistants)

The OAuth connector supports the common shape: one account, one workspace, one assistant. If your account spans several workspaces — or a workspace runs several assistants — the connector refuses with a clear message instead of guessing which one you meant. Connect the specific one you want with its per-workspace API-key URL instead, copied from the dashboard's Integrations page (it looks like https://api.getyawp.ai/mcp/agents/<assistant>).

Troubleshooting

• “This authorization is no longer valid” — disconnect and reconnect the connector; your sign-in was revoked or expired.
• “No Yawp workspace yet” — finish account setup at app.getyawp.ai, then reconnect.
• “No phone number configured” — calls need a Yawp number: dashboard → Settings → Phone number. Email errands work without one.
• “Token verification is temporarily unavailable” — a hiccup on our side; retry in a minute. Your connection is fine.
• Connected but no tools listed — remove the connector and add it again with the exact URL above.

Is my data safe?

Every outbound message and call discloses that Yawp is an assistant acting for a named person — see how Yawp works for what recipients are told. What Yawp stores and why is in the privacy policy. Questions or trouble connecting: [email protected].