Skip to main content
Glama
EasyModeOnly

@ezquill/mcp-server

by EasyModeOnly

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoThe port for the HTTP transport.
MCP_PATHNoThe path for the MCP endpoint in HTTP transport./mcp
EZQUILL_TOKENNoAn explicit credential that outranks a cached sign-in. While set, the server will not offer to sign in.
EZQUILL_ISSUERNoThe OIDC issuer.https://auth.ezquill.com/realms/ezquill
EZQUILL_NO_BROWSERNoSet to any value to never launch a browser. The link is still returned.
EZQUILL_TOKEN_PATHNoThe path where the cached sign-in is stored.
EZQUILL_API_BASE_URLNoThe base URL for the ezQuill API.https://api.ezquill.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_projectsA

List the writer's projects. Start here: every other tool needs a projectId.

get_projectA

One project in detail: what it is, how far along it is, and its story-world premise.

search_projectA

Search a project semantically — by meaning, not keywords. Use this to find where something is discussed when you do not know what words the writer used. Results are ordered by similarity; there is no relevance score and no threshold.

get_outlineA

The structure of a project: its parts, chapters and scenes, with status and word counts. Returns no prose — use read_scene for that.

read_sceneA

Read one scene: its prose, its outline plan, and which characters and places appear in it. One node at a time — to find a scene, use search_project or get_outline.

list_entitiesA

The project's story world: characters, locations, factions, items, and research notes. Filter by kind, by tag, or by which scene they appear in.

get_entityB

One character, place or note in full: its profile, who and what it is connected to, and every scene it appears in.

get_timelineA

The project timeline. Story mode is chronology inside the fiction; project mode is the writer's own milestones.

list_feedbackA

Open comment threads and suggested edits on a project. Read this before revising a chapter — it is what the writer's collaborators have already said about it.

authenticateA

Sign in to ezQuill. Returns a link for the person to open. Call this only if a tool reports NOT_AUTHENTICATED and no link was already given.

sign_outA

Forget the stored ezQuill sign-in on this machine.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 11 tools

Disambiguation5/5

Each tool targets a clearly distinct resource or action: project listing/detail/search, outline vs. scene, entity list/detail, timeline, feedback, and auth. There is little risk of an agent selecting the wrong tool for a given intent.

Naming Consistency5/5

All tools use a consistent lowercase snake_case verb_noun pattern: list_projects, get_project, search_project, get_outline, read_scene, list_entities, get_entity, get_timeline, list_feedback. authenticate and sign_out are the only exceptions but they are auth actions and still read predictably.

Tool Count5/5

Eleven tools is well within the ideal range for this domain. Each tool covers a distinct need without unnecessary duplication, and the auth tools are justified for a service that requires sign-in.

Completeness4/5

The read-side surface is thorough: projects, outline, scenes, entities, timeline, and feedback are all covered. The only notable gap is the absence of any create/update/delete operations, but that appears intentional for a read-only writing-project assistant.

Maintenance

ActivityMaintained
ResponsivenessNo issues