Developers
Amo.ng MCP
Connect compatible AI and developer clients to search and retrieve current published Amo.ng Prompts, Workflows, and Skills.
Public read-only MCP server
Model Context Protocol (MCP) is a standard way for a compatible AI or developer tool to discover and call external tools. Amo.ng MCP lets those clients find and retrieve the same current published Prompts, Workflows, and Skills available through the public API.
No account, API key, or authentication is required. The server receives search terms and stable Amo IDs needed for a request; it has no user data and exposes no write or execution capability.
MCP connection
Available tools
search_promptsget_promptsearch_workflowsget_workflowsearch_skillsget_skill
Search first, then retrieve full content
The three search_* tools return compact discovery results. Use the matching get_* tool with an Amo ID or slug only after choosing an asset.
Search calls return 10 results by default and accept at most 20 per page. Full Prompt bodies, ordered Workflow steps, and complete Skill instructions are returned only by the corresponding retrieval tool.
Connect and try it
- Add the endpoint to a compatible remote MCP client.
- Review and enable the six read-only Amo.ng tools.
- Search published content or retrieve a current Prompt, Workflow, or Skill by its Amo ID or slug.
Example requests:
- Retrieve
AMO-P-000001, Laravel Bug Fix and Refactor Prompt. - Retrieve
AMO-W-000001, Laravel Incident Investigation and Controlled Correction, and preserve its step order and review notes. - Retrieve
AMO-S-000001, Assess AI Agent Workflow Readiness, with its public source reference.
MCP clients send JSON-RPC transport requests with POST. Opening this URL with GET or HEAD returns this public information page and does not run an MCP operation.
View verified client setup guidance. If you are building an application instead of connecting an MCP client, use the public read-only API for ordinary JSON over HTTP.