Quilvo MCP Server

Overview

What the server does

Quilvo exposes a focused MCP server for personal AI assistants and local automation. It is intentionally smaller than the JSON API: assistants can discover project context, inspect session history, and log a writing session when the user asks them to.

Endpointhttps://quilvo.app/mcp/quilvo

TransportHTTP MCP

AuthenticationOAuth

Grantmcp:use

Authentication

Connect with OAuth

Hosted MCP clients connect to Quilvo through the standard OAuth flow. Add the endpoint, sign in to Quilvo, and approve the connection when the client opens the authorization screen.

API keys: User-managed public API keys still belong to the JSON API and scripted integrations. MCP connectors use OAuth instead of manual bearer-token setup.

Grant

Quilvo advertises a single MCP OAuth grant: mcp:use. Approving it lets the client use the MCP tools available to your Quilvo account. Tool code still scopes every request to your own data.

Tools

Available tools

An approved OAuth connection can see the full Quilvo MCP tool set for the authenticated user.

Tool	Writes	Purpose
list-projects	No	List the user projects with status, type, target, current count, and progress.
get-project	No	Read one project with recent writing sessions when requested.
list-writing-sessions	No	List recent writing sessions and return totals for the selected range.
log-writing-session	Yes	Create a writing session and update the project current count.
list-characters	No	List planning characters with role, hook, colour, and linked projects.
create-character	Yes	Create a character (name only is required) and optionally link a project.
update-character	Yes	Update fields on an existing character.
list-codex-entries	No	List worldbuilding codex entries (locations, factions, items, lore).
create-codex-entry	Yes	Create a codex entry of a given type and optionally link a project.
update-codex-entry	Yes	Update fields on an existing codex entry.
list-timeline	No	List story timeline events with free-text dates, type, project, and characters.
create-timeline-event	Yes	Create a timeline event (fictional or real dates) and optionally link characters.
update-timeline-event	Yes	Update an existing timeline event and its linked characters.

Connect

Client setup

MCP client configuration differs by host, but the required value is the same: the remote server URL. Authenticated clients discover Quilvo's OAuth metadata from that endpoint. Use HTTPS in production.

1. 01
   Add the endpoint
   Use the remote HTTP MCP URL in the hosted connector or MCP client.
2. 02
   Approve access
   Sign in to Quilvo and approve the OAuth connection for the single mcp:use grant.
3. 03
   Use the tools
   After approval, the assistant can list the available Quilvo MCP tools for your account.

Connection values

{
  "url": "https://quilvo.app/mcp/quilvo"
}

Some local MCP clients use Node's certificate store. If a local development URL fails over HTTPS, use the local HTTP URL while developing.

Examples

Tool arguments

list-projects

Find active drafting projects.

{
  "status": "drafting",
  "include_archived": false,
  "limit": 10
}

log-writing-session

Add 750 words to a project and keep the session history intact.

{
  "project_id": "9b7d4f6a-...",
  "word_count_action": "add",
  "word_count": 750,
  "date": "2026-05-24",
  "duration_minutes": 45,
  "notes": "Morning session."
}

Set the project total when an editor or writing app knows the latest count. Quilvo stores only the calculated session delta.

{
  "project_id": "9b7d4f6a-...",
  "word_count_action": "set_total",
  "word_count": 42100
}

MCP or API

Use the right surface

Use MCP when an AI assistant needs a small, discoverable tool surface. Use the JSON API when you are building an app, script, importer, or integration that controls its own interface and request flow.