BotShelf Vampire BOTSHELF VAMPIRE Register

Library · Team · MCP · writing-draft

MCP mcp Content Untested tool-protocol free

Writing Draft — MCP

Draft a clear first pass from notes — then stop for human edit. No fake claims or invented metrics. (MCP-oriented tool + prompt pack (read-only first).)

Id: mcp/writing-draft · Slug: writing-draft · Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.

What is this

MCP for MCP. Draft a clear first pass from notes — then stop for human edit. No fake claims or invented metrics. (MCP-oriented tool + prompt pack (read-only first).)

How this runtime fits

This MCP pack is an MCP integration / tool-enabled agent surface for the parent AI Team. Multi-agent language applies only when a host actually composes multiple agents around these tools.

Parent AI Team: writing-draft · What is an AI Team?

What it does

Draft a clear first pass from notes — then stop for human edit. No fake claims or invented metrics. (MCP-oriented tool + prompt pack (read-only first).)

Who for

Builders working on Content jobs who can run MCP themselves.

Need to run

How to use

  1. Review server_hints.md and implement only allowlisted read-only tools.
  2. Load prompt.md as the client system prompt.
  3. Run one Example in query with tools off; then enable library_search only.
  4. Confirm path allowlist before any file read tool.

Limitations

Test status

Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.

# MCP pack — Writing Draft

## prompt.md (client)
You are a first-draft writer. Goal: clear prose from notes — then stop.

RULES:
- Do not invent quotes, customers, metrics, or legal claims.
- Mark gaps as [NEED FACT].
- Keep tone plain. Prefer short paragraphs.
- One draft only; wait for human edit directions.

OUTPUT:
1) Working title
2) Draft body
3) [NEED FACT] list
4) Suggested next edit pass

## server_hints.md
Expose only read-only tools for stage 1, for example:
- `library_search` — search local catalog snippets the user installed
- `fetch_local_file` — read a path under an allowlisted directory

Tool design rules:
- No tool that sends email, posts to social, or charges payment.
- No tool that reads `~/.ssh`, `.env`, or browser cookie DBs.
- Arguments must be schema-validated; reject path traversal.
- Log tool calls for the human operator.

Example tool schema (illustrative JSON):
```json
{
  "name": "library_search",
  "description": "Search local BotShelf library snippets",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {"type": "string", "minLength": 1, "maxLength": 200}
    },
    "required": ["query"]
  }
}
```

Wire this pack into an MCP-aware client with tools disabled until the allowlist is reviewed.
Notes: announce Build Library stage 1. Free. Local AI. Not replacing marketplace teams. Soft CTA to sell/fork.
Audience: AI builders
Title: Build Library stage 1 is on the shelf
Draft: BotShelf Vampire now has a free Build Library for local AI users…
[NEED FACT]: exact item count at publish
Next edit: tighten CTA; keep marketplace distinction.

Protocol-level pack. Prefer read-only tools. Never ship credentials inside MCP configs.

Parent: writing-draft · implementation_id: mcp/writing-draft

teams/writing-draft/mcp · commit eb87e8e049fdf9908e438305ff827c7b617505b5 · license: free-use-at-own-risk

Structural check: PASS · env: structural (structural only — does not set Verified)

Soft thematic links only — not identity merges. Marketplace Teams ≠ Library AI Team records.