Connect Claude Code to Skysay MCP

Claude Code connects directly to hosted Skysay MCP. No private repository, local bridge or downloaded skill is needed. Start by inspecting your workspace; connecting the server alone does not give you an active phone number.

Prerequisites

• A current Claude Code installation and a Skysay workspace.
• For API-key setup, a workspace key with account:read, supplied through SKYSAY_API_KEY in the environment of the process launching Claude Code.
• For OAuth instead, access to Skysay sign-in and permission to approve the read-only connection. Choose one method, not both.

Create the credential. Do not paste its value into a conversation or commit it.

API key: configure HTTP explicitly

In the project where you run Claude Code, merge this server entry into .mcp.json. Preserve any other server entries:

{
  "mcpServers": {
    "skysay": {
      "type": "http",
      "url": "https://api.skysay.ai/mcp/read-only",
      "headers": {
        "Authorization": "Bearer ${SKYSAY_API_KEY}"
      }
    }
  }
}

The environment-variable reference is literal in the file. The type field is required: a URL-only entry is not Claude Code's HTTP configuration. This file contains no key; the exported variable must be present when you start Claude Code. Before approving project MCP configuration, check that its URL is exactly https://api.skysay.ai/mcp/read-only (or the full /mcp resource for an approved workflow) and that the header references ${SKYSAY_API_KEY}. Do not approve an untrusted project entry that sends that variable to another host.

Use /mcp in Claude Code to inspect the connection, then ask:

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

OAuth alternative

Without the API-key entry above, run:

claude mcp add --transport http skysay https://api.skysay.ai/mcp/read-only

Start Claude Code, open /mcp, select Skysay and follow its authentication flow. Sign in to Skysay and review the workspace and read-only permissions before approving. Then use the same read-only prompt.

Do not combine this local server entry with another project/user entry named skysay. If you previously configured one, update or remove that entry using its original scope before adding a different authentication method.

Calls, SMS and number setup

Once the read succeeds, follow Quickstart to move to the full /mcp resource with the exact additional scopes. A read-only OAuth token must be replaced by a grant for that full resource. Review the billable-action controls and the tool reference; do not let a connection test contact people or spend money. Endpoint authorization does not enforce a conversational human-confirmation step on behalf of your assistant.

Troubleshooting

Configuration syntax: Claude Code MCP documentation. For endpoint permissions and protocol details, see MCP overview.