Quire MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Quire MCP Serverlist my tasks in the Q3 Planning project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Quire MCP Server
A Model Context Protocol (MCP) server for the Quire project management platform.
This server allows AI assistants (like Claude) to interact with your Quire projects, tasks, and data securely.
Quick Start
Prerequisites
Node.js v22 or higher
A Quire account
A Quire OAuth app (see Create a Quire OAuth App)
Step 1: Create a Quire OAuth App
Go to Quire App Management
Click Create new app
Set Redirect URL to:
http://localhost:3000/callbackChoose the permission scopes you need
Copy the Development Client ID and Development Client Secret
Step 2: Configure Your MCP Client
Choose the setup that matches your MCP client:
Claude Desktop (Recommended)
Add to your claude_desktop_config.json:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"quire": {
"command": "npx",
"args": ["-y", "quire-mcp"],
"env": {
"QUIRE_OAUTH_CLIENT_ID": "your-client-id",
"QUIRE_OAUTH_CLIENT_SECRET": "your-client-secret"
}
}
}
}Claude Code (CLI)
Add to your Claude Code MCP settings (~/.claude/mcp.json or project-level):
{
"mcpServers": {
"quire": {
"command": "npx",
"args": ["-y", "quire-mcp"],
"env": {
"QUIRE_OAUTH_CLIENT_ID": "your-client-id",
"QUIRE_OAUTH_CLIENT_SECRET": "your-client-secret"
}
}
}
}Cursor
In Cursor settings, add an MCP server:
{
"mcpServers": {
"quire": {
"command": "npx",
"args": ["-y", "quire-mcp"],
"env": {
"QUIRE_OAUTH_CLIENT_ID": "your-client-id",
"QUIRE_OAUTH_CLIENT_SECRET": "your-client-secret"
}
}
}
}Step 3: First-Time Authorization
On first use, the server will:
Print an authorization URL to the console
Wait for you to open that URL in your browser
After you grant access, Quire redirects to localhost
The server captures the tokens and caches them
Subsequent uses will automatically refresh tokens as needed.
Related MCP server: MCP Feishu Project Manager
Transport Modes
The server supports two transport modes: stdio (default) and http.
STDIO Mode (Default)
STDIO mode is the simplest setup. The MCP client spawns the server process directly and communicates via JSON-RPC over stdin/stdout.
How it works:
MCP client spawns
npx quire-mcpwith environment variablesOn first tool call, if no cached token exists, the server prints an OAuth URL to stderr
User opens URL in browser and authorizes
Quire redirects to
localhost:3000/callbackwhere the server captures the tokenToken is cached to disk for future use
Token cache locations:
Windows:
%APPDATA%\quire-mcp\tokens.jsonmacOS:
~/Library/Application Support/quire-mcp/tokens.jsonLinux:
~/.config/quire-mcp/tokens.json
HTTP Mode
HTTP mode runs an HTTP server with OAuth 2.0 endpoints. Use this when you need:
A long-running server process
Multiple clients connecting to the same server
Deployment to a remote host (e.g., Cloudflare Workers, cloud VMs)
Important: In HTTP mode, the server must be running before clients can connect. Environment variables are set on the server process, not in client configs.
Running HTTP Mode Locally
Step 1: Start the server:
# Using npx
QUIRE_OAUTH_CLIENT_ID=your-client-id \
QUIRE_OAUTH_CLIENT_SECRET=your-client-secret \
MCP_TRANSPORT=http \
npx quire-mcp
# Or using pnpm (for development)
pnpm dev:httpThe server will output:
[quire-mcp] HTTP server listening on 127.0.0.1:3001
[quire-mcp] OAuth metadata: http://localhost:3001/.well-known/oauth-authorization-server
[quire-mcp] MCP endpoint: http://localhost:3001/mcpStep 2: Configure your MCP client to connect:
{
"mcpServers": {
"quire": {
"type": "http",
"url": "http://localhost:3001/mcp"
}
}
}Note: No env section is needed in the client config for HTTP mode—the OAuth credentials are on the server.
Step 3: When the MCP client connects, it will:
Discover OAuth endpoints via
/.well-known/oauth-authorization-serverRedirect you to authorize with Quire
Exchange tokens and establish a session
HTTP Mode Environment Variables
Variable | Required | Default | Description |
| Yes |
| Set to |
| Yes | - | Quire OAuth Client ID |
| Yes | - | Quire OAuth Client Secret |
| No |
| Host to bind the HTTP server |
| No |
| Port for the HTTP server |
| No |
| Base URL for OAuth endpoints |
| No |
| Quire OAuth callback URL |
Quire App Configuration for HTTP Mode:
When using HTTP mode, update your Quire app's redirect URL to: http://localhost:3001/oauth/callback
Manual Token Mode
If you have a pre-obtained access token (e.g., from Postman), you can skip OAuth entirely:
{
"mcpServers": {
"quire": {
"command": "npx",
"args": ["-y", "quire-mcp"],
"env": {
"QUIRE_ACCESS_TOKEN": "your-access-token"
}
}
}
}Note: Manually-obtained tokens will eventually expire and won't auto-refresh without OAuth credentials.
Configuration Reference
All Environment Variables
Variable | Required | Default | Description |
| Yes* | - | Quire OAuth Client ID |
| Yes* | - | Quire OAuth Client Secret |
| No | - | Manual token override (skips OAuth flow) |
| No |
| OAuth callback URL (stdio mode) |
| No | Platform default | Path to token cache file |
| No |
| Transport mode: |
| No |
| HTTP server bind address |
| No |
| HTTP server port |
| No |
| OAuth issuer URL (HTTP mode) |
*Required unless QUIRE_ACCESS_TOKEN is set.
Features
Tools
The server provides 60+ tools organized by category:
Authentication
Tool | Description |
| Get the current authenticated user's profile |
Organizations
Tool | Description |
| List all accessible organizations |
| Get organization details by ID or OID |
| Update organization followers |
Projects
Tool | Description |
| List all projects, optionally filtered by organization |
| Get project details including task counts |
| Update project name, description, icon, and followers |
| Export project tasks in JSON or CSV format |
Tasks
Tool | Description |
| List tasks in a project (root-level or subtasks) |
| Get task details by project+ID or OID |
| Create a new task with optional priority, dates, assignees, tags |
| Update task properties |
| Delete a task and its subtasks |
| Search tasks in a project by keyword and filters |
| Create a task after a specified task |
| Create a task before a specified task |
| Search tasks within a folder |
| Search tasks across an entire organization |
Tags
Tool | Description |
| List all tags in a project |
| Get tag details by OID |
| Create a new tag with name and color |
| Update tag name or color |
| Delete a tag |
Comments
Tool | Description |
| List all comments on a task |
| Add a comment to a task |
| Update comment text |
| Delete a comment |
| List all comments in a chat channel |
| Add a comment to a chat channel |
Users
Tool | Description |
| Get user details by ID, OID, or email |
| List all accessible users |
| List all members of a project |
Custom Statuses
Tool | Description |
| List custom statuses in a project |
| Get status details by value |
| Create a custom workflow status |
| Update status name or color |
| Delete a custom status |
External Teams (Partners)
Tool | Description |
| Get external team details |
| List all external teams in a project |
Documents
Tool | Description |
| Create a document in an organization or project |
| Get document content and metadata |
| List all documents |
| Update document name or content |
| Delete a document |
Sublists
Tool | Description |
| Create a sublist |
| Get sublist details |
| List all sublists |
| Update sublist name or description |
| Delete a sublist |
Chat Channels
Tool | Description |
| Create a chat channel |
| Get chat channel details |
| List all chat channels |
| Update chat name, description, or members |
| Delete a chat channel |
Key-Value Storage
Tool | Description |
| Get a stored value by key |
| List storage entries by prefix |
| Store a value |
| Delete a stored value |
Notifications
Tool | Description |
| Send notification to users |
Attachments
Tool | Description |
| Upload a file attachment to a task |
| Upload a file attachment to a comment |
Resources
The server exposes data as MCP resources:
Static Resources
Resource URI | Description |
| Current authenticated user's profile |
| List of all accessible organizations |
| List of all accessible projects |
Resource Templates
Resource URI | Description |
| Specific project details and metadata |
| Root tasks in a project |
| Tags defined in a project |
| Custom statuses in a project |
Prompts
The server provides guided prompts for common workflows:
Prompt | Description |
| Generate a task plan from a goal description |
| Generate a daily standup summary |
| Plan a sprint from the backlog |
| Break down a complex task into subtasks |
| Generate a weekly progress report |
Development
Setup
# Clone the repo
git clone https://github.com/jacob-hartmann/quire-mcp.git
cd quire-mcp
# Use the Node.js version from .nvmrc
# (macOS/Linux nvm): nvm install && nvm use
# (Windows nvm-windows): nvm install 22 && nvm use 22
nvm install
nvm use
# Install dependencies
pnpm install
# Copy .env.example and configure
cp .env.example .env
# Edit .env with your OAuth credentialsRunning Locally
# Development mode (stdio, auto-reload)
pnpm dev
# Development mode (http, auto-reload)
pnpm dev:http
# Production build
pnpm build
# Production run
pnpm start # stdio mode
pnpm start:http # http modeDebugging
You can use the MCP Inspector to debug the server:
# Run from source
pnpm inspect
# Run from built output
pnpm inspect:distpnpm inspect loads .env automatically via dotenv (see .env.example).
If you see Ignored build scripts: esbuild..., run pnpm approve-builds and allow esbuild.
In CI we install dependencies with lifecycle scripts disabled (pnpm install --ignore-scripts) and then explicitly rebuild only esbuild for the production build job.
Contributing
Contributions are welcome! Please see CONTRIBUTING.md for guidelines on how to contribute to this project.
Security
See SECURITY.md for security policy and reporting vulnerabilities.
Support
This is a community project provided "as is" with no guaranteed support. See SUPPORT.md for details.
License
MIT © Jacob Hartmann
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jacob-hartmann/quire-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server