Skysay

io.github.skysay-aiPublished by GitHub account skysay-aiv0.1.0Updated Oct 24, 2026

Skysay voice agents, phone numbers, calls, SMS and campaigns over MCP. 100+ countries covered.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Skysay lets an assistant check coverage, get phone numbers, place AI voice calls, send SMS and read call results through a hosted MCP server.

What you can do
  • Check coverage and available number types and their costs by country
  • Get or request phone numbers and review outbound readiness
  • Place AI voice calls and check their status
  • Send SMS and read SMS records
  • Read call metadata, transcripts and workspace overview
  • Evaluate onboarding and policy information for the workspace
When to use it
Useful when you want an assistant to run phone-based outreach or verification: checking number availability and cost, placing AI voice calls, sending texts, and reviewing call status or transcripts from within a chat client.
Requirements
A remote streamable HTTP endpoint at api.skysay.ai; no local install or package. OAuth 2.0 sign-in with PKCE through Skysay's own sign-in page (email code, Google or GitHub), plus consent to the requested scopes. A Skysay workspace with purchased funds for numbers, calls and SMS. A read-only endpoint variant is offered.
Before you install
Calls, SMS, number requests and top-ups spend purchased Skysay funds; the $5 welcome credit only covers browser testing inside Skysay. Write scopes such as calls:write, sms:send, sms:read, recordings:read, numbers:write and wallet:write need extra consent, and the default grant is read-only. The approval-before-spending step is assistant behaviour, not enforced by OAuth, so review consent scopes carefully. Access can be revoked under Connected apps.

Installation

In SourceWeft

  1. Open Skysay in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.skysay-ai%2Fskysay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "skysay": {
      "type": "http",
      "url": "https://api.skysay.ai/mcp"
    }
  }
}

README

Skysay plugin for Cursor and Grok Bot

Give your agent a real phone number. With Skysay, an agent can check coverage, get a number, place AI voice calls, send SMS and read call results through Skysay's hosted MCP server. 100+ countries covered; channels vary by country and number type.

What's included

ComponentPathPurpose
Manifest.cursor-plugin/plugin.jsonPlugin metadata
MCP servermcp.jsonRemote Skysay MCP at https://api.skysay.ai/mcp
Skillskills/skysay-phone/SKILL.mdHow to get a number, call, text and check results safely, with approval before anything that costs money or contacts someone
Logoassets/logo.svg (assets/logo.png 512×512)Marketplace icon

No hooks, scripts, install steps, local processes or telemetry. No credentials are stored in this repository.

Connect

  1. Install Skysay from the marketplace (Cursor: Customize → Plugins; Grok Bot: Connect apps).
  2. When asked, authenticate. Skysay opens its own sign-in page (verified email code, or Google/GitHub). Review the client, workspace and permissions on the consent screen, then choose Allow access.
  3. Ask the agent: "Use Skysay account_overview and summarise my workspace. Do not place calls or send SMS."
SettingValue
Server URLhttps://api.skysay.ai/mcp
TransportStreamable HTTP
AuthenticationOAuth 2.0 authorization code with PKCE S256; dynamic client registration and Client ID Metadata Documents supported; no client secret
Read-only alternativehttps://api.skysay.ai/mcp/read-only (five read tools, no calls or writes)

The default grant is read-only: workspace, agents, call metadata, coverage, numbers, onboarding and policy evaluation. Calling (calls:write), SMS (sms:send, sms:read), transcripts (recordings:read), number requests (numbers:write) and top-ups (wallet:write) need extra consent. Revoke access any time under Connected apps on the API keys page in your Skysay workspace.

Costs

Connecting is free. Phone numbers, phone calls and SMS use purchased Skysay funds; the one-time $5 welcome credit only covers browser testing inside Skysay. See https://skysay.ai/pricing. The skill shows the expected cost and waits for your approval before any call, text, number request or top-up. That approval step is the assistant's behaviour, not something OAuth enforces, so review consent scopes carefully.

Example prompts

  • "Which Skysay number types are available in Germany, and what do they cost?"
  • "Check my UK number's outbound readiness, prepare one short test call to the number I give you, and show me the cost before dialling."
  • "Check whether my number can send SMS and draft this text for my approval: …"
  • "Show the status and transcript of my last Skysay call."

Docs and support

Other files in this repository

  • .mcp.json: the same remote OAuth MCP configuration for clients that read .mcp.json.
  • plugin.json: portable display metadata for the connection package.
  • .claude-plugin/plugin.json and .grok-plugin/plugin.json: client plugin metadata.
  • server.json: proposed Official MCP Registry metadata. Inclusion in this repository does not mean registry publication or marketplace approval.

Marketplace submission, marketplace approval and production service availability are separate.

License

MIT for the files in this repository. Use of the hosted Skysay service is governed by Skysay's terms. Skysay is operated by Herous Futurus OÜ.

Source: README.md at commit e4ad27b

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 15, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts