Quire

AModel Context Protocol (MCP)server for theQuireproject management platform.

- Node.js v22 or higher
- A Quire account
- A Quire OAuth app (seeCreate a Quire OAuth App)
- Go toQuire App Management
- ClickCreate new app
- SetRedirect URLto:http://localhost:3000/callback
- Choose the permission scopes you need
- Copy theDevelopment Client IDandDevelopment Client Secret

{ "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.jsonor 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" } } } }

{ "mcpServers": { "quire": { "command": "npx", "args": ["-y", "quire-mcp"], "env": { "QUIRE_OAUTH_CLIENT_ID": "your-client-id", "QUIRE_OAUTH_CLIENT_SECRET": "your-client-secret" } } } }

- 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.

The server supports two transport modes:stdio(default) andhttp.

STDIO mode is the simplest setup. The MCP client spawns the server process directly and communicates via JSON-RPC over stdin/stdout.
- MCP client spawnsnpx quire-mcpwith environment variables
- On 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 tolocalhost:3000/callbackwhere the server captures the token
- Token is cached to disk for future use

- Windows:%APPDATA%\quire-mcp\tokens.json
- macOS:~/Library/Application Support/quire-mcp/tokens.json
- Linux:~/.config/quire-mcp/tokens.json

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 runningbeforeclients can connect. Environment variables are set on theserver process, not in client configs.

# 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

[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:Noenvsection 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-server
- Redirect you to authorize with Quire
- Exchange tokens and establish a session

Quire 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 unlessQUIRE_ACCESS_TOKENis set.

The server provides60+ toolsorganized 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 theMCP Inspectorto debug the server:

# Run from source pnpm inspect # Run from built output pnpm inspect:dist

Contributions are welcome! Please seeCONTRIBUTING.mdfor guidelines on how to contribute to this project.

SeeSECURITY.mdfor security policy and reporting vulnerabilities.

This is a community project provided "as is" withno guaranteed support. SeeSUPPORT.mdfor details.

Comprehensive Trello integration: 46 tools covering boards, cards, lists, labels, checklists, attachments, members, custom fields, and search. Read-only mode, image attachment auto-download. Active fork of kocakli/Trello-Desktop-MCP integrating contributions from across the Trello MCP fork ecosystem