Use Yawp inside Claude or ChatGPT.

How do I connect from Claude?

In Claude (web or desktop): Settings → Connectors → Add custom 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, add the connector with one command:

The command only registers Yawp — Claude Code signs in when you ask it to. Then run /mcp in Claude Code and choose Authenticate. A browser window opens for the same Yawp sign-in.

How do I connect from ChatGPT?

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

Paste the URL, leave the Client ID and Client Secret blank, then sign in.

ChatGPT walks you through the same Yawp sign-in Claude uses. You sign in with your Yawp account, and ChatGPT sends your assistant only what you ask it to.

ChatGPT identifies itself to Yawp on its own, so there is no Client ID to enter.

What should I try first?

An email task 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?

By default, calls and email wait for your approval. If you turn on trust mode for calls or autopilot for email, Yawp follows those settings. Under the default, 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.

Inline approval needs a client that sends your API key as a header — Claude Code, Cursor, or a script. Claude Desktop's key-in-URL connector keeps using the approval code. For a header-sending key, the setting Allow inline approval under the dashboard's Settings → API keys shows approve/deny forms right in the conversation — a form only you can click. With it on, review_pending_approvals walks you through everything already waiting, including items queued in an earlier conversation.

Which tools does the connector expose?

Everything is scoped to your workspace; reads are reads, and anything that touches the outside world follows the approval settings 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
• review_pending_approvalsgo through everything waiting for your approval in one pass (inline forms only)
• plan_taskhave Yawp turn your words into a plan for a task (sign-in connector only)
• answer_plananswer Yawp's questions about a plan, or have it redraft one (sign-in connector only)
• create_taskdelegate a multi-day task
• confirm_taskstart a task, or (sign-in connector only) the task a plan describes
• amend_taskchange a running task's limits, deadline or approach
• get_task_statuscheck a task's progress, or (sign-in connector only) a plan's, and how Yawp is going about it
• get_task_timelineread a task's full history — every call and email
• list_taskslist your tasks
• answer_taskanswer a question the task raised
• cancel_taskcancel a task
• list_factssee which standing facts your assistant has on hand — labels and sharing rules, never the values

I'm in multiple workspaces

The sign-in connector reaches one workspace at a time, and it never guesses which: if your account spans several, it refuses with a clear message until you tell it. Pick a default workspace on the dashboard's Integrations page, and the connector uses that one from its next request on — no reconnecting needed unless your client has already given up on the connection. You can change or clear it there at any time. If you would rather not set a default at all, connect with an API key instead: the key-based setup is under Advanced on that same page, in the workspace you want to connect.

Troubleshooting

• “This authorization is no longer valid” — disconnect and reconnect the connector; your sign-in was revoked or expired. (If the message says the app was disconnected from the workspace, see the next item — reconnecting will not help there.)
• “This app was disconnected from this Yawp workspace” — someone disconnected it on the dashboard under Settings → API keys → Connected apps. Reconnecting signs the same app in again and meets the same block. If you disconnected it yourself, press Allow again there; otherwise ask a workspace admin to. If the message adds that the connector reached the workspace because it is your default, you can also pick a different default workspace on Integrations to use one of your other workspaces from the next request on.
• “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 tasks 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].