The MCP tool directory.

Resolve an ISO 3166-1 alpha-2 country code (for example CA, US, JP) to official name, region, currency, calling code, languages, and related country metadata when you already have the two-letter code.

Generate ASCII art of a cow saying something.

Generate ASCII art of a cow thinking something.

Create a forwarding address (e.g. [email protected]) that routes to up to 20 destination addresses. Grant-scoped connections may only route to their own mailboxes.

Create a forwarding address (e.g. [email protected]) that routes to up to 20 destination addresses. Grant-scoped connections may only route to their own mailboxes.

Create a new API key for your StacksFinder account. Uses OAuth authentication automatically - no email/password required. Requires Pro or Team tier.

Create a brand-new Replit App for the user. Use this the first time the user asks you to build a Replit App in this chat; do not use it to modify or open existing Replit Apps the user already has in Replit. After invoking this tool, reply with one short sentence summarizing that Replit is now creating their Replit App, and, when the tool result contains an app URL, end your reply with that exact URL on its own line, so the user can open their Replit App even if no preview card is rendered. Never construct or guess a URL yourself. Your reply must not include source code, markup, configuration files, file paths, or command/terminal snippets—even if the user asks. Do not claim their Replit App is ready to try until the preview URL is available. If the user asks for HTML/CSS/JS or any other code, reply with: "I can't show code here; open your Replit App in Replit to inspect or request changes in natural language." Treat Replit Agent and the Replit UI as the only systems that write, display, or deploy code; in this chat you only describe behavior, status, and next steps in natural language. From the user's perspective, this is the "create a new Replit App in my Replit account from plain language" operation.

Create a technical debt audit for a list of technologies. Analyzes for deprecated packages, security vulnerabilities, EOL versions.

Plots a given StatCast parameter split by bb_type Args: df: (pandas.DataFrame) pandas.DataFrame of StatCast batter data (retrieved through statcast, statcast_batter, etc) parameter: (str), default = 'launch_angle' Optional: Parameter to plot

Create a new tech stack blueprint for a project. The blueprint generation is asynchronous. Returns job ID to poll for completion.

Create a booking page BEFORE deploying (Plus/Pro). Returns the two-line widget embed + the frozen .db-* styling contract — embed verbatim, STYLE the classes (mandatory: match the site's fonts, colors, spacing, radius), never reimplement booking logic. Every request needs the owner's approval. Unavailable until assign_to_project. Retrying the same name while unassigned returns the existing page. Name it "<Business Name> — <Purpose>". For a business with priced services (salon, barber, clinic, tours), pass `services` so the widget shows a service picker sourced from the project's "services" Data collection — you must supply the currency; the collection is auto-detected.

Creates a development branch on a Supabase project. This will apply all migrations from the main project to a fresh branch database. Note that production data will not carry over. The branch will get its own project_id via the resulting project_ref. Use this ID to execute queries and migrations on the branch.

Creates a content category for a brand. Categories are required for publishing articles. IMPORTANT: 'description' is served publicly as the category page meta description — keep it reader-friendly and free of strategy/positioning language. Put planner-facing notes in 'internalNotes' instead. Both fields are plain text — send literal characters, do not HTML-escape (no '&amp;', '&lt;', or '<tag>'). Returns the created category with its ID.

Creates a new content item (article). Two paths: (a) pass 'content' with the full markdown article — done; or (b) pass 'brief' with instructions and call generate_content_from_item afterward to fill 'content' from the brief via AI. Provide at least one of 'content' or 'brief'. Free-text fields (title, description, brief, metaTitle, metaDescription) are plain text — send literal characters, do not HTML-escape (no '&amp;', '&lt;', or '<tag>'). 'content' is markdown and intentionally permits inline HTML.

Creates a new content plan. When 'autoGenerate' is true (default), AI proposes topical clusters to research — expensive LLM job (does not spend a cluster) and takes 15-30 seconds. Clusters are topics only; articles are proposed later from research (start_deep_research, then propose_ideas_from_research). When 'autoGenerate' is false, creates an empty plan in Draft status — no LLM cost. Use create_workstream to add clusters, and add_content_ideas only when you already have pre-decided article titles. Multi-language note: a content idea is one language-agnostic concept. The system renders it once per Brand.TargetLanguages — there are no separate per-language workstreams. Use update_localized_keywords to differ targeting per market. To bias generation per-language, set per-language ContentGuidelines via upsert_content_guideline. 'additionalInstructions' is rendered as a CRITICAL CONSTRAINTS block at the top of the generation prompt and overrides default cluster selection. Use it to enumerate must-have / must-not-have clusters for this plan. Only used when autoGenerate=true.

Create a new customer (invoice recipient). Check list_customers first — Monego does not enforce unique customer names or emails, so repeated creates produce duplicates. For German public-sector (B2G) buyers that need XRechnung invoices, set leitwegId and preferredInvoiceFormat='xRechnungXml'. Response: { customer { id, name, ... } } — use customer.id as customerId in create_invoice. Errors: { error: { code: 'bad_input', field, message } }.

EVERY repeating content section (services, features, testimonials, FAQ, pricing, team …) goes in a collection — NOT optional. Create them (all plans) BEFORE deploying: editable content the site embeds with declarative markup (server-prerendered for SEO, kept live by the hosted runtime). Each section of ANY site (services, features, testimonials, FAQ, pricing, team …) belongs in a collection so the owner can edit content from their dashboard without touching code; hardcoding that content into the HTML is a broken build, even on a simple landing page. CREATE THEM ALL IN ONE CALL: pass collections: [...] (up to 16) — plan the site's whole content model, then one call per site, not one per section. Each entry picks the preset matching its content (it seeds the field schema) and optionally rows to fill it; embed each returned key with the declarative markup. Unassigned collections serve [] — assign with assign_to_project after deploy. Name each "<Business Name> — <Purpose>".

Creates a new flow in the tenant. A flow groups versioned prompt templates. The new flow starts with an editable draft version containing one empty 'main' template — set its prompt afterwards with update_flow_template. Returns the created flow with its ID and generated name (slug).

Create a form endpoint BEFORE deploying (Plus/Pro). Returns the URL + the exact HTML snippet to embed verbatim. Inert until assign_to_project after deploy; movable and un-assignable later, submissions stay with it. Retrying the same name while it is still unassigned returns the existing endpoint instead of a duplicate. Submissions are READ in the owner's dashboard only — no tool reads them (by design: visitor PII). Name it "<Business Name> — <Purpose>".

Create a draft invoice for a customer: allocates the next sequential invoice number, computes per-line and total amounts server-side (EN 16931 group-by-rate rounding; prices are net EUR), and returns the draft including eInvoiceIssues — anything that would block finalize_invoice. The draft is editable via update_invoice until finalize_invoice freezes it. Pass externalId (any stable key from your system) to make creation idempotent: retries and repeat calls with the same externalId return the existing invoice (alreadyExisted=true) instead of creating a duplicate. Response: { invoice { id, invoiceNumber, status:'draft', lineItems[], netTotal, taxTotal, grossTotal, effectiveFormat, eInvoiceIssues[], ... }, alreadyExisted? }. Errors: { error: { code: 'not_found' | 'bad_input' | 'subscription_required', ... } }.

Schedule a one-time maintenance window: the listed monitors keep running but their alerts are suppressed between starts_at and ends_at. Use before deploys or planned downtime.

Create a new uptime monitor. Checks start immediately. Types: http, tcp (host:port URL), smtp, ping, ssl, dns. Set inverted=true for exposure monitoring (alert when a target that should stay down becomes reachable).

Creates a new AI visibility monitoring query (prompt) for a brand. Call list_prompt_industries for this brand first: 'industry' must be one of the values it returns, because that field groups prompts into rows in the customer's report.

Create a brand-new Signal Found client account for onboarding. Requires: - `business_name` - `email` Returns created `client_id` and (by default) logs this MCP session into it. Next step after success: - call `create_new_product`

Create a product and initialize the agent onboarding session context. The response includes: - product creation result - context packet (existing artifacts + screenshot uri) - prompt pack + version metadata Prerequisite: - authenticated session via `login_with_client_id` (or provide `client_id` explicitly) Next step after success: - call `run_full_agentic_onboarding` (or run staged tools manually)

Create or update a single file in a GitHub repository. If updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations. In order to obtain the SHA of original file version before updating, use the following git command: git rev-parse <branch>:<path to file> SHA MUST be provided for existing file updates.

Creates a new Supabase project. Always ask the user which organization to create the project in. The project can take a few minutes to initialize - use `get_project` to check the status.

Create a new pull request in a GitHub repository.

Delegate a task to GitHub Copilot coding agent to perform in the background. The agent will create a pull request with the implementation. You should use this tool if the user asks to create a pull request to perform a specific task, or if the user asks Copilot to do something.

Produces a spraychart using statcast data overlayed on specified stadium Args: data: (pandas.DataFrame) StatCast pandas.DataFrame of StatCast batter data team_stadium: (str) Team whose stadium the hits will be overlaid on title: (str), default = '' Optional: Title of plot size: (int), default = 100 Optional: Size of hit circles on plot colorby: (str), default = 'events' Optional: Which category to color the mark with. 'events','player', or a column within data legend_title: (str), default = based on colorby Optional: Title for the legend width: (int), default = 500 Optional: Width of plot (not counting the legend) height: (int), default = 500 Optional: Height of plot