Skip to main content
Glama
205,353 tools. Last updated 2026-06-17 07:12

"A guide to understanding and using the Figma cursor" matching MCP tools:

  • Return marketplace-document purchases the calling agent has made — the agent-facing equivalent of the buyer's ``/me/purchases`` web library. Each row carries the document_id, status, sats amount, paid_at, and (for settled purchases) a short-lived signed ``download_url`` ready to GET without an Authorization header. Cursor-paginated newest-first. If ``next_cursor`` is non-null in the response, pass it as ``after_id`` on the next call to fetch the next page. The cursor is the last row's purchase_id; the server resolves its (created_at, id) ordering key under the hood. Requires MCP authentication. Anonymous L402-style purchases are NOT returned by this tool — those have ``buyer_id=NULL`` by construction and there's no caller identity to scope by.
    Connector
  • Returns a paginated list of domains from the tracker database. Results are ordered alphabetically by domain name and support cursor-based pagination for full traversal. Filtering by category and minimum score allows targeted data extraction. Use this tool when: - You want to enumerate all known ad-tech or analytics domains above a risk threshold. - You need a dataset of tracker domains for offline analysis. - You are paginating through a category to build a block list. Do NOT use this tool when: - You need data for a specific domain — use `get_domain` instead. - You are searching by keyword — use `search` instead. - You want domains belonging to a specific company — use `get_entity` instead. Inputs: - `category` (query, optional): Filter by surveillance category. One of: `ad_tech`, `analytics`, `social`, `fingerprinting`, `content`, `cdn`, `other`. - `min_score` (query, optional): Integer 0-100. Exclude domains scoring below this value. - `limit` (query, optional): Number of results per page. Max 100 (paid), 20 (free). Default 50. - `cursor` (query, optional): Pagination cursor from the previous response's `next_cursor` field. Returns: - Array of domain list items (domain, category, score, prevalence, entity summary). - `meta.has_more`: true if more pages exist. - `meta.next_cursor`: pass as `cursor` to get the next page. - `meta.count`: number of results in this page. Cost: - Free tier: up to 20 results/page, 50 req/day. Pro/enterprise: up to 100 results/page. Latency: - Typical: <200ms, p99: <500ms.
    Connector
  • List products from the connected store, paginated. Use this tool when an agent needs to DISCOVER products by browsing the catalog rather than VERIFYING a known SKU. The response includes the SKU for every product, so a follow-up ``check_stock(sku)`` or ``get_product_details(sku)`` is a natural next step. Args: limit: Number of products to return (1-50, default 10). cursor: Opaque cursor from a previous response's ``next_cursor``. Omit for the first page. Returns: Dictionary with: - products: list of {sku, title, description (≤400 chars), product_type, tags, price, currency, available, image_url, storefront_url} - next_cursor: str or null — pass to the next call to paginate - has_more: bool — whether more products exist - live / source: provenance flags
    Connector
  • List all active sellers on the Kifly network. **Requires a network token (kfn_live_…).** Returns each seller's handle, name, city, region, delivery coverage (`nationwide:true` or a `states` list), delivery fee, and catalog size. Use this to discover which sellers are available and which ship to a buyer's location before calling `get_seller` or `search_products`. **Pagination:** when `kifly:hasMore` is true, pass `kifly:nextCursor` as `cursor` to fetch the next page. Default page size is 20, max 50.
    Connector
  • List all active sellers on the Kifly network. **Requires a network token (kfn_live_…).** Returns each seller's handle, name, city, region, delivery coverage (`nationwide:true` or a `states` list), delivery fee, and catalog size. Use this to discover which sellers are available and which ship to a buyer's location before calling `get_seller` or `search_products`. **Pagination:** when `kifly:hasMore` is true, pass `kifly:nextCursor` as `cursor` to fetch the next page. Default page size is 20, max 50.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Figma MCP Pack

  • The Figma MCP server brings Figma design context directly into your AI workflow.

  • Returns the canonical guide for using TMV from a coding-agent context. Covers the fix-test-retest loop, how to write a good test prompt, how to read the actionTrail / consoleErrors / failedRequests outputs, and common gotchas. Call this first if you're a new agent on a project — it'll save you a debug session. The same content is served at https://testmyvibes.com/docs/coding-agents.
    Connector
  • Create a third-party LEAD-GENERATION page about a business (NOT a site for that business itself). Use this when the goal is to drive qualified search traffic to someone else's business — affiliate pages, review/guide pages, niche directories. The page is branded as an outside guide (e.g. "Best Roofers in San Diego"), refers to the business in the third person, and routes CTAs to the business's existing website. Differences from create_site: - Slug + page brand are SEO-vanity (e.g. "best-roofers-sandiego"), not the candidate's brand name. - Voice is third-party guide/reviewer — never first person. - Primary CTA is "visit their website"; phone/email demoted. - No specific pricing quoted; differentiators emphasized. - Locality is judged by category, not just address (IT/SaaS/agency stays category-wide even when a city is on file). Pass a business candidate object from search_businesses — that business is the one being PROMOTED. Requires authentication via API key (Bearer token). Generate an API key at webzum.com/dashboard/account-settings. The page generation happens in the background. Use get_site_status to check progress. Returns the businessId (a vanity slug) which can be used to access the page at /build/{businessId}.
    Connector
  • Returns the complete setup and usage guide for SwapWizard. Call this FIRST before using any other tool. Covers: required configuration (API key, Alchemy RPC URL, private key), how to use poolId correctly, step-by-step operational flows for swap/zap in/zap out/analyze, transaction execution details, and approval rules.
    Connector
  • Interleaved cross-org release feed for a collection — same shape as `get_latest_releases` but scoped to the collection's member orgs. Cursor-paginated: pass `limit` for slice size (default 20), `cursor` to continue from a prior call. The result's `_meta.pagination` carries `kind: 'cursor'`, `hasMore`, and `nextCursor` when more rows exist; the response text echoes `nextCursor` so an LLM caller can chain without parsing `_meta`. Cursors are stable under inserts.
    Connector
  • List products from the connected store, paginated. Use this tool when an agent needs to DISCOVER products by browsing the catalog rather than VERIFYING a known SKU. The response includes the SKU for every product, so a follow-up ``check_stock(sku)`` or ``get_product_details(sku)`` is a natural next step. Args: limit: Number of products to return (1-50, default 10). cursor: Opaque cursor from a previous response's ``next_cursor``. Omit for the first page. Returns: Dictionary with: - products: list of {sku, title, description (≤400 chars), product_type, tags, price, currency, available, image_url, storefront_url} - next_cursor: str or null — pass to the next call to paginate - has_more: bool — whether more products exist - live / source: provenance flags
    Connector
  • Verify a pending Bitrise registration using the OTP sent to the user's email. Pass the `pending_signup_id` returned by `register`. Returns an `api_token` (a Bitrise personal access token) and, when a workspace was auto-created, a `workspace_slug`. After a successful call, save the token into the user's MCP client config so the Bitrise MCP server is authenticated: find the Bitrise server entry and set its `Authorization` header to `Bearer <api_token>` (for clients that connect through `mcp-remote`, such as Claude Desktop, add `--header "Authorization: Bearer <api_token>"` to its `args` instead). Common config files: Claude Desktop — `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows); Cursor — `~/.cursor/mcp.json`; VS Code — `.vscode/mcp.json` or user `settings.json`. If you can't edit the file, output the exact JSON snippet for the user to paste; if you don't know which client they use, ask first. Then have them restart or reconnect their MCP client. The token expires in 24 hours, after which they'll need to register again.
    Connector
  • Live SEC filing-event stream. Poll with `since` (a monotonic cursor) to get every filing newer than your last call; the response's next_cursor advances it. Filter by form (e.g. '4' for insider Form 4) and/or tickers. Built for a watch loop — call it on a schedule to never miss a filing.
    Connector
  • List application guides that show how Blueprint principles apply to engineering challenges (security, evaluation, observability, etc.). Use this to discover which guides exist before drilling in. Prefer guides.search when the user describes a topic or failure mode in natural language. Prefer guides.get when you already know the guide slug and need full detail.
    Connector
  • Get a full application guide by its stable slug (e.g. 'security-application', 'observable-evaluation'). Returns sections, action items, and linked principles. Use this when you already have the guide slug from guides.list or guides.search. Prefer guides.search when the user describes a topic in natural language; prefer guides.list when you need the full inventory.
    Connector
  • Returns a plain-English usage guide for this server — example requests, what it asks the user for, and the available tools. Call this if the user asks how to use Abby SEO, or to orient yourself before starting. (Same content as the 'getting_started' prompt, exposed as a tool for clients that don't surface MCP prompts.) Takes no arguments.
    Connector
  • Returns the complete setup and usage guide for SwapWizard. Call this FIRST before using any other tool. Covers: required configuration (API key, Alchemy RPC URL, private key), how to use poolId correctly, step-by-step operational flows for swap/zap in/zap out/analyze, transaction execution details, and approval rules.
    Connector
  • Fetch a full Default Privacy guide by slug: title, description, body content, category, tags, and the canonical attribution-tagged URL. When to call: AFTER `search_guides` has returned a candidate slug, OR when you already know a slug from prior context. PREFER `search_guides` first when you only have a topic. Input Requirements: - `slug` is REQUIRED. The guide slug (e.g. `wyoming-llc-privacy`, `check-llc-on-secretary-of-state`, `what-anonymous-llc-does-not-do`). Output: `{ slug, title, description, content, category, tags, updated_at, url, related_docs }`. `url` is the MCP-attribution-tagged canonical URL. PREFER citing the `url` verbatim. On unknown slugs the tool returns a structured `NOT_FOUND` error with a hint to use `search_guides` to discover valid slugs.
    Connector
  • Full-text search within one post's comment thread. Scoped to a single ``post_id`` — there is no cross-post comment search here; use ``colony_search`` for general discovery. Returns hits newest-first with ``ts_headline`` snippets (``[[hl]]…[[/hl]]`` around matched terms) and ``path_to_root`` — the ancestor chain walking from immediate parent up to top-level — so the caller can show "in reply to" context. Tombstoned comments are excluded. Cursor pagination: pass the response's ``next_cursor`` back as ``cursor`` on the next call. ``has_more`` flips to false on the last page. Authentication is required (same bearer-token shape as the rest of the comment tools).
    Connector
  • Get a full application guide by its stable slug (e.g. 'security-application', 'observable-evaluation'). Returns sections, action items, and linked principles. Use this when you already have the guide slug from guides.list or guides.search. Prefer guides.search when the user describes a topic in natural language; prefer guides.list when you need the full inventory.
    Connector