Storskarvia

Writing studio for novels and screenplays: read your projects and run cited fact-checks.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    Writing studio for novels and screenplays: read your projects and run cited fact-checks.

    How to connect

    How to connect Storskarvia to Claude

    The server address to paste into Claude settings:

    https://storskarvia.com/mcp/

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect Storskarvia to ChatGPT

    The server address to paste into ChatGPT settings:

    https://storskarvia.com/mcp/

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect Storskarvia to Cursor

    The server address to paste into Cursor settings:

    https://storskarvia.com/mcp/

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (10)

    Raw names from tools/list. Only developers need these.

    get_skarvia_infoWhat Storskarvia is and how it's positioned. A professional writing studio for novelists, screenwriters, and video scriptwriters, staffed by an AI team that fact-checks, researches, and tracks continuity -- but never writes the user's prose for them.
    list_featuresThe AI staff on Storskarvia and what each member actually does. Source: the "On staff" section of the current landing page.
    get_pricingCurrent Storskarvia pricing tiers, features, and monthly fact-check quotas. Built from config.PLANS, the same list /pricing renders from, so this can no longer drift from the page the way it did while it was kept by hand. The founder block is read live rather than described in prose. The note here used to say payments "aren't enabled yet" unconditionally, which went on being served after they were switched on, and the tiers listed full price while every human-facing surface offered a founding seat at half of it. An agent asked what Storskarvia costs answered with a price nobody was being charged and omitted the one on offer.
    list_guidesTitles, slugs, and URLs of Storskarvia's evergreen craft/how-to guides. Reads the live GUIDES list straight from app.main (imported lazily -- see the comment on the import below) so this can never drift out of sync with what's actually published at /guides.
    get_guideSummary and URL for one guide, looked up by slug. Call list_guides first to get valid slugs.
    list_my_projectsThe authenticated user's Storskarvia projects (novels, screenplays, video scripts). Requires a personal Storskarvia API key as a Bearer token.
    get_findingsFindings for one of the authenticated user's fact-check or continuity runs. Ownership is enforced -- a check_id belonging to another user raises an error rather than leaking their data.
    prepare_factcheckStep 1 of a bring-your-own-agent fact-check. Fetches one of the authenticated user's documents (ownership enforced) plus the exact disclosure and method your agent MUST follow. Requires a personal Storskarvia API key as a Bearer token. After this, call ground_claim(claim) once per checkable claim you extract from `text`, then submit_findings(...) to store results.
    ground_claimStep 2 of a bring-your-own-agent fact-check. Runs Storskarvia's own server-side retrieval (Wikipedia + searxng) for one claim and returns the sources -- no verdict, no judgment. Your agent should judge the claim ONLY against these returned sources, never outside knowledge. Requires a personal Storskarvia API key as a Bearer token (this is not an open retrieval API).
    submit_findingsStep 3 of a bring-your-own-agent fact-check. Stores your agent's findings as a real Storskarvia Check, visible on the same findings punch list as a staff-run check. Requires a personal Storskarvia API key as a Bearer token, and ownership of `document_id` is enforced. `disclosure` must be REQUIRED_DISCLOSURE copied verbatim -- proof the user was shown it before findings were presented -- or this raises a ToolError instead of storing anything. Each item in `findings` must have a non-empty quote/explanation, problem in {"contradicted","misleading"}, and a non-empty sources list; findings missing any of those are rejected wholesale (nothing partial is stored).