Server facts
quire-mcp
Project
- Author
- jacob-hartmann
- Repository
- github.com/jacob-hartmann/quire-mcp
- License
- Not specified
- Category
- Productivity
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 4
- Last commit
- Data as of
Tags
- project management
- quire
Overview
Quire task hierarchies are central to quire-mcp: assistants can inspect project tasks, create subtasks, place new items before or after existing tasks, and change task properties. Searches can cover a project, folder, or organization, while tags and custom statuses provide controls for categorization and workflow stages. Project tools expose settings, membership information, and task exports in CSV or JSON. Deleting a task also deletes its subtasks, so the available operations include destructive changes as well as retrieval. MCP resources provide access to account information, organizations, projects, and project-specific task, tag, and status data.
Beyond task management, the integration supports creating and maintaining documents, sublists, and project chat channels. Assistants can work with task and chat comments, upload attachments to tasks or comments, inspect external teams, and read or write named storage values. A notification tool targets the authenticated user. OAuth setup uses a Quire app and browser authorization, with tokens cached and refreshed for later use. An existing access token can instead bypass that flow, but automatic refresh requires OAuth credentials.
quire-mcp setup notes
- quire-mcp records stdio only; confirm a network transport upstream before planning remote access.
- quire-mcp has no recorded license; confirm reuse terms in its repository.