Storywright

io.storywrightPublished by storywright.ioOfficial publisherv0.2.0Updated Oct 24, 2026

Manage your tabletop RPG campaign from any MCP client: worlds, sessions, quests, lore, recaps.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server for managing tabletop RPG campaigns — worlds, sessions, quests, lore and recaps — from any MCP client.

What you can do
  • Manage campaign worlds and their lore.
  • Track sessions and quests.
  • Produce or keep session recaps.
  • No tool list is published, so the exact operations are not documented; the description only names worlds, sessions, quests, lore and recaps.
When to use it
Useful for game masters or players who run tabletop RPG campaigns and want an assistant to help organize campaign material — worlds, sessions, quests, lore and recaps — without leaving their MCP client.
Requirements
A remote MCP endpoint at mcp.storywright.io over streamable HTTP. OAuth authentication is required, so a Storywright account is needed. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, so your campaign data is stored with the third-party provider. No tool list is published, so it is unclear whether tools can create, change or delete campaign content; check before relying on it for important material.

Installation

In SourceWeft

  1. Open Storywright in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.storywright%2Fstorywright/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "storywright": {
      "type": "http",
      "url": "https://mcp.storywright.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.