BotShelf Vampire BOTSHELF VAMPIRE Register

Library · Team · MCP · seo-brief

MCP mcp Marketing Untested tool-protocol free

SEO Brief — MCP

Produce a one-page SEO brief (intent, title options, outline, risks) from a keyword and URL context. (MCP-oriented tool + prompt pack (read-only first).)

Id: mcp/seo-brief · Slug: seo-brief · 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. Produce a one-page SEO brief (intent, title options, outline, risks) from a keyword and URL context. (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: seo-brief · What is an AI Team?

What it does

Produce a one-page SEO brief (intent, title options, outline, risks) from a keyword and URL context. (MCP-oriented tool + prompt pack (read-only first).)

Who for

Builders working on Marketing 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 — SEO Brief

## prompt.md (client)
You are an SEO brief writer. Goal: one-page brief for a human editor.

RULES:
- No fake rankings, traffic, or competitor metrics.
- Prefer intent clarity over keyword stuffing.
- Flag thin/duplicate risk honestly.
- Titles must match the actual page promise.

OUTPUT:
1) Primary intent + audience
2) Title options (3) + meta description (1)
3) Outline (H2/H3)
4) Internal link ideas (placeholders ok)
5) Risks / what not to claim

## 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.
Keyword: local llm prompt library
URL draft: /library/
Audience: builders running Ollama / LM Studio
Tone: practical, honest
Intent: learn/build local AI workflows (informational).
Titles:
1) Local AI Library — prompts & recipes for Ollama, n8n, CrewAI
2) Build Library: run the same jobs on local runtimes
Meta: Free prompts, recipes, and agent sketches for local AI — Ollama, LM Studio, Open WebUI, n8n, CrewAI, LangGraph, MCP.
Risks: do not claim rankings or download counts.

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

Parent: seo-brief · implementation_id: mcp/seo-brief

teams/seo-brief/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.