WeCall365

DocsConnect, call, read

Connect Claude to WeCall365

Three commands in a terminal. After that, you ask Claude to make a call and it does.

Before you start

You need a WeCall365 API key. If you do not have one yet, sign up.

Your account comes with one US phone number. Claude calls from that number, and calls to it are answered by the assistant.

Sign up

  1. Fill in the sign-up form: your name, email, what Claude will call about, and the plan. Accept the acceptable use rules.
  2. Pay on Stripe's secure page. WeCall365 never sees your card details.
  3. You land on a page that shows your API key once. Copy it and keep it safe. We cannot show it again. The key is only shown in the browser you signed up in.
  4. We review every account. Until we approve yours, the key can read your account (get_account, /v1/me) and calls are refused with not_approved.
  5. Once approved, your account gets its own US number and Claude can place calls.
  6. If a payment fails or the subscription is canceled, calls pause (refused with billing_inactive, and incoming calls hear that the number is not available) until the subscription is paid again.

Lost the key before you saved it? Write to us through the contact form and we will issue a new one.

Connect Claude Code

  1. Put your key in an environment variable

    Name it WECALL365_API_KEY. This keeps the key out of the command you run next.

    macOS, Linux

    export WECALL365_API_KEY="your-key-here"

    Windows PowerShell

    $env:WECALL365_API_KEY = "your-key-here"

  2. Add the WeCall365 server

    Terminal

    claude mcp add --transport http wecall365 https://www.wecall365.com/mcp --header "Authorization: Bearer $WECALL365_API_KEY"

    Add --scope user to make it available in every project.

    In PowerShell, write $env:WECALL365_API_KEY where the command says $WECALL365_API_KEY.

  3. Check that it is connected

    Terminal

    claude mcp list

    You should see wecall365 in the list.

Connect the Claude apps

In claude.ai or Claude Desktop, add WeCall365 as a custom connector with this address:

Connector URL

https://www.wecall365.com/mcp

Claude opens a WeCall365 page. It shows which app is asking and where it sends you back. Paste your API key there once and press Allow. We use the key only to find your account. We do not keep it, and the app never sees it.

The app then works with your account and your limits, the same as with the key. If you get a new API key, every connected app has to sign in again. To disconnect an app, ask WeCall365 support.

A first safe test

Call yourself first. Ask Claude to call your own cell phone, say it is a test, and end the call.

Say this to Claude

Call my cell at (your number). Say this is a test call, then end the call.

Your phone rings. The assistant says it is an AI assistant and who it is calling for. When the call is over, Claude shows you the summary and the transcript.

Tools

Once connected, Claude has seven tools. You do not call them yourself. Ask in plain words and Claude picks the right one.

make_call
Place a call to a US or Canada number. Claude passes the number and what the call should get done.
get_call
Read one call: its status, the summary, the key facts and the full transcript.
list_calls
List your recent calls.
end_call
End a call that is still going.
get_account
Show your account: your phone number, your limits, your incoming call settings and the names your calls may be made on behalf of.
update_inbound_settings
Change how incoming calls are answered: the greeting and the instructions.
send_text
Not available yet. Texting is not turned on, so this tool sends nothing and says so.

Who the call is on behalf of

Every call says who it is for: "I am an AI assistant calling on behalf of" and then a name. By default that name is your account name.

A call may use another name only if we approved it for your account first. This keeps anyone from making calls in someone else's name. Ask us to approve a name, such as a business you run or a colleague you call for. We check it and add it.

Claude passes the name as on_behalf_of, in make_call or in POST /v1/calls. Case does not matter; the call uses the spelling we stored. Any other name is refused and nothing is dialed. get_account and GET /v1/me list the names you can use under allowed_on_behalf_of.

REST API

There is also a REST API at https://www.wecall365.com/v1. It takes the same key, sent as a Bearer token.

POST/v1/calls
Start a call.
GET/v1/calls/{id}
Read one call.
GET/v1/calls/{id}/recording
Download the call's audio as MP3, when the call was recorded.
GET/v1/calls
List your calls.
POST/v1/calls/{id}/end
End a call.
GET/v1/me
Read your account.
PATCH/v1/inbound
Change how incoming calls are answered: on or off, the greeting and the instructions.

Check your key

curl https://www.wecall365.com/v1/me --header "Authorization: Bearer $WECALL365_API_KEY"

Limits

Accounts start with these fair-use limits.

Calls at a time
1
Calls per hour
20
Calls per day
50
Call minutes per day
1,000
Minutes per call
60

WeCall365 calls US and Canada numbers only. The acceptable use rules say what calls are allowed.

Call recording

Recording is off by default. WeCall365 turns it on for an account only when you ask, and sets how many days recordings are kept (30 unless you choose otherwise, at most 365). After that they are deleted.

When recording is on, the assistant says that the call is recorded in its first turn, and people who call your number hear "This call may be recorded." in the greeting.

You are responsible for the consent laws where you are and where the other person is. Some places need everyone on the call to agree to a recording. The acceptable use rules apply.

When a call has a recording, get_call says so, and you download it with GET /v1/calls/{id}/recording. Audio is never sent over MCP.

Not available yet

  • Texting. It is planned. Today WeCall365 makes and answers calls only.