Skip to main content

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

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.

Metadata

Release files for profile-wrap-mcp 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for profile-wrap-mcp 0.3.0
File Size Uploaded Provenance
profile_wrap_mcp-0.3.0.tar.gz 21.2 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for profile-wrap-mcp 0.3.0
File Interpreter ABI Platform
profile_wrap_mcp-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 32.3 kB

Release files / profile_wrap_mcp-0.3.0.tar.gz

Download URL profile_wrap_mcp-0.3.0.tar.gz
Size 21.2 kB
Tags Source
SHA-256 checksum
How to use checksums
0a9af8941989d1ba9f8b5bd0f69a86396e61d27edaa2b190f429575967640450
BLAKE2b-256 checksum
How to use checksums
6480fcf29f717700d6708316a1b0f49fa758e9ab5338975055453928e79b58d8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Release files / profile_wrap_mcp-0.3.0-py3-none-any.whl

Download URL profile_wrap_mcp-0.3.0-py3-none-any.whl
Size 11.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
06ad686a8de516ea7fb7c7347daf28ed99feb22d29b03c8d6834b4362287485f
BLAKE2b-256 checksum
How to use checksums
57c5b44990549c660768c4d10918010638cee821ea84bdbac533ac09d1af0154
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Security for profile-wrap-mcp 0.3.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for profile_wrap_mcp-0.3.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Release history Release notifications | RSS feed

This release

0.3.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page