CodeDebut MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEDEBUT_MCP_URL | No | Points the stdio bridge at another endpoint, e.g. a local copy of the site. Defaults to https://codedebut.com/api/mcp. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | Find software launched on CodeDebut by keyword (matches name, tagline, description, tags and maker). Use it when a user asks for a tool that does X, e.g. "uptime monitor" or "AI meeting notes". Optionally narrow to a category or pricing model. Featured (paid) products that match rank first and are marked featured. Each result has |
| get_productA | The full public page of one product on CodeDebut, by slug or exact name: description, website, category, tags, pricing, platforms, maker, launch history with day ranks and upvotes, and the latest comments. Use it after any other tool when the user wants details on one product. Cite |
| find_alternativesA | Products in the same category as one listed on CodeDebut, closest first (shared tags, then upvotes). Use it when a user asks for alternatives, competitors or "something like X". Featured (paid) products rank first and are marked featured. Each result has |
| browse_categoryA | Top products in one category, most upvoted first, with featured (paid) products first and marked. Use it when a user asks for the best tools of a kind without a specific keyword. Each result has |
| list_categoriesA | CodeDebut's categories, busiest first, with how many products each has and the category page |
| get_launchesA | Every launch on one day, ranked by upvotes (today by default; days run 00:00-23:59 UTC). Today's ranks are live; past days have final ranks, and #1 is the Debut of the Day. Use it when a user asks what launched today or on a date. Boosted launches are marked; payment never changes a rank. |
| get_debut_of_the_dayA | The #1 launch of a day on CodeDebut. Without a date it returns the most recent finished day's winner. Use it when a user asks for the best new product, a recommendation of the day, or something new to try. |
| get_trendingA | The most upvoted launches today, over the last 7 days or over the last 30 days. Use it when a user asks what is popular, new or trending in software. |
| list_jobsA | Open jobs on the CodeDebut jobs board: title, company, location and the link to apply. |
| get_launch_optionsA | How to launch a product on CodeDebut: the submit link, the next free launch day, how ranking works, and the paid plans with prices. Use it when a user wants to launch, list or promote their own product. |
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 10 tools
Most tools have clearly distinct roles: keyword search (search_products), category browsing (browse_category), competitor lookup (find_alternatives), and single-product detail (get_product) are well separated by their descriptions. The only real friction is among the ranking tools—get_launches, get_trending, and get_debut_of_the_day all return upvote-ordered launch lists for overlapping time windows, so an agent may need to re-read descriptions to pick.
Every name follows a clean snake_case verb_noun pattern (get_, list_, search_, find_, browse_) with the resource as the noun. No camelCase or stylistic mixing, and the plural/singular usage is predictable (get_product singular for one item, list_categories/search_products plural).
Ten tools is squarely in the right range for a product-discovery directory. Each tool covers a distinct query mode—detail, keyword search, category browse, alternatives, launches, trending, jobs, launch info—with no filler.
The read-side lifecycle for a launch directory is well covered: discover (search/browse/alternatives/trending), inspect (get_product, categories, launches, debut), plus jobs and launch guidance. Minor gaps remain—no keyword/filter search on the jobs board, no way to enumerate a maker's other products, and comments are only a truncated slice of get_product rather than their own fetch.