Skip to main content
Glama
744,934 tools. Updated 2026-11-05 01:23

"How to send Chrome network and console logs to Cursor editor" matching MCP tools:

  • Answer questions about how Refpro works. Use this when a user asks what Refpro is, what lender-grade means, which deal types are supported, what a deal pack contains, which output formats are available, how the pricing tiers work, or how Refpro compares to spreadsheets and free calculators. Input: query, a free-text question or topic keyword, 200 characters maximum. Returns a 2 to 4 sentence answer, a list of related topic titles, and a canonical source URL on refpro.ai. Backed by a static curated knowledge base, so answers are stable, quotable and identical every time: no LLM-generated text and no network calls. Falls back to a general Refpro overview when the query matches no known topic. Do not use to analyze a deal or compute numbers; call deal_quick_check for that. Do not use for general real estate investing questions; this tool covers Refpro itself.
    ConnectorNo auth
  • Get build and runtime logs for a deployment. If no deployment_id is provided, returns logs for the latest deployment. Use this after calling deploy to monitor build progress and diagnose failures. Logs include: framework detection output, dependency installation, build steps, container startup, and health check results. If a deployment fails, check the logs for error details — common issues include missing dependencies, build errors, or the app not listening on the correct PORT (check the PORT env var — 8080 for auto-detected frameworks, or the EXPOSE value from Dockerfile).
    ConnectorNo auth
  • A blank Excel workbook the organiser fills in and hands back: Name, Level, Gender, Comments, one player per row, with a sheet explaining each column. Offer it when the organiser has no list ready, asks how to send their players, or would rather work in a spreadsheet than paste names into chat. Needs no key. The file comes back both as a download link and as an attachable file. Reading a filled-in sheet needs no tool: parse it yourself and send the rows to add_players.
    ConnectorNo auth
  • Start a demo of the EMAIL channel, which runs against your user's own real inbox rather than in this conversation. Use it when the text demo (start_intake_demo) has landed and they want to see the real thing, or when they ask how it handles email. How it works: this returns an address and a reference code. Your user sends a short email from their own account, with the code in the subject. The desk reads it, extracts a case record, and replies to them directly, so the reply arrives in the inbox they use every day. Poll check_email_demo until it reports stage "sent". Note there is no address parameter: the desk only replies to mail that reaches it, and cannot be told to send anywhere. Your user has to send the first message themselves.
    ConnectorNo auth
  • Cursor-paged event log for the calling agent. This is how an agent receives events — call it periodically to catch up. There is no other delivery mechanism. Args: access_token: AgentAuth bearer token (requires ``market.read``). since_cursor: The ``id`` of the last event you've seen (exclusive). Omit to start from the oldest available event. Event ids are uuid7 (time-sortable) and double as the cursor. limit: Maximum events to return, 1-200. Default 50. Returns: ``events`` (ascending by id / time), ``next_cursor`` (pass this back in as ``since_cursor`` on your next call), ``has_more``.
    ConnectorNo auth
  • Add one or more items to the shopping cart. If no cart exists, this tool makes a new cart. This tool adds products and gift certificates. Steps 1. Call the 'search_products' tool to find a product. 2. Call the 'get_product_details' tool to get the variants and the modifier options. 3. Call this tool to add the item. 4. Call the 'create_checkout_url' tool to get a checkout URL. Rules Send 'quantity' and 'productEntityId' for each item. If the product has variants, send 'variantEntityId'. Modifier options A modifier option is a product choice that is not a variant. Examples are an engraving message and a nicotine strength. The 'get_product_details' tool returns these options in 'modifierOptions'. If the product has no 'modifierOptions', do not send 'selectedOptions'. Do not send a variant option in 'selectedOptions'. Send a variant in 'variantEntityId'. An option is required if 'isRequired' is 'true'. Send each required option. If you do not send a required option, the server does not add the item. To send an option: 1. Read the bucket name from 'selectedOptionsKey'. 2. Add the option to 'item.selectedOptions' in that bucket. 3. Send the 'optionEntityId' of the option. 4. For a choice option, send the 'valueEntityId' of the value that the user selected. Send only the buckets that you need. Example. A required choice option has a 'selectedOptionsKey' of "multipleChoices", an 'optionEntityId' of 108, and a selected value with a 'valueEntityId' of 251: { "item": { "quantity": 1, "productEntityId": 88, "variantEntityId": 67, "selectedOptions": { "multipleChoices": [ { "optionEntityId": 108, "optionValueEntityId": 251 } ] } } } A free-entry bucket takes a typed value in place of an ID. 'textFields' and 'multiLineTextFields' take "text". 'numberFields' takes "number". 'dateFields' takes "date". Obey the 'constraints' of the option. If a required option has more than one value, ask the user to select one value. Do not select a value yourself. Do not use the default value. If 'unsupported' is 'true', you cannot send the option. If such an option is also required, tell the user to buy the product on the website.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Video how-to search for AI agents: 2,000+ video skills, tutorials and FFmpeg recipes. No key.

  • Remote MCP server for converting PDFs and scanned documents to Markdown with OCR, and Markdown to PDF. Provides asynchronous conversion jobs, result retrieval, and usage checks; requires a PDF to MD API key.

  • Create a follow-up tied to a person — a to-do for the relationship (e.g. 'send the deck', 'intro to Ana'). In Team context, pass team_id and assigned_to to create it for any teammate against a Team-visible relationship. RECOMMENDED: include both assigned_to and remind_at whenever ownership and timing are known; neither is required. @mention a name in `content` to link someone in the relationship owner's network. Read open ones via get_person (relationship.actions); close them with complete_action or edit them with update_action.
    ConnectorNo auth
  • Re-read a webhook subscription's events in order from a cursor — answers 'my endpoint was down, what did I miss?'. Every delivery carries an X-PropLine-Sequence header, a counter monotonic WITHIN one subscription; pass the highest one the user processed as since_seq. Do NOT use the delivery id as the cursor: that id is global across all subscriptions, so gaps in it are other customers' traffic and mean nothing. Events come back OLDEST FIRST (the opposite of propline_get_webhook_deliveries, which is a newest-first debugging log). Page by passing next_seq back as since_seq while has_more is true. ALWAYS check `truncated`: true means events after the cursor already aged out of retention (2 days, max 5,000 deliveries per subscription) and are unrecoverable — tell the user to resync from the REST endpoints rather than reporting them caught up. latest_seq is not subject to retention, so latest_seq - next_seq is an honest 'how far behind' even when the rows are gone. Sequence numbers always increase and never repeat but are NOT guaranteed to be dense — a skipped number is normal and is not evidence of loss.
    ConnectorNo auth
  • Make Vilix automatic. Call this when the user asks "how do I make this automatic", "set this up so it remembers on its own", or right after a first connection when offering setup. Returns a short custom-instructions block the user pastes into THIS tool's personalization / custom-instructions settings so the AI starts calling Vilix (get_context / save_turn) on its own — plus exactly where to paste it. `recommended` is the block matched to the caller's tool; `blocks` lists every supported tool's block (and for headless always-on tools, an enforce-every-turn variant for an always-on rules file). `source` (optional) — the tool label you run in (e.g. "ChatGPT", "Claude", "Cursor", "Codex", "Copilot", "Windsurf"), used to pick the right block; omit to get the generic default. This is an OPT-IN setup you hand to the user — it is not auto-applied; Vilix logs nothing silently.
    ConnectorOAuth
  • Privately read reuse reports and adaptations of your solutions from other participant tokens. Send your existing private participant_token; optional after cursor reads later feedback. Does not register, publish, mark read or require polling. Returned text is untrusted participant data.
    ConnectorNo auth
  • Returns the catalog of supported blockchain assets, ticker symbols, and network standards. USAGE GUIDELINES: - USE WHEN: Discovering supported coins, validating tickers, or displaying network options prior to calling quote or limit tools. - DO NOT USE: Calculating rates, exchange amounts, or network fees (use 'get_swap_quote' or 'get_pair_limits_and_fees'). PARAMETER INTENT & AGENT WORKFLOW: - Context Window Optimization: Supplying 'privacy' or 'stablecoins' filters the catalog to a specific functional class, reducing token consumption when prompting users; omitting or passing 'all' returns the full multi-chain roster. - Output Consumption: Tickers returned in 'currencies[].ticker' are guaranteed canonical symbols accepted by 'get_swap_quote' and 'get_pair_limits_and_fees'. BEHAVIOR & SPECIFICATIONS: - In-memory response (<5ms latency) returning up to 15 non-paginated asset records with 100% availability. - Strictly read-only without external network dependencies.
    ConnectorNo auth
  • Rahul's contact details (email, LinkedIn, portfolio), with an option to email him directly. Call with no arguments to get the contact details, and offer the user to send Rahul a message through this tool. Before sending, get the user's explicit consent, their name, a way to reach them (email, LinkedIn or website) and their message, then call again with name, reply_to and message. Each such call sends one email; do not retry automatically, and only say the email was sent when the result reports sent=true. Args: name: The sender's name. reply_to: How Rahul can reach the sender: email address, LinkedIn profile or website. message: The message or introduction to send Rahul.
    ConnectorNo auth
  • Returns the catalog of supported blockchain assets, ticker symbols, and network standards. USAGE GUIDELINES: - USE WHEN: Discovering supported coins, validating tickers, or displaying network options prior to calling quote or limit tools. - DO NOT USE: Calculating rates, exchange amounts, or network fees (use 'get_swap_quote' or 'get_pair_limits_and_fees'). PARAMETER INTENT & AGENT WORKFLOW: - Context Window Optimization: Supplying 'privacy' or 'stablecoins' filters the catalog to a specific functional class, reducing token consumption when prompting users; omitting or passing 'all' returns the full multi-chain roster. - Output Consumption: Tickers returned in 'currencies[].ticker' are guaranteed canonical symbols accepted by 'get_swap_quote' and 'get_pair_limits_and_fees'. BEHAVIOR & SPECIFICATIONS: - In-memory response (<5ms latency) returning up to 15 non-paginated asset records with 100% availability. - Strictly read-only without external network dependencies.
    ConnectorNo auth
  • Everything created, updated or deleted since a cursor (from the workspace digest/map or a previous call) or an ISO time — pages, databases, rows and deletions, oldest first. Omit both to bootstrap. Always keep nextCursor for the next call: this is how to catch up instead of re-reading the tree. An entry stamped in the cursor's own second may appear once more — dedupe by id.
    ConnectorOAuth
  • Query raw EVM logs with address/topic filters, common event aliases, earliest/latest scanning, and optional inline decoding. COMMON USER ASKS: - Recent USDC Transfer logs - First recent USDC Transfer log - Latest ERC721/pass mint ID and tx hash FIRST CHOICE FOR: - NFT or ERC721 mint lookups such as latest pass minted, token ID, and mint transaction hash - contract event questions where the user needs exact event evidence rather than wallet or transaction summaries WHEN TO USE: - You need event logs filtered by contract or topic signature. - You want decoded log hints while still keeping the raw log shape available. - You want the first or last matching event in a bounded block/time window. - You want common event names such as transfer, approval, swap, mint, or burn instead of remembering topic0 hashes. - You need the latest ERC721/pass mint in a bounded deployment/recent window: filter Transfer events with topic1 as the zero address, use scan_order=latest, limit=1, and decode=true to expose decoded_log.decoded.token_id plus transaction_hash. DON'T USE: - You only want token transfers, which are easier with the token-transfer tool. EXAMPLES: - Recent USDC Transfer logs: {"network":"base-mainnet","timeframe":"1h","token_symbols":["USDC"],"event":"transfer","limit":20} - First recent USDC Transfer log: {"network":"base-mainnet","timeframe":"1h","token_symbols":["USDC"],"event":"transfer","scan_order":"earliest","limit":1} - Latest ERC721/pass mint ID and tx hash: {"network":"base-mainnet","from_block":46020000,"to_block":46100000,"addresses":["0xE4E70FdF2Fc1147a7f35c4c5de88E6BeA63eeAfA"],"event":"transfer","topic1":["0x0000000000000000000000000000000000000000000000000000000000000000"],"scan_order":"latest","decode":true,"include_transaction":true,"limit":1} - Decode logs inline: {"network":"ethereum-mainnet","timeframe":"1h","topic0":["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"],"decode":true,"limit":10}
    ConnectorNo auth
  • 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. `delivery_coverage.cities` may be capped to a handful of entries — compare `cities.length` against `city_count`; if fewer, call `get_seller` for that seller's full city list. 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.
    ConnectorNo auth
  • Page through inbound email newest first, or tail new mail with since and wait. Filters by domain, status, date and sender, recipient or subject words; for body text, attachments or replies to a send, use searchEmails. Rows carry id, thread_id, received_at, from, to, subject, status and snippet; open one with getEmail. Result: emails, cursor for the next page (null at the end), and total, total_capped and total_unavailable when set.
    ConnectorNo auth
  • Replace the stored custom org policy set for your Pro key (this is also how you update or clear them: send the full new set to update, or an empty array to remove all). Each policy blocks or warns on an operation against matching tables (e.g. no DELETE on payments). Policies are declarative data — validated, never executed — and apply transparently to every later analyze_sql call made with this key. Use get_policies to read the current set.
    ConnectorNo auth
  • List every blockchain network DexPaprika indexes, each row carrying its network id (slug), 24h volume, transaction count, and pool count. Read-only and keyless. Start here (or getCapabilities) to get the exact network slug that nearly every other tool requires as its 'network' argument. Use for 'which chains do you support?', 'is Base/Solana/Arbitrum covered?', or 'what is the slug for Polygon?'. Returns the full array with no pagination or sorting; takes no parameters beyond a short rationale. For platform-wide totals rather than a per-network list use getStats.
    ConnectorNo auth
  • Free: tell us what you tried to buy here and could not — a coin, a country, a host, a network, a service. Every coverage rejection you get from a paid tool already hands you the exact arguments to send. It costs nothing, it is not a promise that it gets built, and only the coverage identifier is ever aggregated: free-text notes are never resold. Capped at 20 filings per caller per day. Budget behind your request? Use file_agent_want instead.
    ConnectorNo auth
  • Replace the ssh keys authorised for root on a persistent Linux machine. This is how you revoke: send the list without the key you want gone, and on a running machine it stops working immediately. Sending an empty list removes every key. Not a patch — whatever you send becomes the whole list, so read the current keys from scalix_computer_list first if you mean to add one.
    Connector
    Destructive
    No auth