Amo.ng

ng.amoPublished by amo.ngOfficial publisherv1.0.0Updated Oct 24, 2026

Discover and retrieve published Amo.ng Prompts, Workflows, and Skills.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Amo.ng is a remote MCP server that lets an assistant discover and retrieve published Amo.ng Prompts, Workflows, and Skills.

What you can do
Discover published Amo.ng Prompts, Workflows, and Skills through the remote endpoint at amo.ng, then retrieve the ones the assistant needs. The manifest lists no individual tools, so the exact operations are not documented; the stated purpose is limited to finding and fetching published content.
When to use it
Use it when you want an assistant to look up published Amo.ng prompts, workflows, or skills and bring them into a conversation or task, rather than authoring them from scratch.
Requirements
A remote MCP connection to the Amo.ng endpoint over streamable HTTP. The manifest declares no authentication, environment variables, or headers, and no local package or runtime is needed.
Before you install
The manifest declares no authentication, so it is unclear what account or access controls apply. No tool list is published, so what the server can read or change cannot be verified before connecting; confirm this on the provider's integration page.

Installation

In SourceWeft

  1. Open Amo.ng in the dashboard and add it to a workspace.
  2. 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/ng.amo%2Famo-ng/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": {
    "amo-ng": {
      "type": "http",
      "url": "https://amo.ng/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 listedRequired15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.