Using MCP Code Mode for Efficient Claude Keyword Research

Architecture and Token Efficiency

A developer shared their experience building an MCP server that gives Claude autonomous keyword research capabilities. The main technical challenge was token efficiency - traditional MCP servers with 15-20 tools can burn thousands of tokens just in tool definitions before any actual work begins.

They implemented the Code Mode pattern (the same approach Cloudflare open-sourced for their API) to reduce this to approximately 1,000 tokens with only two tools: search and execute.

How Code Mode Works

Instead of creating one tool per API endpoint, the agent writes JavaScript snippets against the OpenAPI specification. This code runs in a sandboxed VM with a null-prototype context. The API key is injected server-side and never enters the agent's context. Redirects are blocked to prevent token exfiltration.

Capabilities in Practice

With this setup, Claude can now:

• Analyze keywords (volume, CPC, difficulty, intent)
• Detect trend signals (breakout, spike, seasonal patterns)
• Get 350+ related keywords per lookup
• Chain multiple API calls in a single tool invocation

Key Benefits

The biggest advantage is composability. The agent can search the specification to discover endpoints and then execute multi-step workflows without pre-defined tool chains. This approach allows for more flexible and autonomous operation compared to traditional one-tool-per-endpoint architectures.

The developer is curious whether others are building MCP servers with Code Mode or if the traditional approach works better for different use cases.