Loading
Loading
The API Freaks MCP server connects your AI assistant directly to the API Freaks platform, giving it real-time access to the full range of API Freaks APIs, right inside your workflow. It's the official API Freaks MCP server, running locally over stdio and set up with a single API key, and it works with Claude, Cursor, VS Code, Gemini CLI, Codex CLI, Windsurf, and any MCP-compatible client.
Set it up once and your assistant can reach every API in our catalog, with new ones added as we ship them. There's nothing to wire up per data type and no extra keys to manage.
It stays in sync with every API Freaks endpoint, so it just works, no betting your key or your results on a third-party wrapper that breaks or falls behind.
Your assistant makes the API calls for you from a plain request, so you skip writing and looking after client code just to pull data.
You'll need Node.js v20 or higher and an API Freaks API key.
To get a key:
You'll pass it to the server as the APIFREAKS_API_KEY environment variable, shown in each setup below. Full API reference: APIFreaks Docs.
The setup is the same idea everywhere: run the server with npx -y @apifreaks/mcp and pass your key as APIFREAKS_API_KEY. Pick your client below.
Add it from the terminal (recommended):
claude mcp add apifreaks -e APIFREAKS_API_KEY=your_apikey_here -- npx -y @apifreaks/mcp
Or edit the config file at ~/.claude/settings.json:
{ "mcpServers": { "apifreaks": { "command": "npx", "args": [ "-y", "@apifreaks/mcp" ], "env": { "APIFREAKS_API_KEY": "your_apikey_here" } } } }
Edit claude_desktop_config.json:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{ "mcpServers": { "apifreaks": { "command": "npx", "args": [ "-y", "@apifreaks/mcp" ], "env": { "APIFREAKS_API_KEY": "your_apikey_here" } } } }
Restart Claude Desktop after you save.
codex mcp add apifreaks --env APIFREAKS_API_KEY=your_apikey_here -- npx -y @apifreaks/mcp
Start a new Codex session after you add the server.
Create or edit .cursor/mcp.json in your project root, or ~/.cursor/mcp.json for a global setup:
{ "mcpServers": { "apifreaks": { "command": "npx", "args": [ "-y", "@apifreaks/mcp" ], "env": { "APIFREAKS_API_KEY": "your_apikey_here" } } } }
You can also add it through the UI under Cursor Settings → MCP.
Edit ~/.codeium/windsurf/mcp_config.json:
{ "mcpServers": { "apifreaks": { "command": "npx", "args": [ "-y", "@apifreaks/mcp" ], "env": { "APIFREAKS_API_KEY": "your_apikey_here" } } } }
Edit ~/.gemini/settings.json, or .gemini/settings.json in your project root for project-level config:
{ "mcpServers": { "apifreaks": { "command": "npx", "args": [ "-y", "@apifreaks/mcp" ], "env": { "APIFREAKS_API_KEY": "your_apikey_here" } } } }
Create .vscode/mcp.json in your workspace:
{ "servers": { "apifreaks": { "type": "stdio", "command": "npx", "args": [ "-y", "@apifreaks/mcp" ], "env": { "APIFREAKS_API_KEY": "your_apikey_here" } } } }
The APIFreaks MCP server is listed on Glama. Click Connect on the listing and follow the prompts. Glama generates the right config for your client and connects it for you.
You don't call tools by name. Ask in plain language and your assistant picks the right one, runs it, and works the answer into its reply. Click the copy icon on any prompt block to paste it directly into your assistant:
Who owns the domain apple.com? Give me the full WHOIS record including registrar, creation date, and expiry date. Now check if apple.com's WHOIS record has changed recently - pull the history for any nameserver or registrant updates. Find other domains registered by the same organisation using a reverse WHOIS lookup by company name.
What organization owns the IP address 8.8.8.8? Give me the ASN, route prefix, and the city-level location. Now look up that ASN - AS15169 - show me the organisation name, country, and all associated route prefixes. What upstreams does AS15169 peer with? Check AS24940 and list its upstream ASN numbers. Is the IP 1.1.1.1 anycast? Show me the announced route prefix and the ASN that originates it. For IP 2.56.12.11, pull the abuse contact email, phone number, and the organisation responsible. Check these IPs for VPN, proxy, Tor, bot, and spam indicators: 49.12.212.42, 2.56.12.11, 8.8.8.8
What are the MX, NS, and A records for github.com? Show me all of them organised by record type. Has github.com changed its IP addresses in the last 2 years? Pull the DNS history and highlight any changes. Which other domains or hostnames are currently pointing to the same IPs as github.com? Run a reverse DNS lookup. Now check stripe.com's SPF, DKIM, and DMARC records - are they configured correctly for email deliverability?
Is mycompany.io available to register? If not, suggest 5 similar domain alternatives I could try. Now check what known subdomains exist for tesla.com - I want to map their external attack surface. Also find domains that are similar to "google" - possible typosquatting domains registered by third parties.
Is contact@example.com a valid, deliverable email address? Run SMTP verification and check if the mailbox actually exists. Now verify these other addresses in bulk and tell me which are risky or invalid: admin@stripe.com, test@nonexistent12345.com, hello@apple.com
You can combine multiple tools in one request - ask it to check a domain's registration, DNS records, certificate, and hosting at once, and it pulls each piece before answering. For everything available, see Supported Tools.
The server lists its tools even without a key, but every request needs one. Open your config, confirm APIFREAKS_API_KEY is set to a valid key from your dashboard, and restart the client.
Check that Node.js v20 or higher is installed with node -v. The server runs through npx, which ships with Node.
Still stuck? Email support@apifreaks.com or open an issue on GitHub.
APIFREAKS_API_KEY.