#6610: Quire Feedback
Status: To-do
πΈ Quire MCP is too expensive to keep connected in clients that load all tools up front, so we had to turn it off for most of our team.
π¨ Problem
- π¦ The Quire MCP server exposes 107 tools, and every tool definition is sent to the model at the start of each chat.
- π We measured about 100k input tokens for the Quire tool list alone in Codex/Cursor-style clients, before any task is read.
- π Several descriptions are very long;
search_tasksalone is over 5,000 characters with its schema. - β In September we disabled Quire MCP for the team in Codex and Cursor because of this. Now we use it only in Claude Code, which loads tools on demand.
π οΈ Suggestion
- π§° Selectable toolsets via the connection URL or app settings, e.g.
tasks(read, search, create, update, comment, move),read-only, andadmin(dashboards, insights, statuses, fields, approvals, chats, documents). - βοΈ Shorter descriptions: keep shared grammar (date filters, user boolean syntax) in one help tool or resource that the model opens only when needed.
- π A read-only option would also let teams hand the server to everyone safely.
βΉοΈ Notes
- Our daily agent work uses about 15 tools: get/search/list tasks, create/update task, comments, move and status.
- Related to MCP hits rate limits too easy/often: both block wider team use of the MCP.
Created by Grox Oct 31, 2026, Edited Nov 2, 2026
Hi,
Thank you for your feedback.
Weβve updated the Quire MCP so you can now choose a smaller set of tools through the connection URL:
The core set covers the daily tools you mentioned and comes to about 16k tokens. The read-only option only includes tools that donβt change anything, so it can be shared with the whole team, and it can be combined with core.
The default URL still loads every tool, so existing connections arenβt affected. Feel free to ask your AI to try these URLs and let us know how it works.
Golda, Nov 2, 2026