接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令? 兩種安裝方式的差異
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.
http://localhost:3000/callbackChoose the setup that matches your MCP client:
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"
}
}
}
}
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"
}
}
}
}
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"
}
}
}
}
On first use, the server will:
Subsequent uses will automatically refresh tokens as needed.
The server supports two transport modes: stdio (default) and http.
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:
npx quire-mcp with environment variableslocalhost:3000/callback where the server captures the tokenToken cache locations:
%APPDATA%\quire-mcp\tokens.json~/Library/Application Support/quire-mcp/tokens.json~/.config/quire-mcp/tokens.jsonHTTP mode runs an HTTP server with OAuth 2.0 endpoints. Use this when you need:
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.
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:http
The 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/mcp
Step 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:
/.well-known/oauth-authorization-serverQuire App Configuration for HTTP Mode:
When using HTTP mode, update your Quire app's redirect URL to: http://localhost:3001/oauth/callback
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.
*Required unless QUIRE_ACCESS_TOKEN is set.
The server provides 60+ tools organized by category:
The server exposes data as MCP resources:
The server provides guided prompts for common workflows:
# 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 credentials
# 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 mode
You can use the MCP Inspector to debug the server:
# Run from source
pnpm inspect
# Run from built output
pnpm inspect:dist
pnpm 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.
Contributions are welcome! Please see CONTRIBUTING.md for guidelines on how to contribute to this project.
See SECURITY.md for security policy and reporting vulnerabilities.
This is a community project provided "as is" with no guaranteed support. See SUPPORT.md for details.
MIT © Jacob Hartmann
Model Context Protocol (MCP) server for Quire project management
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Quire 透過 stdio 在本機執行。
上次檢查時間:2026-10-27。 Model Context Protocol (MCP) server for Quire project management