Storytailor

YOUR ACCOUNT · YOUR ASSISTANT

Connect Storytailor.

Use your own Storytailor account from your assistant. Choose your app below, start the connection there, then sign in and review the permissions.

Preview: the Codex compatibility update is being tested. These instructions do not mean a connection is ready on the live service.

Account connection address

https://mcp.storytailor.dev/plugin/v1/mcp

No API key is needed. Your existing Storytailor permissions and allowances apply.

Codex

After the compatibility update is released, use these terminal commands:

codex mcp add storytailor --url https://mcp.storytailor.dev/plugin/v1/mcp

codex mcp login storytailor

Finish sign-in in the browser window that opens. Review the permissions and allow the connection, then return to Codex. Enabled does not mean signed in.

Codex connection help

ChatGPT

Storytailor’s directory submission is under review. If your account has custom-app access, add the account connection address in ChatGPT’s app settings and follow its sign-in flow. Availability depends on your account and workspace settings.

ChatGPT connection reference

Claude

Claude’s custom connectors and Claude Code have different setup flows. Storytailor sign-in for these clients still needs verification. Do not enter another app’s client ID or credentials.

For Claude’s consumer app, start in its custom connector settings. For Claude Code, use HTTP transport after support is verified:

claude mcp add --transport http storytailor https://mcp.storytailor.dev/plugin/v1/mcp

Claude Code setup

Gemini

Gemini custom apps and Gemini CLI are separate products. Storytailor sign-in for both still needs verification. In Gemini CLI, the connection uses Streamable HTTP, not legacy SSE. Consumer custom-app availability depends on Google’s account, region and activity requirements.

Gemini custom apps

Gemini CLI setup

Muse and other assistants

Use the connection settings supplied for your assistant. An assistant must support Storytailor’s sign-in flow before this address alone can connect it. Do not share a token or borrow another app’s credentials.

Signed in, but not connected?

Return to your assistant and start the connection again. Use the same browser window throughout. Signing into Storytailor separately does not finish the assistant connection. If it fails again, contact support with the app name, version and the page path shown in the address bar. Omit everything after ? or #; do not send passwords or sign-in codes.

You stay in control.

Review the requested permissions before allowing access. Storytailor asks for confirmation before supported changes. You can stop future access from your connections page; disconnecting does not erase content or copies already received by your assistant.

Manage connections