Skip to content
MCP server

FoxPlug

Your coding agent records what you ship; FoxPlug drafts launch posts and a changelog

Status and history

Answered our latest tool-list check 16 hours ago with 11 tools. It will be marked verified after 3 successful checks in 7 days.

Install
Pricing
Freemium
Platforms
Web, API
Runs
Remotely
Version
1.0.0
Listing updated
2 days ago

About FoxPlug

FoxPlug is a freemium MCP server for marketing and seo. It runs as a hosted remote server, so there is nothing to install locally.

FoxPlug presents itself as a chief of staff for a small startup. The MCP connection is the route by which a coding agent logs what it finished, and FoxPlug turns that into drafts: launch posts, a changelog entry and image or video material. Nothing is published automatically; every post or email is written for you to press Send.

The wider product reads a lot more. It says it follows 86 tools covering code, deploys, payments, errors, work trackers and analytics, read-only, and can prepare drafts for 15 places including X, LinkedIn, Bluesky, Mastodon, dev.to, Hashnode, Telegram, Discord and Slack, with newsletter drafts for Mailchimp, beehiiv, Kit, MailerLite, Brevo and Resend on paid plans. A Today brief names one thing to fix, one to say and one to skip, with the number and its source. Stripe access is read-only and a key that can change anything is refused.

Up to five agent keys can be created in the app, and seven coding tools are listed on its integrations page. The free plan covers one project and five updates a day, with a public changelog in FoxPlug's look.

Install

Run in a terminal

claude mcp add --transport http foxplug https://foxplug.com/mcp

Add to Settings → Connectors → Add custom connector

https://foxplug.com/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "foxplug": {
      "url": "https://foxplug.com/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "foxplug": {
      "type": "http",
      "url": "https://foxplug.com/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "foxplug": {
      "serverUrl": "https://foxplug.com/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "foxplug": {
      "type": "http",
      "url": "https://foxplug.com/mcp"
    }
  }
}

Tools this server provides (11)

Read directly from the server.

record_work
Record a build-work summary into FoxPlug as a milestone (source: Claude Code). Call this at the end of a session. It captures what you shipped so FoxPlug can score it and surface the shippable moments in your Radar. It never posts anything. Free — capture is not metered. Do NOT include secrets, keys, or tokens in the summary.
log_update
Tell FoxPlug what you just finished building, in one short plain paragraph. Call it after a change a user would notice (user_facing true) or after plumbing nobody outside needs to hear about (user_facing false, which is kept out of drafts and counts toward "not worth a post"). It never posts anything. Free. Do NOT include secrets, keys, or tokens.
get_brief
This week's brief from FoxPlug: one thing to fix, one to say and one to skip, with where each number came from. Ask it when the founder wonders what to post. Read-only. It does not rebuild the brief; the founder presses Build the brief in FoxPlug.
list_drafts
The latest post drafts FoxPlug wrote for the founder (channel, status, text). Read-only; nothing is posted or changed.
simulate_buyers
Before you merge or ship, ask your buyers. Give the change as the buyer would see it (pricing text, a feature description, launch copy). FoxPlug builds 3 to 5 buyer personas ONLY from evidence the founder already gave it (their site, the feedback requests they connected, what they shipped), each citing its evidence, and returns how each would react: would buy, hesitate or leave, the objection, the
set_plan
Set the current plan, intent, or priorities for a project in FoxPlug (source: Claude Code). Call this when you set or change what a project is working toward, so FoxPlug knows the goal your later work is measured against. It replaces the project's previous current plan. Free — it never posts anything. Do NOT include secrets, keys, or tokens in the plan.
check_drift
Check whether a project's recent work still matches its current plan. FoxPlug compares the plan you set (via set_plan) against the work recorded since, and returns an alignment verdict with any divergences — work that is off-plan, or plan items nothing has moved toward. Read-only judgment; it never posts anything. Free.
get_plan_status
Get where a project stands: its current plan, how much work has been recorded since the plan was set, and the latest drift verdict (if any). Read-only and cheap — it runs no judgment, so use it to pull current state without re-running check_drift. It never posts anything. Free.
what_nobody_knows
What this project shipped that nobody outside it knows about. Counts the milestones worth talking about in a window and how many of them were actually posted, and names the loudest silent ones. Read-only — it generates nothing and posts nothing. Free.
recall
What FoxPlug remembers about this maker, with an epistemic status on every fact: settled (more than one observation, none contradicting), thin (seen once), contested (the evidence disagrees with itself), superseded (replaced by something later — never propose it again). Read-only. Free.
supersede_fact
Mark a remembered fact as finished, so it is never proposed again. Takes the fact id from recall and a REASON — a fact struck out without a reason cannot be restored. This is the only one of these tools that changes anything, and it changes memory, never anything public. Free.

What it does

Agent updates
A coding agent records what it finished and FoxPlug drafts from it.
Today brief
One thing to fix, one to say and one to skip, with sources.
Launch drafts
Posts for X, LinkedIn, Bluesky, Mastodon, dev.to and more.
Public changelog
Free uses FoxPlug's look; paid plans use your brand.
Read-only stack access
Reads 86 tools such as GitHub, Stripe, Vercel and Sentry.
Approval first
Nothing posts or sends until you press Send.

Good for

  • Turn a day of commits into a changelog entry
  • Draft launch posts from what an agent shipped
  • See which failed payments or cancelling customers need a personal note
  • Publish a public changelog for a product

Pricing

Freemium

Free plan with 1 project; Pro and Serial plans are paid, prices not shown

Prices change. Check foxplug.com before you buy.

FoxPlug FAQ

Does FoxPlug post on its own?

No. Everything is drafted and you press Send.

Is there a free plan?

Yes: one project and five updates a day, with a public changelog in FoxPlug's look.

How many agent keys can I create?

Up to five.

Can it change my Stripe account?

No. Stripe access is read-only and a key that can change anything is refused.

Is FoxPlug free?

FoxPlug has a free plan, with paid plans for more usage or features.

How do I add FoxPlug to Claude Code?

Run this command in your terminal: claude mcp add --transport http foxplug https://foxplug.com/mcp

What are the best alternatives to FoxPlug?

The closest alternatives to FoxPlug are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to FoxPlug

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ha MCP

    MCP server

    MCP server for managing and automating Home Assistant from AI assistants

    Runs locally
    • 8 tools
    • Open source
    • 7.9K GitHub stars
    • Productivity