Abyssale

com.abyssalePublished by abyssale.comOfficial publisherv1.0.1Updated Oct 24, 2026

Browse, generate and import Abyssale designs — banners, video, PDF — from your AI client.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Lets an assistant browse, generate, and import Abyssale designs such as banners, video, and PDF assets.

What you can do
This remote MCP server connects an AI client to Abyssale, a design generation platform. According to its description, it lets the assistant browse existing designs, generate new ones, and import designs, covering formats such as banners, video, and PDF. It runs as a hosted endpoint rather than a local process.
When to use it
Consider it when you already use Abyssale for marketing or brand assets and want an assistant to find, create, or bring in designs without leaving the chat client. It is less relevant if you do not use Abyssale or need offline design tooling.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the hosted Abyssale endpoint. The manifest declares no authentication, environment variables, or headers, and no local package or runtime. An Abyssale account is likely needed to work with your own designs, but the input does not state this.
Before you install
The manifest declares no authentication, so confirm how the hosted endpoint identifies you and who can reach your designs before connecting. Generating or importing designs may create or change content in your Abyssale workspace, and design data is handled by a third-party service.

Installation

In SourceWeft

  1. Open Abyssale in the dashboard and add it to a workspace.
  2. Connect the required 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/com.abyssale%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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "abyssale": {
      "type": "http",
      "url": "https://mcp.abyssale.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 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.