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 |
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_allowedrefuses every state exceptallowed(draft, revising, hold, rejected, needs_check, missed, posted, demo), and refuses anallowedstatus that has no board Allow as the latest entry in the review history.- It calls
profile_wrap.linkedin.post.publish, the same function asprofile-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_createsends 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.
1 maintainer
Metadata
1 maintainer
Release files for profile-wrap-mcp 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| profile_wrap_mcp-0.2.1.tar.gz | 20.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| profile_wrap_mcp-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.7 kB
Release files / profile_wrap_mcp-0.2.1.tar.gz
| Download URL | profile_wrap_mcp-0.2.1.tar.gz |
|---|---|
| Size | 20.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7b6791d0e7c1b0ec100429b95d4360b1c9037a20caefee9eed467d0f429f876
|
|
BLAKE2b-256 checksum How to use checksums |
bdbf42f34e416ec1346865c8c5c8a77a62d10a11d2fb4a421c502dce479c84e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 16, 2026.
Transparency logRelease files / profile_wrap_mcp-0.2.1-py3-none-any.whl
| Download URL | profile_wrap_mcp-0.2.1-py3-none-any.whl |
|---|---|
| Size | 10.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9704752766560117e8b780ff2dd139c23856d24c5660efa4a3fa39498bdecd63
|
|
BLAKE2b-256 checksum How to use checksums |
86584e32479aeffa4aabf2fd8ff2db1fa4b3776486cbd9bfcac67eee075cd769
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 16, 2026.
Transparency log
