# RanklyBee Muse connector From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta. ## RanklyBee SEO research, content planning, lead generation, and backlink submission for small business websites - Record: https://musedirectory.ai/connector/ranklybee - Category: Marketing & Ads - Developer: RanklyBee (https://ranklybee.com/mcp) - Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse. - Health: Working, 3362ms, checked 2026-10-29T15:56:31Z - Endpoint: https://api.ranklybee.com/mcp - Auth: No account needed; Pricing: unknown - Screening: Screened, no issues found (2026-10-29T15:56:31Z) - Source: Found in the official MCP Registry (io.github.dazhiyu0235/ranklybee) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.dazhiyu0235%2Franklybee Connects to RanklyBee's SEO platform to manage projects, analyze websites, generate and publish content plans, track leads from search and social, and automate backlink submissions to third-party sites. Example request: "Show me hot leads from my keyword monitoring and move the most promising ones to my contact queue" How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use RanklyBee to help me. It is a free service with an MCP server at https://api.ranklybee.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer. Tools: - list_projects: List the signed-in user's Projects with their role and websites. Start here to get a projectId. - list_backlink_submission_projects: List the signed-in user's Projects and their active Site details so the user can choose a target without knowing an internal Project ID. - get_backlink_submission_profile: Read the current active Site's backlink submission profile and readiness state. - list_backlink_submission_sources: List visible, available backlink sources that have a supported submission destination. - preflight_backlink_submission: Check paid access, profile confirmation, source policy, inventory, duplicate backlinks, and daily capacity before creating a submission job. - create_backlink_submission: After user review and approval, create one idempotent submission job in waiting_human state. This does not click the third-party site's final submit button. - get_backlink_submission: Read the current state and recorded outcome of a backlink submission job. - record_backlink_submission_outcome: Record the result after a user-approved browser interaction. Use needs_verification for CAPTCHA, MFA, email verification, rate limits, or ambiguous results. - list_leads: List scored leads for a Project, newest first. Filter by tier (hot, warm, explore), stage, platform, or text. Each lead has the evidence quote that shows the buying intent and a link to the original post. - get_lead: Read one lead with its score, evidence quote, reason, stage, and link. - list_lead_keywords: List the monitoring keywords (search phrases and platforms) for a Project. - move_lead_stage: Move a lead to to_qualify, to_contact, in_conversation, or closed. This fires any stage-changed automations the user configured. - list_sites: List the websites in a Project. Most tools need a siteId from this list. - get_site_profile: Read what Ranklybee knows about a website: positioning, audience, products, competitors, and the latest analysis job. - update_site_profile: Replace the editable site profile. Read it with get_site_profile first and send every field back, changing only what the user asked for. - analyze_site: Crawl the website again and rebuild its profile. Runs in the background; poll get_site_profile for the result. - get_plan_usage: Read how much of each plan allowance the Project has used in the current period. - get_content_plan: Read the latest content plan for a website with its scheduled article briefs. Returns null when no plan exists. - generate_content_plan: Generate a new content plan from the site profile and keyword research. Uses the plan's content allowance. - activate_content_plan: Start a reviewed content plan so its briefs are written on their scheduled dates. - decide_content_plan: Approve or reject a whole content plan. - decide_content_brief: Approve or reject one article brief in a content plan. - reschedule_content_brief: Move an article brief to another date (YYYY-MM-DD) on the content calendar. - update_content_brief_instructions: Set the notes the writer follows for one article brief. Send an empty string to clear them. - update_content_brief_keyword: Change the target keyword of one article brief. - search_article_keywords: Look up keyword ideas for a seed phrase with volume, difficulty, and whether each is already in the plan. The ideas are saved to the website's keyword list. - list_article_keywords: List the keywords saved for a website's articles. - add_article_keywords: Add keywords to the content plan as article briefs, optionally on a given date. Returns the keywords that were skipped and why. - import_article_keywords: Save keywords to the website's keyword list without scheduling articles for them. - remove_article_keywords: Remove keywords from the website's saved keyword list. - list_articles: List a website's articles, newest first, with their state and publication. Each item is large, so pass a small limit such as 10 and page with offset. - get_article: Read one article with its full content, quality checks, and publication state. - generate_article: Write the article for an approved brief. Uses the plan's article allowance and takes a few minutes; poll get_article. - update_article: Replace an article's editable content. Read it with get_article first and send every content field back. - regenerate_article_fields: Rewrite the chosen fields of an article with AI. - submit_article_for_review: Send a draft article to the approval step. - decide_article: Approve or reject an article that is waiting for approval. - list_cms_connections: List the CMS connections an article can be published to. - publish_article: Publish an approved article to a connected CMS. The article goes live on the user's website, so confirm with the user first. - verify_article_publication: Record the live URL of an article the user published by hand, after checking the page. Screening checks: - MCP handshake: pass (Answered in 3362ms) - Domain against threat feeds (Cloudflare security DNS): pass (api.ranklybee.com, ranklybee.com not flagged) - Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published) - Hidden instructions or invisible characters in tool text: pass (120 tools read, nothing found) - Inputs asking for passwords, card numbers or seed phrases: pass (None found) - Domain and redirects: pass (Domain registered 307 days ago) - AI review of purpose and tool behavior: pass (No concerns)