StoryOS

● Active

dev.storyos/storyos

Your StoryOS workspace (records, approvals and agents) for Claude, ChatGPT and any MCP client.

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "storyos": {
      "command": "npx",
      "args": [
        "-y",
        "@storyos/mcp@0.1.2"
      ],
      "env": {
        "STORYOS_TOKEN": "<your STORYOS_TOKEN>"
      }
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --env STORYOS_TOKEN='<your STORYOS_TOKEN>' --transport stdio storyos -- npx -y @storyos/mcp@0.1.2
OpenAI Codex CLI
codex mcp add storyos --env STORYOS_TOKEN='<your STORYOS_TOKEN>' -- npx -y @storyos/mcp@0.1.2
VS Code
code --add-mcp '{"name":"storyos","type":"stdio","command":"npx","args":["-y","@storyos/mcp@0.1.2"],"env":{"STORYOS_TOKEN":"<your STORYOS_TOKEN>"}}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

Environment variables
  • STORYOS_TOKENrequiredsecretStoryOS personal API token (mn_pat_...), created under API tokens in StoryOS. Scoped to one workspace.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
AI & Agents
Version
0.1.2
Registry
active
Published
11/18/2026

Live check

checked Nov 19, 2026, 06:07 UTC
● Needs sign-in

The endpoint is up but wants a key or an OAuth sign-in before the handshake, so its tools can only be read with an account.

Checked by Serverdex with a plain initialize + tools/list call to mcp.storyos.dev/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 19, 2026
Stars
8
Forks
0
Last push
Nov 18, 2026
License
Other

TypeScriptai-agentsmcpnestjsnextjsno-codenotion-alternativepostgresqlself-hostedwork-os

From the README

The open-source work OS your AI can actually run. Relational databases for the whole company, with a public API and an MCP server, so your own AI works inside it, not beside it. StoryOS is a connected-database work OS. You define databases, link them with real two-sided relations, and work the same records through nine kinds of view. Clients, tasks, content pipelines, CRM and sprints all live in one engine, on your schema, on your server. It is built API-first and agent-first. The web app is just one client of a public REST API. Everything it can do, a script can do, and so can the AI you already use, through the built-in MCP server. When an agent does something risky, it waits for a human to approve it first. Hosted: app.storyos.dev · Docs: docs.storyos.dev · Self-host: one docker compose up (below) What's in it The engine • Databases and fields. Text, rich text, number, checkbox, date, select, multi-select, workflow (a database's one canonical status), URL, email, colour, person, attachment, relation, lookup, rollup, formula, button and AI fields (a value computed by a model from the record's own fields). Schema changes are API calls, not migrations. → Databases and fields • Relations, lookups and rollups. Relations are paired on both sides, one-to-many or many-to-many, across spaces. Lookups show a related record's field; rollups aggregate related records. → Relations • Formulas and validation rules.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://mcp.storyos.dev/mcp

Alternatives to StoryOS

Best AI & Agents servers →

The most-starred AI & Agents servers in the index, with their live-check result.

ServerStarsLast pushLive check
Ruflo81,994Nov 2026Local / not checked
Claude Flow81,985Nov 2026Local / not checked
CodeBurn11,805Nov 2026Local / not checked
Kaneo9,825Nov 2026Local / not checked
Ha MCP7,958Nov 2026Local / not checked

StoryOS: questions people ask

Is StoryOS a remote or a local MCP server?
According to its entry in the official MCP registry, StoryOS ships as a hosted endpoint (streamable-http) that your client connects to by URL and as a local package (npm) that your client starts on your machine. Use the hosted endpoint when your client supports Streamable HTTP; use the package when you want it to run locally.
Does StoryOS need an API key or a sign-in?
Yes. Its hosted endpoint answered the credential-free Serverdex live check with HTTP 401/403 on Nov 19, 2026: it expects an API key in a header or an OAuth login before it lists its tools.
Is StoryOS still maintained?
Active: the repository's last commit today. Last push Nov 18, 2026, 8 GitHub stars, Other licence. Read from GitHub on Nov 19, 2026.
How do I add StoryOS to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all AI & Agents →

Add the badge to your site

Show visitors that StoryOS is listed here — it’s also the link we check for a free listing.

StoryOS — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/dev-storyos-storyos?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="StoryOS — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![StoryOS — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/dev-storyos-storyos?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.