QuillBot Local MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUILLBOT_SETTINGS | No | Selects the local settings file. If omitted, the server uses the included safe example with browser disabled. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| quillbot_statusB | Estado local del adaptador. No abre navegador ni envía texto. |
| quillbot_inspectB | Inspecciona controles visibles para validar la integración; no ejecuta detección. visible=true permite que el usuario inicie sesión. |
| quillbot_detectA | Envía el texto autorizado a la web de QuillBot y devuelve su resultado literal y fragmentos señalados. Requiere integración validada. No certifica autoría. |
| quillbot_humanizeB | Solicita a QuillBot una propuesta de redacción para el fragmento autorizado. Devuelve una sugerencia para revisión; no modifica documentos. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: status checks local adapter state, inspect validates visible controls/login readiness, detect runs AI detection, and humanize requests a rewriting proposal. Although status and inspect both relate to integration health, the descriptions cleanly separate them.
All tools follow the same predictable quillbot_ prefix with lowercase snake_case verbs/nouns: status, inspect, detect, humanize. There are no deviations or mixed conventions.
Four tools is well-scoped for a focused local QuillBot adapter. Each tool has a clear role in the workflow: health, validation/login, detection, and humanization.
The core detection and humanization operations are covered, along with status and integration validation. Minor lifecycle gaps remain, such as explicit session cleanup/logout, batch operations, or configuration tools, but agents can work around these.