mcpField
P
Profile-Wrap

Profile-Wrap

Local
github.comSocial Media1Updated 1d ago

About Profile-Wrap

Profile-Wrap is a stdio MCP server for drafting and reviewing LinkedIn posts in a Profile-Wrap workspace. It supports fact checks and board-based approval, and publishes only drafts a person has explicitly allowed.

Key features

  1. 01Create drafts from topics
  2. 02Run deterministic fact gates
  3. 03Manage unverified facts
  4. 04Read calendar and review board
  5. 05Publish only board-allowed drafts

Use cases

  1. 01Draft posts from verified workspace facts
  2. 02Review claims before publishing
  3. 03Check posting status and schedule
  4. 04Publish a draft after board approval

MCP support

The stdio MCP server provides tools for workspace status, drafting, fact gates, fact management, calendar and review-board access, and publishing. Its publishing tool requires the latest review entry to be an explicit board Allow.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"nj-burrito-profile-wrap": {
"command": "uvx",
"args": [
"profile-wrap-mcp"
],
"env": {
"PROFILE_WRAP_WORKSPACE": "<PROFILE_WRAP_WORKSPACE>"
}
}
}
}
Run commanduvx profile-wrap-mcp
Environment variables to set
PROFILE_WRAP_WORKSPACEAbsolute path of the Profile-Wrap workspace folder (the one holding config/, drafts/, research/). Leave empty to use the default lookup.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiprofile-wrap-mcp0.2.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

profile-wrap-mcp

mcp-name: io.github.NJ-Burrito/profile-wrap-mcp

A stdio MCP server for a Profile-Wrap workspace. It lets an MCP client (Claude Code, Codex, any other) check the workspace, draft a post from a topic, run the fact gate, manage unverified facts and read the review board. It can also post, but only a draft a person already pressed Allow on, on the review board.

Independent, open source (MIT). Not affiliated with LinkedIn. The server talks to LinkedIn only through the official API with your own developer app, and only inside post_allowed.

Tools

ToolWhat it doesWrites
workspace_statusposting mode, pauses and stops, 20 h gap, token state, draft counts, posts todaynothing
update_statusis a newer release on GitHub, and what is new (optional; installs nothing; one cached anonymous read)nothing
calendar_listcontent-calendar entries, optional status filternothing
draft_createnew text draft from a topic with your chosen provider; verified facts only; state draftdrafts/<slug>/
gate_runthe deterministic gate on a draft (numbers, claims, language, banned patterns)gates.json
facts_listthe fact register with each fact's statusnothing
facts_addadds a fact as unverified; a person verifies it in a terminalresearch/facts.md
review_statereview-board state of one draft or all, and whether it was Allowednothing
post_allowedposts one board-Allowed draft; confirm=false (default) is a dry runledger, draft status

Resources: pw://calendar, pw://drafts, pw://drafts/{slug}.

Safety

  • post_allowed refuses every state except allowed (draft, revising, hold, rejected, needs_check, missed, posted, demo), and refuses an allowed status that has no board Allow as the latest entry in the review history.
  • It calls profile_wrap.linkedin.post.publish, the same function as profile-wrap post --now: gate PASS, 20 h gap, one post a day, posting lock, 429/403 stop, pauses, and the ledger row written before anything is sent.
  • No tool reads direct messages, sends connection invitations, comments, likes or verifies a fact.
  • No key or token is ever returned. draft_create sends the topic and your verified facts to the provider you chose.

Install

uvx profile-wrap-mcp --workspace /path/to/your/workspace
claude mcp add profile-wrap -- uvx profile-wrap-mcp --workspace /path/to/your/workspace

Without --workspace the server uses PROFILE_WRAP_WORKSPACE, then the usual Profile-Wrap lookup. More: docs/MCP.md.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.