Profile-Wrap

io.github.NJ-BurritoPublished by GitHub account NJ-Burritov0.2.1Updated Oct 24, 2026

Draft, gate and review LinkedIn posts in a Profile-Wrap workspace; posts only board-Allowed drafts.

VerifiedSTDIODesktop onlyProductivity & Workflow Communication & Collaboration

Server details

Identifier: io.github.NJ-Burrito/profile-wrap-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Oct 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account NJ-Burrito for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.NJ-Burrito%2Fprofile-wrap-mcp.svg)](https://sourceweft.com/mcp/io.github.NJ-Burrito%2Fprofile-wrap-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local stdio MCP server for a Profile-Wrap workspace that lets an assistant check status, draft LinkedIn posts, run a fact gate, manage facts and read the post

What you can do: Check workspace status, posting mode, pauses, token state and draft counts, and look up newer releases on GitHub (read-only). List content-calendar entries with an optional status filter. Create a new text draft from a topic using a chosen provider, restricted to verified facts. Run the deterministic gate on a draft for numbers, claims, language and banned patterns. List the fact register and add facts as unverified for a person to confirm. Read review-board state per draft or overall, and post one board-Allowed draft, with a dry run by default.
When to use it: Use it when you keep a Profile-Wrap workspace and want an assistant to help draft, gate and review LinkedIn posts inside that workflow, while keeping publishing behind a human Allow on the review board.
Requirements: Runs locally over stdio, launched with uvx from the profile-wrap-mcp PyPI package. Needs a Profile-Wrap workspace path, passed as --workspace or the PROFILE_WRAP_WORKSPACE environment variable, otherwise the default lookup is used. Posting needs your own LinkedIn developer app and its API credentials. Desktop only.

Before you install

post_allowed publishes to LinkedIn, though only for a draft whose latest review-board entry is Allow; confirm=false is a dry run. Draft creation sends the topic and your verified facts to the chosen provider. No key or token is returned, and no tool reads messages, sends invitations, comments or likes. Added facts stay unverified until a person confirms them.

Installation

In SourceWeft

Open Profile-Wrap in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Tool	What it does	Writes
`workspace_status`	posting mode, pauses and stops, 20 h gap, token state, draft counts, posts today	nothing
`update_status`	is a newer release on GitHub, and what is new (optional; installs nothing; one cached anonymous read)	nothing
`calendar_list`	content-calendar entries, optional status filter	nothing
`draft_create`	new text draft from a topic with your chosen provider; verified facts only; state `draft`	`drafts/<slug>/`
`gate_run`	the deterministic gate on a draft (numbers, claims, language, banned patterns)	`gates.json`
`facts_list`	the fact register with each fact's status	nothing
`facts_add`	adds a fact as unverified; a person verifies it in a terminal	`research/facts.md`
`review_state`	review-board state of one draft or all, and whether it was Allowed	nothing
`post_allowed`	posts one board-Allowed draft; `confirm=false` (default) is a dry run	ledger, 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

bash

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

uvx profile-wrap-mcp --workspace /path/to/your/workspaceclaude 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.

Source: mcp/README.md at commit e1fcb21

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.2.1LatestOct 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts