Skip to main content
Glama
741,773 tools. Updated 2026-11-04 09:00

"A server for finding resources or tools for app design" matching MCP tools:

  • Resolve a pending approval request (approve or deny) once the USER has decided. Use this after get_card_details or create_card returns a 202 requiring approval, or for a row from list_pending_approvals. For card_details and transaction, approval automatically completes the follow-up action and returns the result. For cross_app actions (asks from another app: close/pause/resume a card, change a limit, view details), approval records the user's consent and the REQUESTING app completes the action from its side when it retries with the approval id.
    ConnectorNo auth
  • Get current usage against the plan limits, one entry per category (projects, specs, members, …) with the current count, the maximum and whether the category is unlimited. This is the tool that answers 'why can I not create another one'. Use this for usage against plan limits; for the AI credit balance use get_credit_balance. Requires organization context. Read-only: plan, seat and top-up changes are not available through MCP by design — a human does those in the web app.
    ConnectorAPI key
  • List the teams that reach the active project and with which role. The other direction of list_team_projects — this is the tool for 'who can write here'. Requires project context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.
    ConnectorAPI key
  • Returns the plain-language meaning and step-by-step fix for one Malinois finding. Use it while helping the user fix an issue reported by scan_app, or when they ask what a finding means. Pass the rule_id exactly as scan_app returned it. Read-only, no network, instant.
    ConnectorNo auth
  • Fetch the full content for one id returned by `search`: a rental listing (rental:<uuid>), a plan set (plan:<uuid>) or a published page (page:<route>). Returns {id, title, text, url, metadata}. Always cite the url. Hosts that can call specific tools should prefer get_rental or the resources.
    ConnectorNo auth
  • Maps only stable Tier1 finding identifiers to approved Tier1 services and public resources. Call after a Tier1 score or email-domain check. Do not submit prose, URLs, customer information, or invented identifiers. This tool performs no arbitrary fetching, makes no contact request, changes nothing, and stores nothing.
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    A
    quality
    A
    maintenance
    Enables AI agents to perform local video, audio, and file operations inside an isolated workspace, including cutting/concat videos, extracting audio, transcribing, and managing files, with typed responses and background job support.
    11
    1
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides AI assistants with a standardized interface to interact with the Todo for AI task management system. It enables users to retrieve project tasks, create new entries, and submit completion feedback through natural language.
    10 npm
    Apache 2.0

Matching MCP Connectors

  • Decision Layer for AI Agents — 58+ tools, Advisor, MCP. Free key: POST /v1/register {}.

  • Give your AI agent a phone. Place outbound calls to US businesses to ask, book, or confirm.

  • Discover available product features, API/MCP URLs, versions, content limits, and interpretation boundaries before choosing a content tool. Returns product.capabilities.v1 metadata, without fetching stories or checking upstream freshness. Public and read-only; no credentials or arguments. Use latest_stories for recent records or get_health for endpoint compatibility. The mobile app distribution channel remains separately suspended.
    ConnectorNo auth
  • Return the connected organization, the credential in use, and the granted workspace + environment ("TEST" or "PRODUCTION") targets — exactly the values the required workspaceId/environment arguments on targeted tools accept. Always available; call this first, and again whenever a tool returns UNAUTHORIZED or NOT_FOUND unexpectedly, or after this connection's access changes — resources live per-workspace.
    ConnectorOAuth
  • Get the caller's own role and effective permission strings in the active organization — custom roles resolved. This is the tool to reach for after a permission error: it says what the caller actually holds. Set includeCatalog to also get every permission the product defines with its description, to map a denied action onto a name. Requires organization context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.
    ConnectorAPI key
  • Get the AI credit balance: what is left, what the plan includes, what came from rollover or top-ups, and when the allowance resets. Set includeHistory to also get where the credits went — per day and per feature. Use this for AI credits only; for plan limits across every category use get_usage_limits. Requires organization context. Read-only: plan, seat and top-up changes are not available through MCP by design — a human does those in the web app.
    ConnectorAPI key
  • Get the organization's trial: which tier it grants, whether it is still running, when it expires and how many days are left. Unlike the other billing tools this one only needs organization membership, not billing:read. Use this for the trial; for the paid plan behind it use get_subscription. Requires organization context. Read-only: plan, seat and top-up changes are not available through MCP by design — a human does those in the web app.
    ConnectorAPI key
  • Look up customer-facing Wellness Project product knowledge. Use it for app navigation, visible features, integrations, metric meanings, logging methods, permissions/sync questions, or troubleshooting. Wellness Project-specific answers are closed-book: answer them from this tool's result, never from memory. The result states its own grounding rules. For how-to questions, select the relevant feature topic; a matching published video link is included when one exists. For a request to find, report through, or open the feedback form, use topic=troubleshooting. In-app chat must offer the open_feedback action chip, not print the link (chat links render as plain text). External MCP clients may provide the exact Share feedback link returned. Never claim the form was opened without the user tapping the action. For recognized exercise names or whether an exercise is in the app's exercise library, use list_exercises rather than guessing or expecting the app guide to enumerate exercises. For cost, price, Free vs Pro, Founding Member, upgrading, or the 3-analysis limit, use topic=pricing. Reproduce exactly one returned pricing message verbatim, including its subscription link when it has one, and add no other pricing detail. The app attaches its own upgrade button to that message when one applies; never type out a button, chip, link markup, or call-to-action of your own.
    ConnectorOAuth
  • Only for anonymous callers when guest access is enabled. If this AI app is already connected through InkFE customer sign-in (OAuth) or a provisioned integration key, skip this tool and omit guestToken on design/checkout calls. Before guest designing, tell the customer: unpaid, unsaved guest drafts expire 30 days after the design request starts; save through verified sign-in to keep them. Checkout or unresolved purchase records are protected. Returns a private guestToken valid for seven days; token expiry is separate from draft retention. Pass it to create_business_card_design and create_checkout in this conversation. Claimed designs require an AI connection authorized by the same InkFE account. Starting a session does not place or pay for an order.
    ConnectorNo auth
  • Find the exact tool slugs for an app or integration. Returns mainToolSlugs, relatedToolSlugs, per-toolkit hasActiveConnection, a short plan, pitfalls, and notFoundToolkitSlugs. If you already have the exact ACTION slug and only need its input schema, use FLOWRA_GET_TOOL_SCHEMAS instead. When the result includes a catalog app that covers the job, use that app's tool instead of a generic web search, fetch, or HTTP tool. Toolkit tools are not direct function calls. Once you have a slug: FLOWRA_GET_TOOL_SCHEMAS for its arguments (or set includeInputSchemas=true here and skip that step), FLOWRA_MANAGE_CONNECTIONS if hasActiveConnection is false, then FLOWRA_MULTI_EXECUTE_TOOL to run it. Use only slugs that came back from this call. mode "select" (default): queries are one atomic English useCase per item, with the app name in it. Any schedule or recurrence goes in intentSummary only, never in useCase — recurring work is a workflow, not a tool argument. toolkitSlugs pins that app's important tools into candidates. Pass toolkitSlugs, queries, or both — at least one is required. select returns only the tools needed for one action, never a full catalog. mode "inventory": one page of tools in a known app. Requires toolkitSlugs. Optional query is a whole-word match on slug, name, or description (issue matches issues, not issued; for example query "issue" with toolkitSlugs ["github"]). No selection model and no native Flowra tools unless that toolkit was requested. mainToolSlugs is this page only; relatedToolSlugs is empty. toolSchemas include name and a one-line description. If inventory.truncated is true, call again with the same toolkitSlugs and query and offset=inventory.nextOffset. Do not use the workbench to browse a toolkit catalog. toolkitSlugs: exact catalog toolkit slugs (lowercase app id such as gmail or github). Do not pass ACTION slugs here (GMAIL_SEND_EMAIL). Reuse the returned session.id on GET_TOOL_SCHEMAS, MANAGE_CONNECTIONS, and MULTI_EXECUTE_TOOL so auth and workbench state stay on one session.
    ConnectorAPI key
  • Wait for the discussion to move past `afterSequence` and return it, rather than polling for it. Returns as soon as anybody — a designer in the browser or another agent — posts, resolves or deletes; returns a `timedOut` reply if nothing happens within `waitSeconds`, which you answer by calling again with the same cursor. This is how you hold a conversation about a design: post, wait, read, act.
    ConnectorNo auth
  • Keyword search over the list of places to submit a startup. A place's exact name or website ("Indie Hackers", "indiehackers.com") puts it first. Asking for free ("free", "no cost", "$0") leaves out places that are paid only. Product words ("web app", "SaaS", "AI tool", "mobile app") keep only places that take that kind of product. Kind-of-place words ("launch site", "directory", "community") put places of that kind first. Other words match names, websites, regions, and the list's notes. For example "free launch sites for a web app", "AI tool directories", or "Australia". Returns up to 20 places, best match first, each with id, title, url (its row on submitmystartup.com, for citing), and a one-line summary. A query with no specific words returns the best free places. Use fetch with an id for the full record, and find_directories to shortlist by a founder's product and limits.
    ConnectorNo auth
  • Create a new Bridge app in the workspace this connection belongs to, exactly as the dashboard would. Returns its id. It does NOT become the default: pass its id as `app`, or call use_app. Use a new app for a new environment or product rather than repurposing an existing one — an existing app may have live users, email links and billing attached. Only a connection approved for the whole workspace can create apps. A new app has no sign-in callback address: pass `callbackUrl` with the one the project uses (its real port), or add it later with add_redirect_uri — until then sign-in fails with NBLOCKS_NO_CALLBACK_URI. Before writing app code that signs users in to the new app, call get_integration_guide with topic=auth and the framework the app uses.
    ConnectorOAuth
  • Scaffold a flags-only Bridge integration into an existing project — the MCP equivalent of `bridge flag init`. Returns everything that command produces, for YOU to write to disk: the contents of bridge-flags.config.json (app id, app name, base URL, suggested provider config, read live from this Bridge app), the install command, and the framework-specific setup guide fetched from the plugin repo that owns it. Writes nothing — neither to disk nor to the Bridge app. Call this when adding feature flags to a project for the first time; for auth or billing use get_integration_guide with topic=master or topic=billing-master instead. framework is REQUIRED: this server cannot see the caller's disk, so detect it yourself from package.json (next → nextjs, @sveltejs/kit or svelte → svelte, @nestjs/core → nestjs, @angular/core → angular, react → react, express → express; check in that order) and pass it. The returned guide is the same document get_integration_guide returns for topic=feature-flags, so there is no need to call both. Do not invent import specifiers — they differ per plugin and only the guide has the current ones.
    ConnectorOAuth
  • Search stored daily top-chart snapshot records from the iOS App Store and Google Play; omitting `date` selects the latest snapshot. Costs 1 credit per record returned (minimum 2), so keep `page_size` to what you need. Filter by app, store, platform, chart, country, or category; use datasets_apps_search for app records or datasets_apps_reviews_search for stored reviews.
    ConnectorNo auth
  • Search stored daily top-chart snapshot records from the iOS App Store and Google Play; omitting `date` selects the latest snapshot. Costs 1 credit per record returned (minimum 2), so keep `page_size` to what you need. Filter by app, store, platform, chart, country, or category; use datasets_apps_search for app records or datasets_apps_reviews_search for stored reviews.
    ConnectorNo auth
  • Planning-time statistical power from a design's REAL model matrix — no data needed. Builds the design and takes `ncp = effect_size² / (X'X)⁻¹_jj`, so it is correct for centre points, axial points and unbalanced designs — unlike `covadoe_power_analysis`, which assumes orthogonality and overstates power on a CCD, Box-Behnken or DSD. Use this when planning an experiment; use `covadoe_post_hoc_power` only once you have measured responses. `design_type` + `n_factors` builds the design (same generator as `covadoe_create_design`, so the answer describes the design you would actually get). Common aliases resolve ("full_factorial", "ccd", "dsd"). Alternatively pass `design`, an explicit coded run matrix, to score a design you already hold — D/I-optimal, mixture, split-plot or hand-built. `n_runs` / `model_terms` are forwarded to the generator for the optimal designs. `model`: "linear" | "interaction" | "quadratic" | "quadratic_no_interaction" (a DSD supports only the last). `term` names the coefficient — "x1", "x1^2", "x1*x2"; omit it to get power for every term and group, which differ sharply on the same design. `alpha` is the significance level; the CCD axial distance is `axial_alpha`, and the two are easy to confuse. CCD variant: `axial_alpha` defaults to ROTATABLE, (2**n_factors)**0.25 — the design JMP, Design-Expert and Minitab hand you. Pass a number, or "orthogonal" for the α where Σx² = n_runs (at 3 factors: main-effect power 0.9400 against the rotatable 0.8846 on the same 17 runs; the orthogonal α is also the premise of `covadoe_power_analysis`, so on that design the two agree for a main effect and disagree for every other term). `face` — "circumscribed" (default), "faced" (star points on the faces, α = 1) or "inscribed"; a bool works, and an unknown value is rejected rather than quietly treated as circumscribed. Returns power, power_by_term, power_by_group, df_error, relative_variance ((X'X)⁻¹_jj), the resolved design_summary (the α and factorial level actually built — read both, an inscribed CCD always reports α = 1), and `orthogonal_shortcut_power` — what `covadoe_power_analysis` would have claimed — with its signed error (signed: the shortcut does not always overstate). Returns `estimable: false` plus a reason when the model cannot be fitted on the design.
    ConnectorAPI key