Connect any MCP client (advanced)

Under the hood, Tavernbard is a remote MCP server over Streamable HTTP. The plugin is the polished path (see the setup guide), but any MCP client that supports remote servers with custom headers can be the game master's hands.

The three settings

A generic config shape (adapt the key names to your client; the server name is always tavernbard):

{
  "mcp": {
    "servers": {
      "tavernbard": {
        "enabled": true,
        "transport": "streamable-http",
        "url": "https://api.tavernbard.com/mcp",
        "headers": {
          "Authorization": "Bearer bard_live_REPLACE_ME"
        }
      }
    }
  }
}

Verify the connection

Ask your client to list the server's tools; you should see the full Tavernbard toolbox (dice, campaigns, characters, combat, inventory, checkpoints, and more). No client handy? Check the endpoint directly:

curl -s -X POST "https://api.tavernbard.com/mcp" \
  -H "Authorization: Bearer bard_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

A 401 means the key is wrong or missing its Bearer prefix.

Teach the agent to be a game master

The server carries its own instructions. Have your agent call the get_dm_instructionstool once at session start; it returns the full game-master guide, including the golden rule: never invent rolls, hit points, or resource changes; always use the tools. One line in your agent's system prompt is enough to make that happen.

Source of truth

The complete client documentation, per-client examples, and the full agent prompt live in the Tavernbard repository's docs/clients/ folder and stay authoritative as the API evolves.