Connect Grok Bot to Skysay

Option 1: Let Grok Bot prepare the setup

Paste this into a fresh Grok Bot:

Read https://skysay.ai/docs/grok-bot and connect yourself to Skysay's hosted MCP
server at https://api.skysay.ai/mcp using OAuth. If Skysay is already connected,
use that connection. Otherwise show me the sign-in link and wait while I
approve the workspace consent. If you cannot add the connection, stop and
tell me what I need to configure; do not claim you are connected.

When connected:
1. Run account_overview and tell me my wallet balance and what numbers I have.
2. Ask which country I want my number in. Run get_coverage and get_number_catalog
   using the full country name, such as "Argentina", not "AR". Show number types,
   inbound capability, carrier-review requirements, setup and monthly prices.
   Use a small catalog limit and report any truncation instead of implying completeness.
   Outside the United States, Canada, United Kingdom and Mexico, do not promise
   outbound calls or SMS before carrier review.
3. Prepare the steps to obtain an active number. Before any order, call or SMS, show the exact
   sender, recipient, task or message, and expected costs, then wait for my
   approval. Do not order a number, call anyone or send SMS during this read check.

Connect Grok Bot to hosted Skysay MCP to check coverage, request a number, place calls through a Skysay voice AI agent and send supported SMS. No local bridge or downloaded server is needed. Grok Bot plans the task; the configured voice AI agent speaks on the telephone.

Works outside the US: Skysay offers numbers in 100+ countries, including the United Kingdom, Germany, Brazil, Argentina and Australia. Outside the United States, Canada, United Kingdom and Mexico, local numbers receive inbound calls immediately once active; outbound calls and SMS need a carrier review first. A listed country does not mean every channel is ready to use.

Setting up a different assistant? See Connect an MCP client.

Prerequisites

• Grok Bot with a connected Skysay MCP server, or a custom remote MCP connection that supports OAuth or a securely stored bearer credential.
• A Skysay workspace and permission to connect it.
• Purchased funds for telephone calls, SMS and numbers. The welcome credit covers authenticated browser tests only. See Billing.

Connecting a server does not activate a number or authorize spending. Start with a successful read, then enable only the actions you need.

What Grok Bot does

Option 2: Configure the connection yourself

Ask Grok Bot to add a custom remote MCP server named Skysay with the values below. Complete the connection card's sign-in flow if it appears. To inspect an existing connection, open Connect apps → Your plugins → Skysay and check the URL and connected status. Installed connectors are shared across your account's Bots, so a fresh Bot can use an existing authorized connection.

If the connection cannot be added or authenticated, stop and use a supported MCP client instead of pasting a secret into chat. See Grok Bot's app connection guide.

For API-key setup, create a scoped workspace key. Never paste it into a conversation or commit it. For OAuth, review the requested permissions before consenting. Start the workspace read with account:read; add coverage:read for the coverage checks and the specific write scopes only when you decide to enable those actions. See Scopes.

Then ask Grok Bot:

Use Skysay account_overview and summarize the result.
Do not perform writes, place calls or send SMS.

The fixed read-only resource has five workspace read tools and deliberately excludes coverage checks and writes. Its OAuth resource and token are separate from the full endpoint; reconnect when switching resources.

Coverage and limits

Numbers are available in 100+ countries. Always check live get_coverage and get_number_catalog results for the country and number type you want.

Number availability and activation requirements vary. "Inbound immediately" describes an active number's capability, not an instant-purchase guarantee. Workspace outbound approval and a number's carrier review are separate checks; neither makes every number SMS-capable.

Costs: pay as you go has no monthly platform fee. Number rental, setup, carrier minutes, hosted voice AI and SMS are charged separately. Use the quote shown before assignment or use and the public pricing page.

Workspace limits: pay as you go supports up to 10 simultaneous calls and 10 billed numbers. Workspace risk limits and carrier capacity may be lower. get_capabilities shows current channels, destinations, caps and usage. For higher limits, contact Skysay.

Calls also have duration and silence controls. See How a call ends. Before each outbound action, check Policy & outbound. A refusal needs the named readiness issue resolved; do not retry it automatically.

Things to ask Grok Bot

Start with an approved caller number, a configured voice AI agent and a destination you own or whose recipient agreed to the call. For example:

Check my UK number's outbound readiness and my voice agent's English setup.
Prepare one short test call to the number I provide. Show me the caller,
recipient, task and expected cost, and wait for approval before dialling.
Afterwards, report the terminal status and transcript if available.

Once you have tested that path, adapt the task:

Prepare a call to a restaurant in Madrid in Spanish to ask about a table for
4 on Friday at 21:00. Use my approved outbound-capable number and a published
Spanish voice agent. Show me the recipient, instructions and cost first.
Instruct the agent to ask about availability only and not confirm a booking or
alternative date. Report back so I can decide what to approve next.

Check whether my number can send SMS. Prepare this text to the recipient I
provide: "Hi Maria, see you Wednesday at 10. Reply if anything changes."
Show me the sender, recipient, exact message and cost before sending.

Help me assign a published inbound voice agent to my active Berlin number
to take messages while I am busy. Show me the configuration before changing
it. Do not enable outbound calls or SMS without the required carrier review.

Recurring reminders need a separately configured scheduler. Receiving calls needs an assigned inbound agent; a post-call SMS summary needs a separate automation and an SMS-capable, approved sender. These examples do not set those automations up automatically.

The approval instructions are for your assistant; OAuth does not enforce a human confirmation for every billable tool call. Follow the billable-action controls, including recipient consent, AI disclosure and recording requirements for your use case.

Troubleshooting

Next steps

Docs for agents: llms.txt