BotShelf Vampire BOTSHELF VAMPIRE Register

MCP

BotShelf Vampire as an MCP server (read-only)

Point an MCP client at one address and your AI tool can search the shelf and read the full text of the free items. No account, no key.

https://botshelfvampire.com/api/mcp

Transport: Streamable HTTP. Each request gets one JSON reply (a notification gets an empty 202). It keeps no session and offers no event stream.

Try it now

The example uses Codex CLI, the one client with a recorded run. The other clients have their own sections below.

  1. Add the server: codex mcp add botshelf --url https://botshelfvampire.com/api/mcp
  2. Ask your tool: Use the botshelf tools to get the item /library/claude-code/code-review/ and show me its full text.
  3. It calls get_item and shows the text of Code Review for Claude Code, the same text as on its page. To find other items, ask it to search the shelf, for example for meeting notes.

The server is listed in the MCP Registry as com.botshelfvampire/botshelf (registry entry, read back as active on 2026-11-18). A registry entry is a directory listing, not an endorsement.

What it can do

ToolWhat it returns
search_itemsSearch by words, with optional filters (kind, where it runs, topic, access, recorded check). Returns short cards.
get_itemOne item by id. Returns its card and, when the item has a plain file that is open without sign-up, the full text (in parts when long).
list_itemsItems in shelf order, a page at a time, with the same filters. Also returns how many items each kind holds.

It reads the same public index as Explore and the same plain files the item pages link to. Nothing else.

Claude Code

Run this once:

claude mcp add --transport http botshelf https://botshelfvampire.com/api/mcp

That saves it for you alone, in the current project. To use it in all your projects, add --scope user:

claude mcp add --transport http botshelf --scope user https://botshelfvampire.com/api/mcp

Or share it with a project: put this in .mcp.json at the project root.

{
  "mcpServers": {
    "botshelf": {
      "type": "http",
      "url": "https://botshelfvampire.com/api/mcp"
    }
  }
}

Source: Claude Code: Connect to tools via MCP, read 2026-11-18.

Grok Build

grok mcp add --transport http botshelf https://botshelfvampire.com/api/mcp

Add --scope project to write it to .grok/config.toml in the current directory instead. Or put this in ~/.grok/config.toml yourself:

[mcp_servers.botshelf]
url = "https://botshelfvampire.com/api/mcp"

To see whether it connects: grok mcp list, then grok mcp doctor botshelf.

Source: Grok Build: MCP servers, read 2026-11-18.

Codex

codex mcp add botshelf --url https://botshelfvampire.com/api/mcp

Or put this in ~/.codex/config.toml:

[mcp_servers.botshelf]
url = "https://botshelfvampire.com/api/mcp"

codex mcp list shows what is configured. This is the one client with a recorded run so far (see Status).

Source: Codex: Model Context Protocol, read 2026-11-18.

Cursor

Put this in .cursor/mcp.json in the project (or ~/.cursor/mcp.json for every project):

{
  "mcpServers": {
    "botshelf": {
      "url": "https://botshelfvampire.com/api/mcp"
    }
  }
}

Source: Cursor: Model Context Protocol, read 2026-11-18.

Gemini CLI

gemini mcp add --transport http botshelf https://botshelfvampire.com/api/mcp

By default this writes the project's .gemini/settings.json. Add -s user for ~/.gemini/settings.json.

Source: Gemini CLI: MCP servers, read 2026-11-18.

VS Code and other clients

VS Code: .vscode/mcp.json in the workspace.

{
  "servers": {
    "botshelf": {
      "type": "http",
      "url": "https://botshelfvampire.com/api/mcp"
    }
  }
}

Source: VS Code: MCP configuration reference, read 2026-11-18.

For another client that speaks Streamable HTTP: give it the address above and choose “no authentication”. We have not run any of them. A client that only speaks stdio needs a bridge of your own choosing; BSV does not ship one.

Try it without a client

curl -s https://botshelfvampire.com/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_items","arguments":{"query":"code review","limit":3}}}'

What it does not do

Limits

60 calls a minute per caller (per server instance, so treat it as approximate); 32 KB per request; up to 25 results per call; up to 60,000 characters of text per call, with next_offset to read on. Past the call limit you get HTTP 429 with Retry-After; a request that is too large gets 413; an argument out of range comes back as a tool error.

Status

Independent shelf. Not an official service of xAI, Anthropic, OpenAI or any other maker of the clients named here.

Browse the shelf yourself Grok Bot tools What is open

Coming back later? What changed on this site, by date: new shelves, rule changes, corrections. The same list is an Atom feed for a feed reader.