Quickstart
Connect Claude Code or Codex to hosted MCP and verify read-only access without placing a paid call.
Connect your coding assistant directly to Skysay's hosted MCP server. You do not need a Skysay source checkout, a local bridge or a Twilio account. Start with read-only access; adding a connection does not provision a phone number or place a call.
1. Sign in and choose a credential
Open Skysay, then your workspace's API keys page.
For the first check, create a key with only account:read. Keep the value in
your local secret store or SKYSAY_API_KEY environment variable. The key is
shown once; do not paste it into a prompt, commit it or share it in screenshots.
Do not use all or all-read for this check: bundles can include future scopes.
OAuth is an alternative when your client supports it. The read-only resource
is https://api.skysay.ai/mcp/read-only; review the workspace and permissions
on the consent screen. API-key permissions and OAuth grants are independent.
2. Connect your client
Claude Code
HTTP configuration, an environment-variable key or OAuth, and a read-only check.
Codex
A bearer-token environment variable or OAuth, configuration and troubleshooting.
Use exactly one authentication method for the server entry. Both recipes start
at /mcp/read-only, which refuses writes even if a credential has broader
permissions. Its five tools are a catalogue; calling a listed tool still needs
that tool's scopes. With just account:read, use account_overview.
3. Verify a real read
Ask your assistant:
Use Skysay account_overview to show my workspace summary.
Do not create an agent, buy a number, place a call or send SMS.A successful MCP result proves an authenticated read, not a functioning phone line. Empty collections are normal in a new workspace. A connection marked “configured” is not enough: check that a tool returned successfully rather than the assistant answering from its own knowledge.
4. Choose what to enable next
To discover coverage or configure a phone agent, switch the server entry to
https://api.skysay.ai/mcp and grant only the additional scopes needed for that
workflow. For example, get_coverage needs coverage:read and accepts
countries: ["GB"]. It is not available on the read-only profile. See
MCP overview and Scopes.
OAuth grants are resource-specific: reconnect when moving from the read-only
resource to /mcp; a token for one is not a token for the other. For API keys,
update the endpoint and use a key carrying the required scopes. Revoke unused
credentials rather than leaving broad test access behind.
For an audio test, configure an agent and use the browser test. Pay-as-you-go billing has no monthly platform subscription; browser credit and purchased funds are separate. A phone number, real call or SMS has its own availability, activation and funding requirements.
Before any billable action
- Confirm the exact recipient, action and expected cost with the user. A tool's presence or an OAuth consent grant is not approval for a particular call, SMS or number order.
- Use only scopes needed for that action. Read-only MCP refuses all writes; the full endpoint can expose billable operations.
- Review the workspace's destination restrictions and spending safeguards. Policy preflight is not a reservation or a guarantee that a call will pass every admission check. Controls do not supply the recipient's consent.
- Keep keys out of model prompts, project files and logs. A local assistant or program able to read your process environment may still read an exported key.
- Follow applicable recipient-permission, AI-disclosure and recording rules. Do not use a successful API request as proof of legal authorization.
Read Policy & outbound,
Billing and Regulated numbers before
moving to real telephony. Shared-number PIN trials are retired; create_trial_call
is a synthetic fixture, not a phone call.