MCP Tool Directory

Get the complete Next.js 15+ documentation (~2.5MB, ~320,000 tokens). WARNING: This returns ~320,000 tokens. Only use with LLMs that support large context windows (100k+ tokens). For smaller contexts, use 'search_nextjs_docs' instead. Covers: App Router, Server Components, Client Components, routing, layouts, pages, data fetching, Server Actions, middleware, deployment, and optimization.

Get detailed information for a specific GitHub notification, always call this tool when the user asks for details about a specific notification, if you don't know the ID list notifications first.

Fetch server-curated prompt contracts that define required onboarding outputs. Use this when an agent needs exact formatting/expectations before generating: - clarifications - conversation transcript - market positioning - keywords/subreddits Use `artifact` for focused contracts: - clarifications - market_position - conversation - keywords - subreddits

Canonical onboarding progress view for a product/session. Returns: - current phase - next required action - prompt-pack ack state - targeting approval state - missing artifacts + readiness blockers Use this for recovery if a previous onboarding run was partial or failed.

Gets details for an organization. Includes subscription plan.

Get complete page information including metadata, content preview, and citations summary.

Get the citations list for a specific page.

Get only the article content without citations or metadata.

Extract comprehensive metadata from a web page including title, description, Open Graph tags, Twitter cards, and other meta information.

Extract a specific section from an article by header name.

Get a list of all section headers in an article.

Retrieve documentation for a specific abstracted pattern. Patterns are organized into: layouts (app-header, sidebar-layout, auth-layout, overlay-navigation), pages (hero-section, pricing-page, blog-layout), and features (animations, dark-mode). Patterns include implementation details, code examples, accessibility considerations, and dependencies.

Get season-level pitching data from FanGraphs. Args: start_season: First season to retrieve data from end_season: Final season to retrieve data from. If None, returns only start_season. league: Either "all", "nl", "al", or "mnl" qual: Minimum number of plate appearances to be included ind: 1 for individual season level, 0 for aggregate data Returns: Dictionary containing pitching stats from FanGraphs

Get all pitching stats for a set season. If no argument is supplied, gives stats for current season to date.

Get all pitching stats for a set time range. This can be the past week, the month of August, anything. Just supply the start and end date in YYYY-MM-DD format.

Get full details of a specific place or subway station in Seoul by its ID. Args: id: The unique place ID (e.g., "toilet_00001", "pharmacy_001", "wifi_00001", "aed_00001", "tourist_info_01"). Returns: Complete place information including location, services, hours, and accessibility, or an error message if not found.

Returns a dataframe of all split stats for a given player. If player_info is True, this will also return a dictionary that includes player position, handedness, height, weight, position, and team

Returns a list of current season or career stat data for a given player.

Lookup playerIDs (MLB AM, bbref, retrosheet, FG) for a given player Args: last (str, required): Player's last name. first (str, optional): Player's first name. Defaults to None. fuzzy (bool, optional): In case of typos, returns players with names close to input. Defaults to False. Returns: pd.DataFrame: DataFrame of playerIDs, name, years played

**[REAL-TIME API]** Get the total number of posts for a specific tag. Use this when: - You want to know how many posts exist for a character/tag BEFORE collecting data - You need to estimate collection time and resources - You want to verify data completeness after collection Returns only the post count. Use danbooru-turso-mcp.collect_and_save for actual data collection.

**[REAL-TIME API]** Extract all tags from a specific Danbooru post by ID or URL by querying Danbooru API directly. Use this when: - You want to get ALL tags from a single post in real-time - You need tag categories and counts for a specific post For analyzing tag statistics across multiple posts, use 'get_character_tags'.

Return current tool pricing and Solana payment details. Includes USDC rates, wallet/mint, free-tier limits, and transaction instructions.

Get full details for a product by slug, including MCP integration data and agent readiness scores. Response: { p: { slug, name, tagline, description, websiteUrl, logoUrl, pricingModel, currentScore (0-100), tier (free|verified|featured), unverified (true on free only), verifiedAt (ISO; absent if never crawled), categories[] }, mcp?: { hasMcpSupport, totalToolCount, servers[] }, agentReadiness?: { compositeScore (0-100), aiSummary } }. Errors: { error: { code: 'not_found', ... } }.

Get MCP server setup instructions for a product. Returns available servers, their tools, connection details, and whether they support remote (hosted) access. Response when MCP support exists: { product: { slug, name, websiteUrl, tier, unverified, verifiedAt }, hasMcpSupport: true, totalToolCount, servers[], agentReadiness? }. Response when product exists but lacks MCP: { product: {...}, hasMcpSupport: false, message }. Errors: { error: { code: 'not_found', ... } }.

Get nested folders and products for a client, equivalent to frontend product tree.

Gets details for a Supabase project.

Get detailed information about a WebSim project by its ID. Perfect for 'Show me project [ID]' or 'Tell me about project [ID]' questions.

Get detailed information about a WebSim project using the owner's username and project slug. Perfect for 'Show me @username/project-slug' or 'Tell me about [username]/[slug]' questions.

Gets the API URL for a project.

Gets all publishable API keys for a project, including legacy anon keys (JWT-based) and modern publishable keys (format: sb_publishable_...). Publishable keys are recommended for new applications due to better security and independent rotation. Legacy anon keys are included for compatibility, as many LLMs are pretrained on them. Disabled keys are indicated by the "disabled" field; only use keys where disabled is false or undefined.