Apexly

dev.apexlyPublished by apexly.devOfficial publisherv1.0.0Updated Oct 28, 2026

Add, check, diagnose and remove your SaaS customers' custom domains from any MCP client.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Apexly's remote MCP server lets an assistant add, check, diagnose and remove custom domains for your SaaS customers.

What you can do
  • Add custom domains for SaaS customers
  • Check and diagnose domain configuration and status
  • Remove custom domains
  • All actions are performed through Apexly's hosted service from any MCP client.
When to use it
Useful when you run a SaaS product with customer-owned custom domains and want an assistant to set them up, troubleshoot DNS or verification problems, or clean them up without leaving the chat.
Requirements
A remote streamable HTTP endpoint at mcp.apexly.dev; no local package or runtime. An Apexly API key sent as a bearer token in the Authorization header is required.
Before you install
The server can change real customer domain configuration: adding and removing domains are write actions that affect live SaaS tenants. The Apexly API key in the Authorization header is a secret and should be scoped and stored carefully.

Installation

In SourceWeft

  1. Open Apexly in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.apexly%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "apexly": {
      "type": "http",
      "url": "https://mcp.apexly.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.