Launch Directory List Builder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but running the tool requires one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_launch_directory_listA | Build a ranked list of places to submit a product launch: startup directories, product launch sites, newsletters, communities, subreddits, marketplaces, press and review pages, and optionally curated GitHub lists. Describe the product and each row comes back with the submission link, price, dofollow or nofollow, audience, rules, and a fit score, checked live today (up, moved, parked, gone, login first, submit form, prices shown, newest date on the page) and ranked by Tranco popularity. The places come from the public domain awesome-submitlist catalog. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN and is billed per place row. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool in the set, there is no possibility of tool-to-tool confusion or misselection. The tool's purpose (ranked launch-directory list building) is clearly stated and self-contained.
The lone name follows a clean verb_noun pattern (build_launch_directory_list) in snake_case. Nothing deviates from it, so consistency is trivially satisfied.
A single tool is thin for a server, though this one bundles a full workflow (catalog lookup, live availability checks, scoring, ranking) into one call. It borders on 'one trivial tool' territory but is substantive rather than trivial.
Core lifecycle (produce a ranked list) is covered, but there are notable gaps: no way to refine or re-rank an existing run by run ID (errors surface a run ID but nothing consumes it), no per-place detail lookup, and no export/filtering options beyond the initial product description.