Quire (Preview)

Manage Quire projects, tasks, comments, tags, sublists, and statuses from Microsoft Copilot Studio. The Quire MCP server bridges Copilot Studio agents to the Quire workspace via the Model Context Protocol — agents can read and search projects and tasks, create and update work items, post comments, and act on the user's behalf using their own Quire credentials.

This connector is available in the following products and regions:

Service Class Regions
Copilot Studio Premium All Power Automate regions except the following:
     -   US Government (GCC)
     -   US Government (GCC High)
     -   China Cloud operated by 21Vianet
     -   US Department of Defense (DoD)
Logic Apps Standard All Logic Apps regions except the following:
     -   Azure Government regions
     -   Azure China regions
     -   US Department of Defense (DoD)
Power Apps Premium All Power Apps regions except the following:
     -   US Government (GCC)
     -   US Government (GCC High)
     -   China Cloud operated by 21Vianet
     -   US Department of Defense (DoD)
Power Automate Premium All Power Automate regions except the following:
     -   US Government (GCC)
     -   US Government (GCC High)
     -   China Cloud operated by 21Vianet
     -   US Department of Defense (DoD)
Contact
Name Quire Support
Email support@quire.io
Connector Metadata
Publisher Potix Corporation
Website https://quire.io
Privacy policy https://quire.io/privacy
Categories Productivity;Collaboration

Quire is a visual collaboration platform built for breaking dreams down into doable tasks — agile sprints, nested sublists, Kanban boards, Gantt charts, calendars, and OKRs all in one workspace. This connector bridges Microsoft Copilot Studio agents to Quire over the Model Context Protocol (MCP), so agents can read and search projects and tasks, create and update work items, post comments, manage tags and sublists, and act on the user's behalf using their own Quire credentials.

Under the hood the connector exposes a single InvokeServer action that targets the streamable MCP endpoint at https://mcp.quire.app/mcp. Copilot Studio's MCP wrapper handles the initialize → notifications/initialized → tools/list → tools/call handshake on top of that one HTTP entry — the agent sees one connector but invokes any of the ~80 Quire tools the server advertises.

Prerequisites

  • A Quire account — free tier works.
  • Membership in at least one Quire organization or project that the agent should act on. The connector authenticates as the signed-in user, so the agent inherits exactly that user's permissions.
  • For organizations on a paid Quire plan, the workspace owner must allow third-party OAuth apps. (Personal and Free workspaces have this enabled by default.)

How to get credentials

End users sign in to their own Quire account during connection setup — there is no API key to copy or paste.

  1. In Copilot Studio (or Power Apps / Power Automate), add the Quire connector to your agent or flow.
  2. When prompted, click Sign in. A browser tab opens to https://mcp.quire.app/authorize.
  3. The Quire OAuth consent page lists the workspaces this connector will be able to access. Approve the request.
  4. The browser closes and Copilot Studio shows the connection as Connected.

Access tokens are valid for ~1 hour and are refreshed automatically by Power Platform using the connector's refresh URL.

Get started with your connector

Once connected, the connector exposes a single Power Platform action — Invoke Server — but every Quire MCP tool is reachable through it via the agent. The agent will pick the right tool for each user instruction.

Representative things the agent can do for you:

  • Find work: "What's overdue in the Marketing organization?", "Show me tasks assigned to me this week", "Search for tasks tagged 'urgent' in the Design project."
  • Create & update: "Create a task 'Draft Q3 launch deck' in Marketing/Campaigns due next Friday and assign it to me.", "Mark Roadmap #842 as Won't Fix.", "Move all open tasks in the Backlog sublist to In Progress."
  • Collaborate: "Comment on task #1204 that I've reviewed and approved the spec.", "Add Bob as a follower on every open task in the Design Review sublist."
  • Organize: "Create a new sublist 'Phase 2' under the Migration sublist.", "Rename the 'P1' tag to 'High Priority' across the org."

For a complete reference of operations exposed by the Quire MCP server, see the Quire MCP server documentation.

Known issues and limitations

  • One user per connection. Each connection authenticates a single Quire user; sharing a connection between users means actions appear as the connection owner. Provision one connection per user (the default in Copilot Studio).
  • Streamable HTTP only. This connector uses Power Platform's MCP wrapper with x-ms-agentic-protocol: mcp-streamable-1.0. SSE-only MCP clients are not relevant here — Power Platform owns the transport.
  • Paid-plan features may surface 403. Some Quire write operations (custom approval categories, project fields on free tier, etc.) require a paid Quire plan; the connector reports the server's error message verbatim. Upgrade the Quire workspace, not the connector configuration.

Common errors and remedies

  • invalid_request — Missing required parameters during sign-in: ensure your tenant's environment isn't blocking the mcp.quire.app host via a DLP policy that requires Microsoft-only OAuth IdPs.
  • HTTP 469 (ecQuotaExceeded) on a tool call: the Quire workspace has hit its API quota. Wait for the quota window to reset (typically one hour) or upgrade the Quire plan.
  • Unknown client_id when reconnecting: the Quire MCP OAuth client registration has been revoked or rotated. Disconnect the connection in Copilot Studio and reconnect — Power Platform re-registers automatically.
  • PKCE verification failed for the user-facing browser flow: do not modify the Authorization URL inside the connector configuration. Copilot Studio constructs the OAuth request; manual edits drop required parameters.

For anything not covered above, email support@quire.io.

FAQ

Does this connector use the Quire REST API directly? No — it uses the Quire MCP server (https://mcp.quire.app), which sits on top of the Quire API and exposes a tool-oriented surface designed for LLM agents. This is the same server that powers the Claude, Cursor, and ChatGPT MCP integrations.

Where are tokens stored? Refresh tokens are stored encrypted by Power Platform's connector framework; the Quire MCP server stores its own refresh token for the user's Quire account in its database, scoped to that user only. Neither side persists the Power Platform access token.

Can the agent reach my private Inbox ("My Tasks")? Yes — Quire's Inbox is part of the My Tasks scope. Ask the agent for "tasks in my Inbox" or "what's in my My Tasks list" and it will route through the appropriate MCP tool.

Is there a sandbox / dev workspace I can test against? Sign up for a free Quire account at https://quire.io. Free workspaces support the entire connector tool surface — paid features are only required for organization-wide approval workflows and a handful of insight fields.

Throttling Limits

Name Calls Renewal Period
API calls per connection 100 60 seconds

Actions

Quire

Manage Quire projects, tasks, and comments

Quire

Operation ID:
InvokeServer

Manage Quire projects, tasks, and comments