LinkBunny

LOCAL MCP FOR LINK EXCHANGES

Use LinkBunny from your coding agent with MCP

Run LinkBunny locally in Codex, Claude Code, or VS Code. Your agent can add sites, check for link requests, report published links, and reject requests that do not fit.

Open setup guide

IN YOUR SITE WORKFLOW

Use LinkBunny in your existing site workflow

LinkBunny MCP lets your coding agent handle LinkBunny from the same workflow it uses to work on your sites.

Your agent can check for link requests, decide whether they fit, and report or reject them. Site edits and publishing still use your project's normal workflow.

FIVE TOOLS FOR SITES AND LINK REQUESTS

Add sites and handle link requests

create_profile

Add one site to LinkBunny. A subscription is required. Save the profile ID, then wait for review instead of repeatedly checking.

update_profile

Update all LinkBunny settings for a site you own. Changing the target or inventory URL sends the site through review again.

check_in

Check for one link request when the owner asks or gives the agent a limited check-in task. LinkBunny may return the existing request or reserve a new one.

report_assignment

After a link is published, confirm it is live with nofollow, then report the page and anchor text to LinkBunny when the owner asks.

reject_assignment

When the owner asks, reject a link request that does not fit using a supported reason. This does not change the site; rejecting it means excluding that URL from future matches and making the target available to another site.

PROMPTS TO TRY

Paste this to your agent

Add a site

Add our site to LinkBunny. Suggest for me the URL prefix, where links may be added, anchor text, and category.

Check for a link request

Check in

Report a published link

Check that the published page is inside the site's inventory area and the link is live with nofollow. Show me the report before sending it.

SITE CHANGES

Keep site changes in your normal workflow

Your agent runs a LinkBunny tool when you ask or give it a task with clear limits. A link request never changes or publishes your site. Site edits, publishing, and live checks stay in your normal workflow.

TOKENS AND LIMITS

Keep the API token out of prompts and source code

Load the API token from the private source described in the setup guide. The server does not poll, retry on its own, or chain tools. It needs Node.js 22 or later. Some actions also need an active subscription or an approved site. Installing the package does not guarantee a link request or an SEO result.

GUIDANCE AND CHECKS

MCP includes the workflow guidance

Read the bundled guidance

The released MCP serves linkbunny://guidance/skill, with the workflow rules captured for that package version. Your agent should read it before using a tool.

The API checks marketplace state

LinkBunny's API checks site ownership, subscriptions, site review, and inventory boundaries. It records the final status of each link request.

SETUP GUIDE

Use the Docs for setup

The Docs have the current setup for Codex, Claude Code, and VS Code, including loading the token, checking the setup, upgrading, and removing the server. If your agent does not support MCP, use the standalone LinkBunny Skill instead.

Open setup guide

DIRECT LINE TO THE FOUNDER

Questions about fit or setup?

I’m Hwee-Boon, the founder. Ask about LinkBunny, site quality, or setup, and I’ll reply by email.

0 / 2,000⌘/Ctrl + Enter to send