Connect an MCP client

Connect your client directly to Skysay's hosted HTTP MCP server. The public setup needs no connectors/openclaw directory, private repository, custom stdio bridge or key-minting script.

Building an application agent rather than configuring a coding client? Use OpenAI Agents SDK or Claude Agent SDK. Both guides include public, pinned examples and distinguish connection checks from model-mediated tool calls.

Start with Quickstart. The read-only resource is https://api.skysay.ai/mcp/read-only; the full resource is https://api.skysay.ai/mcp. The OpenAI connector profile at https://api.skysay.ai/mcp/openai keeps calling but excludes wallet funding. Use a recipe for your actual client rather than pasting another client's JSON into its settings. Other clients have different configuration and authorization flows; MCP overview describes the server's protocol and resource boundaries.

Credentials and verification

Create a narrow API key in the workspace, or use the client's OAuth flow and review its consent screen. Store API keys in a local secret store/environment; never in a prompt, skill file or committed config. The workspace determines the credential's tenant; no caller-supplied organization ID can change it.

Verify account_overview with account:read before adding write access. A configured server does not prove a successful tool call, and a successful read does not create an active phone line. See the client recipe's troubleshooting section for 401, missing scopes, missing environment variables and expected 405 responses to browser GETs.

Before adding number orders, calls, SMS or paid previews, read the approval and billing boundaries. A plugin or skill is optional guidance, not a prerequisite for the hosted connection and not a substitute for scopes or explicit approval.