Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_HOSTNoSSE bind host127.0.0.1
MCP_PORTNoSSE bind port3001
CF_API_TOKENNoCloudflare API token (also accepts CLOUDFLARE_API_TOKEN)
MCP_TRANSPORTNoTransport mode: 'stdio' or 'sse'stdio
CF_ALLOW_DESTRUCTIVENoSet to 'true' to enable record deletion and full cache purgefalse
CLOUDFLARE_API_TOKENNoCloudflare API token (alternative to CF_API_TOKEN)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_zonesB

List all Cloudflare zones on this account.

get_zoneA

Get details for a specific Cloudflare zone by ID.

get_zone_settingsA

Get key security and performance settings for a zone. Returns SSL mode, security level, minification, always-https, brotli, etc.

list_dns_recordsC

List DNS records for a zone.

get_dns_recordA

Get a specific DNS record by zone ID and record ID.

create_dns_recordC

Create a new DNS record.

update_dns_recordA

Update an existing DNS record. Only the fields you provide will be changed.

delete_dns_recordA

Delete a DNS record. Requires CF_ALLOW_DESTRUCTIVE=true.

purge_cacheC

Purge Cloudflare cache for a zone.

list_page_rulesB

List page rules for a zone.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct resource and action: zones, DNS records, zone settings, cache, and page rules are clearly separated. The DNS record tools follow a standard CRUD split with no ambiguity between get/list/create/update/delete.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (list_, get_, create_, update_, delete_, purge_). This makes the toolset predictable and easy to reason about.

Tool Count5/5

With 10 tools, the server is well-scoped for its purpose. Each tool covers a meaningful operation without redundancy or excessive granularity.

Completeness4/5

DNS record management is fully covered with create, read, update, and delete operations. Zone lookup and settings read are present, but zone settings cannot be updated and page rules only support listing, leaving minor workflow gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues