PuppyIP Resource Center
AI Tool Updates 5 min Published 2026-10-10

Cloudflare MCP skills are available: check client skills/list support first

Cloudflare API MCP serves skills, but clients need the Skills over MCP extension to discover and read them. If connected without visible skills, check extension support and host loading first. Ordinary MCP or a local plugin cannot replace that step.

Cloudflare MCP Agent Skills Client support API integration

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • The October 10 announcement confirms server skills for extension-capable clients, not simultaneous support in every client.
  • skills/list discovers skills and resource reads retrieve files; reading SKILL.md does not activate a host skill.
  • Cloudflare's Claude Code, Cursor, Codex and other local/plugin paths are not a remote-extension support matrix.
  • Connections retain OAuth/API-token permissions. Skill-specific fees, regional scope and exact launch time are unpublished.

Server support does not prove client discovery

Cloudflare announced skills through Skills over MCP on October 10, 2026. A skill combines reusable instructions and references guiding tool workflows, rather than merely another API button.

The condition is an extension-capable client. A connected server and Cloudflare tools do not establish skills discovery. Only a date is supplied, without exact time, skill-specific fees or region list.

Check extensions rather than the tool list

Inspect client docs for io.modelcontextprotocol/skills. MCP says the specification is finalized while SDK/host implementation continues; consult current support. Generic MCP support does not answer this.

The server declares resources and Skills extension before clients use skills/list or skills/get. Discovery supplies names, descriptions and manifests; skills do not automatically become ordinary tools because their names resemble one.

Discovery, reading and activation are three steps

Clients retrieve selected SKILL.md and references through resources, with skill://<name>/<path> URIs described by Cloudflare. Files explain workflows; client/host performs reading and loading.

MCP explicitly says resources/read returning SKILL.md does not activate the skill. Hosts use their loading path, verify files against manifest and handle applicable approval. Returned files do not prove the model is using them.

Hypothetical unexecuted case: Cloudflare tools work but no skills menu exists. Check extension support first; if listed, check host loading. Neither case automatically means connectivity failure, and broader account permissions cannot implement an extension.

Local plugins and remote skills are different paths

Cloudflare docs also show plugins, CLI installation and file-copy paths for Claude Code, Cursor, OpenCode, OpenAI Codex and Pi local skill directories. Those describe installing Agent Skills into an environment.

Remote Skills discovers and fetches on demand. Local skill support does not prove remote extension support, nor remote support require copying identical files first. Choose by current client docs instead of combining two support lists.

Skills do not expand Cloudflare permissions

The API MCP server exposes search and execute for API access. Interactive connections use OAuth with chosen permissions; automation can use appropriately scoped user/account tokens. These existing methods are not skill-driven privilege escalation.

Instructions are not account credentials. Even a skill suggesting DNS or Workers edits remains subject to connection scope and host approval. Distinguish reading, permission to execute and actual API authorization.

Identify your current step

First verify remote MCP host mcp.cloudflare.com and path /mcp, then extension docs and discovery. This is suggested setup order; no server/account connection was tested here.

Second verify selected files are readable and host-loaded. Changed manifests require applicable renewed approval; old approval is not perpetual permission for arbitrary new files. This distinguishes cache/loading issues from API permissions.

Sources

Frequently Asked Questions

What about an old /sse connection?

Cloudflare recommends /mcp Streamable HTTP. Historical /sse aliases the same handler, not deprecated HTTP+SSE transport. SSE-only clients need supported transport or detection; transport and Skills support are separate.

Does a missing listing prove a skill absent?

No. Servers may return empty/partial lists while supporting URI queries for provided skills. Known URIs still need an extension-capable client; unknown URIs stop loading. Do not guess addresses or treat ordinary resources as skills.