Developers / MCP Server Implementation

Aeitron Model Context Protocol (MCP) Server

The official implementation guide for integrating Aeitron Edge, DNS, Compute, and Cloud Infrastructure with Claude Desktop, Cursor, ChatGPT, and Autonomous AI Agents.

Protocol: MCP 2024-11-05 Node.js 22 & TypeScript Transports: STDIO & Streamable HTTP / SSE Open Source: MIT

1. Overview & Architecture

The Aeitron MCP Server provides a standardized, sandboxed Model Context Protocol (MCP) interface that bridges Large Language Models (LLMs) with Aeitron’s global infrastructure. Through this server, AI agents can read real-time edge telemetry, inspect DNS zones, retrieve project configurations, and securely provision resources without exposing raw database credentials.

💡

Consolidated Developer Domain: As part of our domain consolidation, all technical APIs, documentation, and tooling endpoints are unified under developers.aeitron.com. Previous references to api.aeitron.com automatically route to developers.aeitron.com/api.

2. Available Tools Catalog

The MCP server registers the following schema-validated tools governed by strict RBAC scopes:

Tool Name	Required Scope	Action Type	Description
`get_account`	`account:read`	Read	Returns authenticated account profile, tenant organization slug, subscription tier, and global resource quotas.
`list_projects`	`projects:read`	Read	Lists all projects owned by or accessible to the tenant with pagination support across Dhaka, Singapore, Frankfurt, and Virginia PoPs.
`get_project`	`projects:read`	Read	Retrieves detailed deployment status, attached custom domains, and 24-hour edge traffic telemetry for a specific project ID.
`get_dns_records`	`dns:read`	Read	Fetches active DNS records (A, AAAA, CNAME, TXT, MX) for an authorized domain zone on the Aeitron edge network.
`get_usage`	`usage:read`	Read	Summarizes bandwidth egress, request counts, microVM compute hours, and estimated billing costs.
`create_project`	`projects:write`	Write	Provisions a new edge project workspace with automatic Anycast routing and TLS provisioning.
`create_dns_record`	`dns:write`	Write	Adds a new DNS routing record to an authorized domain zone with sub-second global edge distribution.
`delete_dns_record`	`dns:write:delete`	High-Risk	Permanently deletes a DNS record. Requires scope `dns:write:delete`, explicit `confirm: true`, and a cryptographic approval token.

3. Claude Desktop Integration (STDIO)

You can configure the official Anthropic Claude Desktop app to talk directly to your Aeitron infrastructure using the standard I/O (STDIO) transport.

Configuration File Path

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "aeitron": {
      "command": "npx",
      "args": ["-y", "@aeitron/mcp-server"],
      "env": {
        "AEITRON_API_BASE_URL": "https://developers.aeitron.com/api",
        "AEITRON_API_KEY": "atk_live_your_authoritative_aeitron_api_key_here"
      }
    }
  }
}

Where to get your API Key: Log in to your sovereign dashboard at apanel.aeitron.com, navigate to Settings • API Keys, and generate a key with appropriate scopes (e.g. dns:read, projects:read).

4. Cursor & Windsurf IDE Setup

Connect Cursor or Windsurf to execute real-time edge commands directly inside your code editor:

Open Cursor, press Cmd + , (or Ctrl + , on Windows/Linux) to open Settings.
Navigate to Features • MCP Servers.
Click + Add New MCP Server:
- Name: aeitron
- Type: command
- Command: node /path/to/aeitron/apps/mcp-server/dist/src/cli.js
Add environment variable AEITRON_API_KEY with your token.

5. Remote Streamable HTTP & SSE Deployment

For web-based LLMs (such as ChatGPT Custom GPT Actions, Claude Web, or remote orchestrator agents), the server exposes Streamable HTTP and Server-Sent Events (SSE) endpoints:

POST

https://aeitron.com/mcp

Modern Streamable HTTP endpoint for bidirectional JSON-RPC MCP streaming.

GET

https://aeitron.com/mcp/sse

Legacy Server-Sent Events handshake endpoint for streaming sessions.

POST

https://aeitron.com/mcp/messages?sessionId={id}

Channel message delivery endpoint for active SSE sessions.

Example Authentication Header

Authorization: Bearer atk_live_your_api_key_here
Content-Type: application/json

6. Two-Step Human MFA for Destructive Actions

To prevent autonomous LLM hallucinations from causing accidental infrastructure downtime, high-risk mutations (such as delete_dns_record) enforce a cryptographic two-step challenge:

Step 1

Initial Request: The model calls delete_dns_record. The server rejects immediate deletion and responds with an ephemeral challenge: { "requiresApproval": true, "approvalToken": "del_tok_a98f12...", "expiresIn": 300 }

Step 2

Human Verification: An authenticated human operator approves the deletion via the aPanel cockpit or terminal CLI: aeitron dns approve-deletion --token del_tok_a98f12...

Step 3

Final Execution: The model re-invokes delete_dns_record passing confirm: true and approvalToken: "del_tok_a98f12...". The record is permanently deleted.

7. Standalone Push Repository Protocol

In accordance with the Aeitron Engineering Guide (AGENTS.md Section 10), the MCP server is developed within the monorepo at apps/mcp-server and synced to its official standalone repository:

api-mcp-server https://github.com/aeitron/api-mcp-server

View GitHub Repo ↗