Skysay MCP

Connect an AI assistant to your existing Skysay workspace to inspect and manage voice agents, phone numbers, calls, SMS and campaigns.

Number availability, capabilities and verification requirements vary by country. 100+ countries covered.

This repository distributes public connection configuration and metadata for Skysay's hosted MCP service. It does not contain the hosted application's source code, credentials, or customer data.

Connect

• Endpoint: https://api.skysay.ai/mcp

• Transport: Streamable HTTP. No local server installation is required.

• Authentication: OAuth authorization-code flow with PKCE S256, or a scoped Skysay API key.

• Setup and authorization guide

• Tool reference

• Scopes and permissions

For an MCP client with remote OAuth support, add:

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

The assistant will open Skysay sign-in and workspace consent. Review the client, workspace and permissions before connecting. Revoke a connection from Connected apps on the workspace's API keys page.

For clients using API keys, follow the setup guide to supply the key locally as a bearer header. Never commit or publish a key.

Related MCP server: AJEMS MCP Connector

Capabilities and costs

Read workspace activity, agent configuration, phone numbers and call/campaign status. Supported configuration, calling, SMS and campaign actions require the corresponding permissions. Availability depends on account capabilities and service configuration. Calling, messaging, number provisioning, voice previews and simulations may incur charges under your Skysay account. See pricing.

For a fixed read-only connection, use https://api.skysay.ai/mcp/read-only. It exposes account_overview, list_agents, get_agent, list_numbers and list_calls. Agent configuration includes user-authored prompts. Call metadata can include recording status and existing media links; the connector has no tool to fetch audio files or transcripts. Its OAuth resource and tokens are separate from the full endpoint.

Package contents

• .mcp.json: remote OAuth-capable MCP configuration, without credentials.

• plugin.json: portable display metadata for the connection package.

• .claude-plugin/plugin.json and .grok-plugin/plugin.json: client plugin metadata.

• LICENSE: MIT license for this repository's files.

• server.json: proposed Official MCP Registry metadata. Inclusion in this repository does not mean registry publication or marketplace approval.

License

MIT. The license covers the files in this repository. Use of the hosted Skysay service is governed by Skysay's terms.

Support

Contact Skysay · Privacy · Terms · hello@skysay.ai

The hosted service is governed by Skysay's terms. Marketplace submission, marketplace approval and production service availability are separate.