Archonite MCP Server

Last updated: 1/21/2026

The Archonite MCP Server provides a standardized interface for AI models and agents to interact with Archonite's internal documentation and resources. By leveraging the Model Context Protocol (MCP), Archonite allows LLMs to dynamically discover and read documentation.

Production Endpoint

The Archonite MCP server is available at the following production URL:

https://archonite.xyz/mcp

This endpoint is a read-only interface specifically optimized for AI agents and developer tools.

Available Tools

The MCP server exposes several tools that agents can use to navigate the Archonite documentation library.

list_documentation

Returns a comprehensive list of all documentation files available in the Archonite system.

  • Arguments: None
  • Returns: An array of relative paths (e.g., help/00001-what-is-archonite.md).

read_documentation

Reads the full content of a specified documentation file.

  • Arguments:
    • path (string, required): The relative path of the file to read (example: api/00001-introduction.md).
  • Returns: The raw Markdown content of the file.

Editor & Agent Setup

You can integrate Archonite's documentation directly into your favorite AI-powered development environments.

Windsurf (Codeium)

Archonite MCP is fully compatible with Windsurf's Cascade agent. To connect Windsurf to Archonite:

  1. Open Windsurf Settings.
  2. Go to Cascade > MCP Servers.
  3. Click Add New MCP Server.
  4. Select HTTP/SSE.
  5. Enter the URL: https://archonite.xyz/mcp
  6. Click Save. Cascade will now be able to retrieve context from the Archonite library.

Cursor IDE

To add Archonite's documentation to Cursor:

  1. Open Cursor Settings (Cmd+Shift+J or Ctrl+Shift+J).
  2. Navigate to Features -> MCP.
  3. Click + Add New MCP Server.
  4. Enter the following details:
  • Name: Archonite
  • Type: SSE (Required for URL-based servers)
  • URL: https://archonite.xyz/mcp

Click Save. Cursor will now be able to use the list_documentation and read_documentation tools to provide better context for your queries.

Claude Desktop

To connect Claude Desktop to a remote SSE endpoint, you must use a bridge adapter (since Claude Desktop primarily communicates via stdio). Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "archonite": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "[https://archonite.xyz/mcp](https://archonite.xyz/mcp)"
      ]
    }
  }
}

(Note: This configuration uses the mcp-remote package to bridge the remote SSE stream to Claude's local standard input/output).

Usage Example (CURL)

You can verify the connection manually using curl. Note that because this is an SSE endpoint, a standard POST might hang waiting for an event stream unless you hit the initialization endpoint specifically.

To check tool availability (via JSON-RPC POST):

curl -X POST [https://archonite.xyz/mcp/messages](https://archonite.xyz/mcp/messages) \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "list_documentation",
      "arguments": {}
    },
    "id": 1
  }'