Quire
@jacob-hartmann
About Quire
This server allows AI assistants (like Claude) to interact with your Quire projects, tasks, and data securely.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"quire": {
"command": "npx",
"args": [
"-y",
"quire-mcp"
],
"env": {
"QUIRE_OAUTH_CLIENT_ID": "your-client-id",
"QUIRE_OAUTH_CLIENT_SECRET": "your-client-secret"
}
}
}
}Tools
61Get the current authenticated user's profile from Quire. Use this to verify your authentication is working and to see basic information about the connected Quire account.
List all organizations accessible to the current user. Returns an array of organization objects with basic information.
Get detailed information about a specific organization by its ID or OID. Use this to get full details including member count, project count, and followers.
Update an organization's followers. You can set the complete list of followers, or add/remove specific followers.
List all projects accessible to the current user. Optionally filter by organization, archived status, or write access.
Get detailed information about a specific project by its ID or OID. Returns full project details including task counts, organization, and owner.
Update a project's settings including name, description, and followers.
Export all tasks from a project in JSON or CSV format. Useful for backups, analysis, or integrations. Supports progress notifications for large exports when client provides a progressToken.
List tasks in a project. Returns root-level tasks by default, or subtasks if a parent task OID is provided.
Get detailed information about a specific task. Can be retrieved by project ID + task ID, or by task OID alone.
Create a new task in a project or as a subtask of an existing task. To create a root task, provide a project ID/OID. To create a subtask, provide a parent task OID. To position a task relative to another, use createTaskAfter or createTaskBefore instead.
Update an existing task. Can be identified by project ID + task ID, or by task OID alone. Only provided fields will be updated.
Delete a task and all its subtasks. This action cannot be undone.
Search for tasks in a project by keyword and optional filters. Returns tasks matching the search criteria.
Create a new task immediately after a specified task. The new task will be at the same level as the reference task.
Create a new task immediately before a specified task. The new task will be at the same level as the reference task.
Search for tasks within a specific folder by keyword and optional filters.
Search for tasks across an entire organization by keyword and optional filters. This searches all projects within the organization.
List all tags in a project. Returns an array of tag objects with name, color, and identifiers.
Get detailed information about a specific tag by its OID.
Create a new tag in a project. Tags help organize and categorize tasks.
Update a tag's name, global status, or color.
Delete a tag. This will remove the tag from all tasks that have it.
List all comments on a task. Can be accessed by task OID or by project ID + task number.
Add a comment to a task. Can be accessed by task OID or by project ID + task number.
Update an existing comment's text or pin status.
Delete a comment. This action cannot be undone.
List all comments on a chat channel by OID, or by project ID and chat ID.
Add a comment to a chat channel by OID, or by project ID and chat ID.
Get detailed information about a user by their ID, OID, or email. Returns user profile including name, email, and image.
List all users accessible to the current user. Returns an array of user objects with basic profile information.
List all members of a project. Returns an array of user objects who have access to the project.
List all custom statuses in a project. Returns an array of status objects with value, name, and color. Default statuses (0=To-Do, 100=Complete) are always available.
Get detailed information about a specific custom status by its value.
Create a custom status in a project. Custom statuses allow you to define workflow stages beyond the default To-Do (0) and Complete (100).
Update a custom status's name, value, or color.
Delete a custom status. Tasks with this status will be reverted to the default To-Do status. You cannot delete the default statuses (0 and 100).
Get details of an external team (partner) by OID.
List all external teams (partners) in a project.
Create a new document in an organization or project.
Get a document by OID, or by owner type/ID and document ID.
List all documents in an organization, project, folder, or smart-folder.
Update a document's properties by OID, or by owner type/ID and document ID.
Delete a document by OID, or by owner type/ID and document ID. This action cannot be undone.
Create a new sublist in an organization, project, folder, or smart-folder.
Get a sublist by OID, or by owner type/ID and sublist ID.
List all sublists in an organization, project, folder, or smart-folder.
Update a sublist's properties by OID, or by owner type/ID and sublist ID.
Delete a sublist by OID, or by owner type/ID and sublist ID. This action cannot be undone.
Create a new chat channel in a project.
Get a chat channel by OID, or by owner type/ID and chat ID.
List all chat channels in a project.
Update a chat channel's properties by OID, or by owner type/ID and chat ID.
Delete a chat channel by OID, or by owner type/ID and chat ID. This action cannot be undone.
Get a stored value by name from Quire's key-value storage.
List all storage entries with a given prefix. Useful for finding related stored values.
Store a value in Quire's key-value storage. Overwrites any existing value with the same name.
Delete a stored value by name. This action cannot be undone.
Send a notification to the current authorized user. Optionally include a URL that the user can click to navigate to.
Upload a file attachment to a task. The content should be provided as a string (e.g., text content or base64-encoded binary).
Upload a file attachment to a comment. The content should be provided as a string (e.g., text content or base64-encoded binary).
Overview
What is Quire?
An MCP server that enables AI assistants like Claude to interact with the Quire project management platform, allowing secure access to projects, tasks, and organizational data via the Quire API.
How to use Quire?
Set up a Quire OAuth app, then configure your MCP client with the environment variables QUIRE_OAUTH_CLIENT_ID and QUIRE_OAUTH_CLIENT_SECRET. Run the server via npx -y quire-mcp (stdio mode) or set MCP_TRANSPORT=http for HTTP mode. On first use, authorize via the printed OAuth URL; tokens are cached automatically.
Key features of Quire
- 60+ tools for tasks, projects, organizations, tags, and comments
- Supports stdio and HTTP transport modes
- OAuth 2.0 authentication with automatic token refresh
- Manual token mode for pre-obtained access tokens
- Cross-platform token caching (macOS, Windows, Linux)
- Compatible with Claude Desktop, Claude Code, and Cursor
Use cases of Quire
- Let an AI assistant create, update, and delete tasks in Quire projects
- Search and filter tasks across projects or organizations
- Manage project metadata, tags, and comments via natural language
- Export project data in JSON or CSV format
- Automate project management workflows through AI conversations
FAQ from Quire
What prerequisites are needed to use Quire MCP?
Node.js v22 or higher, a Quire account, and a Quire OAuth app with appropriate scopes.
How does authentication work?
The server uses OAuth 2.0. On first use, it prints an authorization URL; after you grant access, tokens are cached for future sessions and automatically refreshed.
Can I use a manual access token instead of OAuth?
Yes, set the QUIRE_ACCESS_TOKEN environment variable to skip OAuth, but manually obtained tokens expire and won't auto-refresh.
Which MCP clients are supported?
Claude Desktop (recommended), Claude Code (CLI), and Cursor – each with specific configuration examples provided.
What transport modes are available?
Two modes: stdio (default) and HTTP. STDIO spawns the server per client; HTTP runs a persistent server for multiple clients or remote deployment.
Frequently asked questions
What prerequisites are needed to use Quire MCP?
Node.js v22 or higher, a Quire account, and a Quire OAuth app with appropriate scopes.
How does authentication work?
The server uses OAuth 2.0. On first use, it prints an authorization URL; after you grant access, tokens are cached for future sessions and automatically refreshed.
Can I use a manual access token instead of OAuth?
Yes, set the `QUIRE_ACCESS_TOKEN` environment variable to skip OAuth, but manually obtained tokens expire and won't auto-refresh.
Which MCP clients are supported?
Claude Desktop (recommended), Claude Code (CLI), and Cursor – each with specific configuration examples provided.
What transport modes are available?
Two modes: stdio (default) and HTTP. STDIO spawns the server per client; HTTP runs a persistent server for multiple clients or remote deployment.
Basic information
More Other MCP servers
ICSS
chokcoco不止于 CSS

DeepMark
DeepMark helps teachers deliver rapid, consistent marking with meaningful feedback for every student — in a fraction of the time. What once took a week, now takes one free period.
Inbox Zero AI MCP
elie222The world's best AI personal assistant for email. Open source app to help you reach inbox zero fast.
Codelf
unbugA search tool helps dev to solve the naming things problem.
Nginx UI
0xJackyYet another WebUI for Nginx
Comments