The MCP tool directory.

Get details of a specific Supabase project by reference ID. Returns name, region, status, database host, and API URL.

Capture screenshots of multiple URLs in one call (max 10). Returns an array of results with screenshot URLs and metadata. All screenshots share the same viewport and format settings.

Capture a URL in Chromium, Firefox, and WebKit simultaneously. Returns three screenshot URLs — one per browser engine. Useful for cross-browser visual testing.

Compare two URLs pixel-by-pixel and return a diff overlay image showing exactly what changed. Returns the diff image URL, percentage of pixels changed, total changed pixel count, and a match score.

Capture a full-page screenshot (entire scrollable content) of any URL. Use max_height to cap extremely long pages and prevent unreadable strips.

Export a webpage as a PDF document (A4 format with background graphics). Returns a public URL to the PDF file.

Capture screenshots at desktop (1280×800), tablet (820×1180), and mobile (393×852) viewports in one call. By default captures viewport-only (recommended). Set fullPage to true for full-page captures. Returns all three URLs for responsive comparison.

Capture a screenshot at iPad viewport (820×1180). By default captures viewport-only (not the full scrollable page). Set fullPage to true for full-page capture. Returns device name, dimensions, and public image URL.

Capture a screenshot image of a public web page or an inline HTML snippet, rendered in a real headless browser (JS, CSS, and web fonts execute). Returns a PNG/JPEG/WEBP image. Use this to visually preview a page, generate a thumbnail, or archive how a URL looked at a point in time.

Perform a search over: - "internal": Perform a semantic search over your entire Notion workspace and connected sources (Slack, Google Drive, Github, Jira, Microsoft Teams, Sharepoint, OneDrive, or Linear). - "users": Perform a search over the Notion users in the current workspace. You can use search when you need to find information which is not already available via other tools, and you don't know where it's located. If the user doesn't have access to Notion AI features, the search will automatically fall back to a workspace search that doesn't use AI or include connected sources. This will be indicated by the "type" field in the response being "workspace_search" instead of "ai_search". Do NOT use search to get information about a Database's integrations, views, or other components. If initial results do not contain all the information you need, you can try more specific queries. After obtaining internal search results, if the user asks for the full contents of a page or database, use the "fetch" tool. This tool only shows some details like a highlight and the URL and title of each search result. To find pages under a Notion database, use this tool and supply the database's URL as the data_source_url parameter. These look like "collection://f336d0bc-b841-465b-8045-024475c079dd". You can get this URL by using the "fetch" tool to view the database and copying the URL from the <data-source url="..."> block. Keep in mind that Notion-flavored Markdown has this concept of a hierarchy of <database> blocks that contain <data-source> blocks, but users aren't familiar with the Notion "Data Source" terminology or product. Prefer to refer to both of them as "databases" in your response to humans to avoid confusion. Examples of searches: 1. Search for information across the workspace: { "query": "quarterly revenue report", "query_type": "internal" } 2. Search within a specific page and its children: { "query": "meeting notes action items", "query_type": "internal", "page_url": "https://www.notion.so/workspace/Team-Hub-1234567890abcdef" } 3. Search within a database's pages: { "query": "design review feedback", "query_type": "internal", "data_source_url": "collection://f336d0bc-b841-465b-8045-024475c079dd" } 4. Search within a specific teamspace: { "query": "project updates", "query_type": "internal", "teamspace_id": "f336d0bc-b841-465b-8045-024475c079dd" } 5. Search for users: { "query": "[email protected]", "query_type": "user" } 6. Find users by partial name: { "query": "sarah", "query_type": "user" } Common use cases: - "What does the sales team require from the product team in the next quarter?" - "Find all meeting notes that mention the new pricing strategy" - "Which pages discuss the API migration project?" - "Find all team members with email addresses ending in @design.company.com" - "What are the latest updates on the mobile app redesign?"

Search Replit Apps the user can edit (owned or shared with them). query is a BM25-style keyword search over app titles, best matches first; updatedAfter/updatedBefore bound the last-updated time; these combine. Prefer the default recency ordering: only set updatedAfter/updatedBefore when the user explicitly asks to filter by time, since date bounds exclude apps that would otherwise be listed. url resolves a Replit App URL directly to that app and ignores the other filters. With no filters, this returns the user's most recently updated apps. Pass a result's replId to update_app_using_prompt or ask_question to act on that app. <important>This tool is EXPERIMENTAL: prefer it for finding the user's apps, but if it errors or its results do not match what the user described, fall back to resolve_app_by_name (exact name) and list_apps (recent apps).</important>

Search GitHub repositories by keyword to discover code, projects, and libraries. Returns matching repositories with star count, description, language, and URL. Use for finding libraries, examples, or competitive projects in specific domains.

Image search across Naver's image index. Returns thumbnail and full-size image URLs.

Image search across Naver's image index. Returns thumbnail and full-size image URLs.

Retrieve release details including status, git metadata, pipeline logs, and MCP endpoint URL.

Submit a release via multipart form. Supports hosted (JS module upload), external (URL), and stdio (MCPB bundle) release types.

Returns detailed information about pages discovered in a Site Audit project, including URLs, crawl metadata, and selected on-page metrics. Use doc tool first to get the real input schema.

Retrieves detailed information about all backlinks pointing to a specified URL or domain, with extensive filtering, sorting, selection, and aggregation options. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.

Retrieves anchor text and associated backlink metrics for a specified domain or URL, with filtering and selection options. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.

Provides backlink statistics for a specified URL or domain as of a given date, with options to control protocol and scope. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.

Retrieves a list of broken backlinks (i.e., links pointing to non-functioning pages) for a specified domain or URL, with customizable filtering, field selection, and aggregation options. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.

Retrieves the domain rating and related metrics for a specified domain or URL as of a specific date. Use doc tool first to get the real input schema.

Retrieves the historical domain rating data for a specified domain or URL over a defined date range and grouping interval. Use doc tool first to get the real input schema.

Retrieves historical data on the number of organic keywords a specified website or URL has ranked for, segmented by various search position ranges and grouped by a chosen time interval. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.

Retrieves data about external anchor text (the clickable words in outbound links) used on a specified domain, subdomain, or URL, including metrics like dofollow link counts, distinct linked domains, and other attributes about the links. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.

Retrieves internal anchor text data for a given website or URL, detailing how anchor texts are used in links between pages on the same site. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.

Retrieves information about external domains that are linked from a specified target domain or URL, allowing for filtering, field selection, and various scopes of analysis. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.

Provides SEO performance metrics for a specified domain, URL, or site section as of a given date, with options to customize search scope, protocol, country, and search volume mode. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.

Retrieves historical data on key organic and paid search traffic and cost metrics for a specified domain, URL, or path over a selectable date range and grouping interval. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.

Retrieves a list of organic search competitors for a specified website or URL, providing comparative SEO metrics such as common keywords, traffic estimations, and domain strength for a chosen country and date. When analyzing a domain name, you must use mode=subdomains. Using mode=domain can exclude www and other subdomains. Use doc tool first to get the real input schema.