Tool-Use Guide

How to use the FTS Akamai MCP server effectively

Getting Started

The FTS Akamai MCP server exposes Akamai platform operations as MCP tools. Any MCP-compatible client (Claude Desktop, Claude Code, custom agents) can connect and use them.

Add to your MCP client configclick to copy
{
  "mcpServers": {
    "fts-akamai": {
      "url": "https://ftsmcp.dev/McpServer/"
    }
  }
}

Credential Setup

The server runs without embedded API credentials. Each session must configure its own via configure_credentials.

Akamai EdgeGrid — Provide one or more .edgerc sections. Most users need only [default]. CPS operations can use a separate [cps] section if your credentials are scoped by API.

configure_credentials — Akamai + Cloudflareclick to copy
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "configure_credentials",
    "arguments": {
      "_sessionId": "<from initialize response>",
      "edgerc": [
        {
          "section": "default",
          "host": "akab-xxx.luna.akamaiapis.net",
          "clientToken": "akab-xxx",
          "clientSecret": "xxx",
          "accessToken": "akab-xxx"
        }
      ],
      "cloudflareToken": "cf-bearer-token-here",
      "accountSwitchKey": "1-ABC123"
    }
  }
}

Credential resolution order:

  1. Session store — requested section (e.g., cps)
  2. Session store — default section
  3. Environment variables (server-side .env)
  4. Not configured — tool returns an error

Credentials live only in process memory and are never persisted to disk or database.

Workflow Patterns

The server offers two approaches for multi-step operations:

Orchestrated (single tool call) — Call one orchestrator tool (competitive_migration or onboard_site) that runs all phases automatically. Best for demos and fully automated pipelines.

Step-by-step (individual tools) — Call each tool individually with human review between phases. Best for production use where you want to validate staging before going to production, or customize parameters at each step.

Both approaches use the same underlying tools — the orchestrators simply chain them together.

Competitive Takeaway Walkthrough

Migrate a site from Cloudflare to Akamai in 17 phases:

  1. configure_credentials — Set Akamai EdgeGrid creds (and optionally CF bearer token)
  2. cf_export_config — Export Cloudflare zone config (DNS, page rules, WAF, workers)
  3. cf_assess_migration — Analyze config, recommend Akamai products (Ion, AppSec, Edge DNS, SBD)
  4. cf_convert_to_akamai — Convert CF rules to PAPI rule tree, WAF policy, DNS records
  5. cps_get_dv_tokens — Get DV/DOM validation tokens for SBD certificates
  6. papi_create_property — Create Akamai property from golden template
  7. dns_validate_zone — Confirm Edge DNS zone is active
  8. dns_add_record — Place domain ownership and certificate validation records
  9. papi_activate_property — Activate to STAGING
  10. papi_check_activation — Monitor staging activation
  11. appsec_create_config — Create WAF in deny mode
  12. appsec_activate — Activate WAF to STAGING
  13. papi_activate_property — Activate to PRODUCTION
  14. papi_check_activation — Monitor production activation
  15. appsec_activate — Activate WAF to PRODUCTION
  16. dns_add_record — Place edge CNAME for DNS cutover
  17. Post-migration deliverables: nameservers, origin IP ACLs, testing guidance

Site Onboarding Walkthrough

Onboard a new site to Akamai in 15 steps:

  1. configure_credentials — Set Akamai EdgeGrid credentials
  2. dns_validate_zone — Confirm Edge DNS zone exists
  3. papi_create_property — Create property with hostname, origin, caching rules
  4. cps_get_dv_tokens — Get certificate validation tokens
  5. dns_add_record — Place domain ownership TXT record
  6. dns_add_record — Place certificate validation CNAME
  7. papi_activate_property — Activate to STAGING
  8. papi_check_activation — Monitor staging activation
  9. dns_add_record — Place edge CNAME
  10. appsec_create_config — Create WAF config (deny mode)
  11. appsec_activate — Activate WAF to STAGING
  12. appsec_check_activation — Monitor WAF staging
  13. papi_activate_property — Activate to PRODUCTION
  14. appsec_activate — Activate WAF to PRODUCTION
  15. Final verification: property ID, edge hostname, WAF config ID

JSON-RPC Examples

All MCP communication uses JSON-RPC 2.0 over HTTP POST to /McpServer/.

Initialize sessionclick to copy
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "initialize",
  "params": {
    "protocolVersion": "2025-03-26",
    "clientInfo": { "name": "my-client", "version": "1.0" },
    "capabilities": {}
  }
}
List all toolsclick to copy
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/list"
}
Call a toolclick to copy
{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "dns_validate_zone",
    "arguments": {
      "_sessionId": "<from initialize response>",
      "zone": "acmecorp.com"
    }
  }
}
Get a prompt templateclick to copy
{
  "jsonrpc": "2.0",
  "id": 4,
  "method": "prompts/get",
  "params": {
    "name": "competitive_takeaway",
    "arguments": { "domain": "acmecorp.com" }
  }
}

REST API — Cloudflare Migration

The CF conversion pipeline is also available as a standalone REST API at /CfApi/. Clients send JSON in and get clean JSON out — no MCP protocol required.

GET /CfApi/ — Returns API documentation and available actions.

POST /CfApi/ — Route by action field: export, assess, or convert.

Step 1 — Export (demo mode)click to copy
curl -X POST https://ftsmcp.dev/CfApi/ \
  -H "Content-Type: application/json" \
  -d '{"action":"export","source":"demo","domain":"acmecorp.com"}'
Step 2 — Assess migrationclick to copy
curl -X POST https://ftsmcp.dev/CfApi/ \
  -H "Content-Type: application/json" \
  -d '{"action":"assess","cloudflareConfig": <output from step 1> }'
Step 3 — Convert to Akamai formatsclick to copy
curl -X POST https://ftsmcp.dev/CfApi/ \
  -H "Content-Type: application/json" \
  -d '{"action":"convert","cloudflareConfig": <step 1>, "assessment": <step 2> }'

The convert response contains: papiRuleTree (PAPI JSON), wafPolicy (WAF config), dnsRecords (Edge DNS format), certEnrollment (CPS params), and metadata.

Tool Categories

See the Tool Catalog for the full list. Tools are grouped by: