Haloscan

Haloscan MCP Server exposes Haloscan SEO API capabilities through a collection of MCP tools designed for common SEO tasks and user management. The server provides user credit retrieval and an extensive suite of keyword exploration tools, including overview, match, related terms, questions, highlights, site structure, SERP comparisons, bulk keyword processing, and SERP scraping. Clients compatible with MCP (such as Claude for Desktop or N8N workflows) can invoke these tools by addressing the designated MCP server and using the tool names listed in the README. The tools are structured to accept a keyword or related inputs and return structured SEO metrics, volumes, competition data, SERP snapshots, and more, enabling automated SEO workflows and data collection.

Prerequisites:

• Node.js (LTS) and npm installed on your machine.
• Access key for Haloscan API (HD API key) and base URL if needed.

1. Clone the MCP server repository:

git clone https://github.com/your-org/occirank-haloscan-mcp-server.git
cd occirank-haloscan-mcp-server

2. Install dependencies:

npm install

3. Configure environment variables:

• Copy or create a .env file and set:

HALOSCAN_API_KEY=your-haloscans-api-key
HALOSCAN_API_BASE_URL=https://api.haloscan.ai

4. Start the MCP server:

npm start

5. Verify the server is running by checking logs or hitting the MCP endpoint provided by your deployment.

Notes:

• If your setup uses a different entry point, adjust the mcp_config accordingly (for example, change server.js to the actual start script).
• Ensure network access to Haloscan API is permitted in your environment.

Tips and common considerations:

• Keep your Haloscan API key secure and do not commit it to version control.
• The keyword exploration tools return large datasets; consider using volume_history or metrics options to limit results when appropriate to manage response size.
• Some endpoints (e.g., similar_category or bulk operations) may have higher latency; consider implementing timeouts or asynchronous handling in your MCP client.
• If you rotate API keys, update the HALOSCAN_API_KEY env var and restart the server.
• Use the get_user_credit tool to monitor remaining quota before running expensive keyword analyses.
• When integrating with N8N, map each MCP tool to a corresponding node, and pass inputs via the node parameters (e.g., keyword, requested_data).
• For debugging, review server logs for tool invocation details and responses from Haloscan API.