# How to integrate Quire MCP with Hermes

```json
{
  "title": "How to integrate Quire MCP with Hermes",
  "toolkit": "Quire",
  "toolkit_slug": "quire",
  "framework": "Hermes",
  "framework_slug": "hermes-agent",
  "url": "https://composio.dev/toolkits/quire/framework/hermes-agent",
  "markdown_url": "https://composio.dev/toolkits/quire/framework/hermes-agent.md",
  "updated_at": "2026-11-06T07:04:49.118Z"
}
```

## Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.
This guide explains the easiest and most robust way to connect your Quire account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

## Also integrate Quire with

- [ChatGPT](https://composio.dev/toolkits/quire/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/quire/framework/claude-cowork)
- [Atomic Agent](https://composio.dev/toolkits/quire/framework/atomic-agent)

## TL;DR

### What is Composio Connect?
Composio Connect is a consumer offering that lets anyone plug 1,700+ applications directly into their agent harness — including Hermes. It can:
- Search and load tools from relevant toolkits on-demand, reducing context usage.
- Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
- Manage app authentication end-to-end with zero manual overhead.

## Connect Quire to Hermes

### Integrating Quire with Hermes
### Using Composio Connect CLI
1. Install the Composio CLI
Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

```bash
curl -fsSL https://composio.dev/install | bash
```

## What is the Quire MCP server, and what's possible with it?

The Quire MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Quire account. It provides structured and secure access to your projects, tasks, documents, discussions, and team workflows, so your agent can create and organize tasks, manage project content, collaborate through comments and chats, and export project data on your behalf.
- Task planning and organization: Have your agent create, update, move, transfer, reorder, and delete Quire tasks, including large batches of tasks at once.
- Project collaboration: Let the agent create project chat channels, add comments to chats and tasks, and remove comments when they are no longer needed.
- Project content management: Direct your agent to create, view, and delete documents, dashboards, insights, and sublists within your Quire workspace.
- Workflow customization: Instruct your agent to create and remove task statuses and tags, add project fields, manage task time logs, and apply task approval transitions.
- Project reporting and exports: Have your agent retrieve organization details and export complete Quire projects with their tasks and related data as CSV or JSON.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `QUIRE_ADD_INSIGHT_FIELD` | Add Insight Field | Add a formula or lookup custom field to an insight by OID or by owner ID plus insight ID. The tool declares the Admin app permission as a requirement. |
| `QUIRE_ADD_PROJECT_APPROVAL_CATEGORY` | Add Project Approval Category | Add an approval category to a Quire project by project ID or OID. The tool declares the Admin app permission as a requirement. |
| `QUIRE_ADD_PROJECT_FIELD` | Add Project Field | Add a custom-field definition to a Quire project by project ID or OID. The ID route has no named app permission in Quire's specification and uses normal resource authorization. The OID route explicitly requires the Quire app's Admin permission. |
| `QUIRE_ADD_TASK_TIMELOG` | Add Task Timelog | Add a time log to a Quire task identified by task OID or by project ID plus task ID. Returns the task's complete, fixed-shape timelogs array. |
| `QUIRE_ATTACH_FILE_TO_COMMENT` | Attach File to Comment | Upload a file as a raw-byte attachment to an existing Quire comment. |
| `QUIRE_ATTACH_FILE_TO_TASK` | Attach File to Task | Upload raw file bytes as an attachment to a task identified by ID or OID. |
| `QUIRE_BULK_CREATE_TASKS` | Bulk Create Tasks | Atomically create one to 300 Quire root, child, or sibling tasks in submitted order. The body is a top-level array. Any item error rolls back the whole batch and retains its `items[i]:` index. Dry-run performs the same validation without persistence; its returned identifiers are disposable. Normal calls cost one rate-limit unit per item and dry runs cost ceil(items / 2), minimum one. |
| `QUIRE_BULK_DELETE_TASKS` | Bulk Delete Tasks | Atomically delete 1 to 300 Quire tasks from a project selected by ID or OID. The request and response are top-level arrays in submitted order. Malformed references and permission failures roll back the whole batch, while unresolved or already-deleted references produce null slots, making retries idempotent. Dry-run performs the same checks without persistence. Real calls cost one rate-limit unit per submitted item even when skipped; dry-runs cost max(1, ceil(items / 2)). The response is always identifier-only. |
| `QUIRE_BULK_MOVE_TASKS` | Bulk Move Tasks | Atomically move or reorder 1 to 300 Quire tasks within one project, selected by project ID or OID. Quire moves resolvable items in submitted order as a sliding chain, returns null for unresolved item references, and rolls back the entire batch on validation, permission, cycle, or database errors. Use dry_run to validate without persistence. A real request costs one rate-limit unit per item; dry-run costs max(1, ceil(items / 2)). Cross-project moves require the bulk-transfer tool. |
| `QUIRE_BULK_SET_TASK_APPROVALS` | Bulk Set Task Approvals | Atomically apply one approval transition to up to 300 Quire tasks in a project selected by ID or OID. Missing tasks preserve null result slots; any validation or permission failure rolls back the whole batch. Supports non-persisting dry runs and full or compact responses. |
| `QUIRE_BULK_TRANSFER_TASKS` | Bulk Transfer Tasks | Atomically transfer 1 to 300 Quire tasks from one project to a different target project using ID or OID routing. The body is a top-level mixed-reference array. Transfers preserve OIDs, assign target-project IDs, and preserve submitted order; by default Quire may invite assignees and add or remap missing tags, statuses, and non-empty custom fields in the target project; set those controls to false to prevent those additional effects. unresolved source items produce null slots. Validation, permission, or database errors retain `items[i]:` and roll back both projects. Dry-run performs the same checks without persistence. Calls cost N units for N submitted items; dry-run costs ceil(N / 2), minimum one, charged before processing even for skipped items. |
| `QUIRE_BULK_UPDATE_TASKS` | Bulk Update Tasks | Atomically update one to 300 Quire tasks in a project selected by ID or OID. Each item selects exactly one task by ID or OID and may apply the full task update surface, including flattened project custom fields and explicit nulls that clear supported values. Missing tasks preserve null response slots; any validation, permission, conflict, or database error rolls back the whole batch and identifies the failing `items[i]`. Supports non-persisting dry runs and full or compact responses. Real calls cost one rate-limit unit per item; dry runs cost max(1, ceil(items / 2)). |
| `QUIRE_CREATE_CHAT` | Create Chat Channel | Create a chat under a project using its human-readable ID or OID. |
| `QUIRE_CREATE_CHAT_COMMENT` | Create Chat Comment | Add a Markdown comment to a chat identified by its OID or by project ID plus chat ID. |
| `QUIRE_CREATE_DASHBOARD` | Create Dashboard | Create a dashboard container under a project, organization, folder, or smart folder using the owner's human-readable ID or OID. Dashboard widgets cannot be configured through this operation. |
| `QUIRE_CREATE_DOC` | Create Document | Create a document under a project, organization, folder, or smart folder using the owner's human-readable ID or OID. |
| `QUIRE_CREATE_INSIGHT` | Create Insight | Create an insight view under a project, organization, folder, or smart folder using the owner's human-readable ID or OID. |
| `QUIRE_CREATE_STATUS` | Create Status | Create a task status in a project identified by ID or OID. |
| `QUIRE_CREATE_SUBLIST` | Create Sublist | Create a sublist under a project, organization, folder, or smart folder using the owner's human-readable ID or OID. |
| `QUIRE_CREATE_TAG` | Create Tag | Create a tag in a project identified by ID or OID. |
| `QUIRE_CREATE_TASK` | Create Task | Create a Quire root task or a child/sibling task using a project ID, a project ID plus task ID, or a project/task OID. Supports nested subtasks and project-defined custom fields. |
| `QUIRE_CREATE_TASK_COMMENT` | Create Task Comment | Add a Markdown comment to a task identified by task OID or by project ID plus task ID. |
| `QUIRE_DELETE_CHAT` | Delete Chat Channel | Remove one Quire chat channel by its OID or by its owner ID and chat ID. Deletion is idempotent: Quire returns success even if the chat no longer exists. A deleted chat may be restorable with RESTORE_CHAT. |
| `QUIRE_DELETE_COMMENT` | Delete Comment | Remove one Quire comment by its OID. Deletion is idempotent: Quire returns success even if the comment no longer exists. A deleted comment may be restorable with RESTORE_COMMENT when that action is available. |
| `QUIRE_DELETE_DASHBOARD` | Delete Dashboard | Remove one Quire dashboard by its OID or by its owner ID and dashboard ID. Deletion is idempotent: Quire returns success even if the dashboard no longer exists. A deleted dashboard may be restorable with RESTORE_DASHBOARD. |
| `QUIRE_DELETE_DOC` | Delete Document | Remove one Quire document by its OID or by its owner ID and document ID. Deletion is idempotent: Quire returns success even if the document no longer exists. A deleted document may be restorable with RESTORE_DOC. |
| `QUIRE_DELETE_INSIGHT` | Delete Insight | Remove one Quire insight by its OID or by its owner ID and insight ID. Deletion is idempotent: Quire returns success even if the insight no longer exists. |
| `QUIRE_DELETE_STATUS` | Delete Status | Delete one project task status by numeric value using the project ID or OID. The operation is idempotent: Quire returns 204 No Content even when the status does not exist. |
| `QUIRE_DELETE_STORAGE_VALUE` | Delete Storage Value | Delete one access-token-scoped app storage value by key name. The operation is idempotent: Quire returns 204 No Content whether or not the key exists. |
| `QUIRE_DELETE_SUBLIST` | Delete Sublist | Remove one Quire sublist by its OID or by its owner ID and sublist ID. Deletion is idempotent: Quire returns success even if the sublist no longer exists. |
| `QUIRE_DELETE_TAG` | Delete Tag | Delete one Quire tag by its OID. The operation is idempotent: Quire returns 204 No Content even when the tag does not exist. |
| `QUIRE_DELETE_TASK` | Delete Task | Remove one Quire task by task OID or by project ID plus numeric task ID. WARNING: Quire also removes every subtask beneath the selected task. The task may be recoverable with RESTORE_TASK while Quire retains the removed record. Deletion is idempotent: both routes return 204 No Content even when the task does not exist. |
| `QUIRE_EXPORT_PROJECT_CSV` | Export Project CSV | Export a Quire project and its filtered tasks and related data as a CSV file, selecting the project by ID or OID. Requires the Professional plan or above. The request costs 5 + max(1, ceil(filtered tasks / 100)) rate-limit units. |
| `QUIRE_EXPORT_PROJECT_JSON` | Export Project JSON | Export a Quire project, all tasks, and related data as JSON by project ID or OID; redundant HTML fields are removed when corresponding source and text fields are present. Requires the Professional plan or above and costs 5 + max(1, ceil(tasks / 100)) rate-limit units. |
| `QUIRE_GET_CHAT` | Get Chat Channel | Get one chat by its OID or by owner ID plus resource ID. |
| `QUIRE_GET_COMMENT` | Get Comment | Get one comment by its OID. |
| `QUIRE_GET_DASHBOARD` | Get Dashboard | Get one dashboard by its OID or by owner ID plus resource ID. |
| `QUIRE_GET_DOC` | Get Document | Get one document by its OID or by owner ID plus resource ID. |
| `QUIRE_GET_INSIGHT` | Get Insight | Get one insight by OID or by owner ID plus insight ID. |
| `QUIRE_GET_ORGANIZATION` | Get Organization | Get organization details by ID or OID, including subscription plan when available. |
| `QUIRE_GET_PARTNER` | Get Partner | Get one external team partner by OID. |
| `QUIRE_GET_PROJECT` | Get Project | Get one complete project record by ID or OID, including plan details. |
| `QUIRE_GET_RATE_LIMIT` | Get Rate Limit | Return current minute and hourly API usage for an organization or personal project by ID or OID. This inspection request consumes no rate-limit units. |
| `QUIRE_GET_STATUS` | Get Status | Get one project task status by numeric value. |
| `QUIRE_GET_STORAGE_VALUE` | Get Storage Value | Get one application storage value by key name. Values are scoped to the connected Quire access token and returned without changing their JSON type. |
| `QUIRE_GET_SUBLIST` | Get Sublist | Get one sublist by its OID or by owner ID plus resource ID. |
| `QUIRE_GET_TAG` | Get Tag | Return one tag identified by its OID. |
| `QUIRE_GET_TASK` | Get Task | Get one complete Quire task by task OID or by project ID plus numeric task ID. Returns identifiers, Markdown and plain-text content, relationships, assignment, scheduling, status, approval, time-log, attachment, and audit data. |
| `QUIRE_GET_USER` | Get User | Get a user by human-readable ID, email address, `me`, or OID. |
| `QUIRE_LIST_CHAT_COMMENTS` | List Chat Comments | List all comments on a chat identified by chat OID or by project ID plus chat ID. |
| `QUIRE_LIST_CHATS` | List Chat Channels | List chats under a supported owner identified by ID or OID. |
| `QUIRE_LIST_DASHBOARDS` | List Dashboards | List dashboards under a supported owner identified by ID or OID. |
| `QUIRE_LIST_DOCS` | List Documents | List documents under a supported owner identified by ID or OID. Quire returns each document's full Markdown body plus rendered text and HTML, so results may be large. |
| `QUIRE_LIST_INSIGHTS` | List Insights | List insights under an owner identified by ID or OID. |
| `QUIRE_LIST_ORGANIZATIONS` | List Organizations | List organizations visible to the connected user. |
| `QUIRE_LIST_PROJECT_PARTNERS` | List Project Partners | List external team partners for a project identified by ID or OID. |
| `QUIRE_LIST_PROJECTS` | List Projects | List projects authorized for the current application, globally or within one organization selected by ID or OID, with optional archived and add-task filters. |
| `QUIRE_LIST_STATUSES` | List Statuses | List task statuses for a project identified by ID or OID. |
| `QUIRE_LIST_STORAGE_VALUES` | List Storage Values | List up to 20 app storage values ordered by key, either across all keys or restricted to a prefix. Returns an object whose dynamic keys are storage names and whose values may be any JSON value; empty storage returns `{}`. |
| `QUIRE_LIST_SUBLISTS` | List Sublists | List sublists under a supported owner identified by ID or OID. |
| `QUIRE_LIST_TAGS` | List Tags | List tags in a project identified by ID or OID. |
| `QUIRE_LIST_TASK_COMMENTS` | List Task Comments | List all comments on a task identified by task OID or by project ID plus task ID. |
| `QUIRE_LIST_TASKS` | List Tasks | List Quire project roots or a task's direct children or paid deep subtree by project/task ID or OID. Supports status filtering, full or compact records, and one-page opaque cursor continuation. Deep traversal requires Professional or above and is capped at 500 nodes on Professional, 2,000 on Premium, and the response-size limit on Enterprise; cropped markers identify partial levels. |
| `QUIRE_LIST_USERS` | List Users | List users visible to the app globally or within a project selected by ID or OID. The optional contacts permission controls which colleagues and member details are visible; the current user is always first. |
| `QUIRE_MOVE_INSIGHT_FIELD` | Move Insight Field | Reorder a custom field on an insight identified by OID or by owner ID plus insight ID. Omit `before` to move it to the end. The OID route requires the Quire app's Admin permission. |
| `QUIRE_MOVE_PROJECT_FIELD` | Move Project Field | Reorder a custom field on a Quire project identified by ID or OID. Omit before to move the field to the end. The OID route requires the Quire app's Admin permission. |
| `QUIRE_MOVE_TASK` | Move Task | Reparent or reorder one Quire task within its current project, selected by project ID plus numeric task ID or by task OID. Move it under a destination task, immediately before or after that task, or to the project root. |
| `QUIRE_REMOVE_INSIGHT_FIELD` | Remove Insight Field | Remove a named custom field from a Quire insight by OID or by owner ID plus insight ID. The OID route requires the Quire app's Admin permission. Removal is idempotent: Quire returns success when the field is already absent. |
| `QUIRE_REMOVE_PROJECT_APPROVAL_CATEGORY` | Remove Project Approval Category | Remove an approval category from a Quire project by project ID or OID. Any task approval that references the category is cleared. The ID route uses normal resource authorization; the OID route requires the Quire app's Admin permission. Removal is idempotent: Quire returns success when the category is already absent. |
| `QUIRE_REMOVE_PROJECT_FIELD` | Remove Project Field | Remove a named custom field from a Quire project by project ID or OID. The ID route uses normal resource authorization; the OID route requires the Quire app's Admin permission. Removal is idempotent: Quire returns success when the field is already absent. |
| `QUIRE_REMOVE_TASK_TIMELOG` | Remove Task Timelog | Remove the task time log matching an exact start, end, and optional user, identifying the task by OID or by project ID plus integer task ID. Quire truncates sub-second timestamp precision before matching and returns all remaining time logs. |
| `QUIRE_RENAME_INSIGHT_FIELD` | Rename Insight Field | Rename a custom field on an insight identified by OID or by owner ID plus insight ID while preserving the field's content. The OID route requires the Quire app's Admin permission. |
| `QUIRE_RENAME_PROJECT_FIELD` | Rename Project Field | Rename a custom field on a project identified by ID or OID while preserving the field content and migrating task values. The OID route requires the Quire app's Admin permission. |
| `QUIRE_RESTORE_CHAT` | Restore Chat Channel | Restore a previously removed chat by its OID or by owner ID plus resource ID. |
| `QUIRE_RESTORE_COMMENT` | Restore Comment | Restore a previously removed comment by OID. |
| `QUIRE_RESTORE_DASHBOARD` | Restore Dashboard | Restore a previously removed dashboard by its OID or by owner ID plus resource ID. |
| `QUIRE_RESTORE_DOC` | Restore Document | Restore a previously removed document by its OID or by owner ID plus resource ID. |
| `QUIRE_RESTORE_INSIGHT` | Restore Insight | Restore a previously removed insight by its OID or by owner ID plus insight ID. If the insight is not removed, Quire returns it unchanged. |
| `QUIRE_RESTORE_SUBLIST` | Restore Sublist | Restore a previously removed sublist by its OID or by owner ID plus resource ID. |
| `QUIRE_RESTORE_TASK` | Restore Task | Restore a previously removed Quire task by project ID plus numeric task ID, or by task OID. Restoring an active task is an idempotent no-op. |
| `QUIRE_REVOKE_TASK_APPROVAL` | Revoke Task Approval | Cancel a Quire task's current approval by task OID or by project ID plus integer task ID. For awaiting or changes states, Quire clears the approval. For approved or rejected states, Quire rolls it back to awaiting and preserves the original requester. Call the action again to clear that approval. The operation is idempotent when no approval is set. |
| `QUIRE_RUN_INSIGHT` | Run Insight | Run a project-scoped insight by OID or by project ID plus insight ID and return its computed grouped table. Available on every Quire plan. A run costs 1 + max(0, ceil(tasks loaded / 250) - 1) rate-limit units after the status filter. Rows sort by group name, with the null group last. Project-wide task-collection tokens in formula columns evaluate to null; other cells in the row remain available. |
| `QUIRE_SEARCH_TASKS` | Search Tasks | Search tasks in one project, folder, or organization selected by ID or OID. Supports each route's documented full-text, regex, people, tag, activity, date, project-only, and project-ID-only filters, including dynamic project custom fields. Returns one page and exposes Quire's documented cursor. Folder and organization searches require Professional or above. Rate-limit cost is max(1, ceil(items returned / 100)). |
| `QUIRE_SEND_NOTIFICATION` | Send Notification | Irreversibly send a Quire notification to the authorizing user, selected visible users, or every user visible to the app. Sending cannot be undone. Using recipients=['*'] is a broadcast to all visible users, whose breadth depends on whether the app has access-to-contacts permission. |
| `QUIRE_SET_STORAGE_VALUE` | Set Storage Value | Create or replace one access-token-scoped app storage value by key. The value may be an object, array, string, number, or boolean. Use DELETE_STORAGE_VALUE to delete a key. New keys are subject to the Quire plan's storage record cap, and each write is limited to 4 KiB. |
| `QUIRE_SET_TASK_APPROVAL` | Set Task Approval | Request, approve, reject, or request changes for a task approval category, selecting the task by OID or by project ID plus task ID. The caller must be an allowed claimer to request approval or an allowed approver to decide it. Optionally creates a prefixed companion comment; use the revoke-approval action instead to cancel an approval. |
| `QUIRE_TRANSFER_TASK` | Transfer Task | Transfer one existing Quire task from its current project to a different project using an ID or OID route. The transfer removes it from the source project, preserves its OID, assigns a new numeric ID from the target project, and can place it at the target root or relative to a target task. By default, Quire may invite assignees and add missing tags, statuses, and non-empty custom fields to the target project; set the corresponding controls to `false` to prevent those side effects. |
| `QUIRE_UPDATE_CHAT` | Update Chat Channel | Update one chat by its OID or by owner ID plus resource ID. |
| `QUIRE_UPDATE_COMMENT` | Update Comment | Update the Markdown content or pin state of a comment by OID. |
| `QUIRE_UPDATE_DASHBOARD` | Update Dashboard | Update one dashboard by its OID or by owner ID plus resource ID. |
| `QUIRE_UPDATE_DOC` | Update Document | Update one document by its OID or by owner ID plus resource ID. |
| `QUIRE_UPDATE_INSIGHT` | Update Insight | Update one insight by OID or by owner ID plus insight ID. |
| `QUIRE_UPDATE_INSIGHT_FIELD` | Update Insight Field | Update an existing custom-field definition on a Quire insight by OID or by owner ID plus insight ID. Omitted properties preserve current values; the field type is immutable. The OID route requires the Quire app's Admin permission. Use the dedicated rename or move actions to rename or reorder a field. |
| `QUIRE_UPDATE_ORGANIZATION` | Update Organization | Update organization properties by ID or OID. |
| `QUIRE_UPDATE_PROJECT` | Update Project | Update project properties by ID or OID, including visibility, followers, dates, and archive state. |
| `QUIRE_UPDATE_PROJECT_APPROVAL_CATEGORY` | Update Project Approval Category | Update an approval category on a Quire project identified by ID or OID. Omitted changes preserve their current values. The ID route uses normal resource authorization; the OID route requires the Quire app's Admin permission. |
| `QUIRE_UPDATE_PROJECT_FIELD` | Update Project Field | Update an existing custom-field definition on a Quire project by ID or OID. Omitted properties preserve current values and the field type is immutable. The OID route requires the Quire app's Admin permission; the ID route uses normal resource authorization and has no named app permission. Use the dedicated rename or move actions to rename or reorder a field. |
| `QUIRE_UPDATE_STATUS` | Update Status | Update one project task status by numeric value. |
| `QUIRE_UPDATE_SUBLIST` | Update Sublist | Update one sublist by its OID or by owner ID plus resource ID. |
| `QUIRE_UPDATE_TAG` | Update Tag | Update one tag by OID. |
| `QUIRE_UPDATE_TASK` | Update Task | Partially update one Quire task selected by project ID plus numeric task ID, or by task OID. Supports replacement and incremental relationship fields, recurrence, archive/snooze state, source references, and project-defined custom fields flattened into the task body. |
| `QUIRE_UPDATE_TASK_TIMELOG` | Update Task Timelog | Replace fields on the task time log identified by its exact existing start, end, and optional user, selecting the task by project/task ID or task OID. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Quire MCP server provides comprehensive access to Quire operations through Composio. Once connected, Hermes can perform all major Quire actions on your behalf using natural language commands.

## Complete Code

None listed.

## Conclusion

### Way Forward
With Quire connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.
From here, you can extend Hermes further:
- Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
- Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
- Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.
If you run into trouble or want to share what you've built, join the [community](https://discord.com/invite/composio) or check out the [Docs](https://docs.composio.dev?cta_placement=toolkit-framework-hermes-docs) for deeper configuration options.

## How to build Quire MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/quire/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/quire/framework/claude-cowork)
- [Atomic Agent](https://composio.dev/toolkits/quire/framework/atomic-agent)

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [Aha!](https://composio.dev/toolkits/aha) - Aha! is a product management platform for setting strategy, prioritizing ideas, and planning roadmaps. It helps product teams align goals with development work and make better decisions.
- [AirOps MCP](https://composio.dev/toolkits/airops_mcp) - AirOps MCP is AirOps' managed content platform exposing brand context, knowledge bases, and workflows. Use it to give agents brand-aware content, automate content workflows, and track Brand Kit edits.
- [Amazing Marvin](https://composio.dev/toolkits/amazing_marvin) - Amazing Marvin is a personal productivity app for tasks, projects, habits, planning, time tracking, and rewards. It helps you build a flexible workflow that matches how you actually work.
- [Ambiguous MCP](https://composio.dev/toolkits/ambiguous_mcp) - Ambiguous MCP is a provider-hosted workspace service for documents, spreadsheets, tasks, CRM, calendar, mail, chat, and administration. It provides one workspace-scoped connection for managing these resources through natural language.
- [AnyDB](https://composio.dev/toolkits/any_db) - AnyDB is a flexible collaborative database platform for organizing records, files, and automated workflows. It helps teams centralize data, collaborate on records, and automate routine tasks.
- [ApptiveGrid](https://composio.dev/toolkits/apptivegrid) - ApptiveGrid is a collaborative no-code database and app platform for spaces, grids, forms, and structured records. It helps teams organize operational data, collect inputs, and build lightweight business apps without custom backend work.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Atlassian MCP](https://composio.dev/toolkits/atlassian_mcp) - Atlassian Rovo MCP connects agents to Jira, Jira Service Management, Confluence, Bitbucket, Compass, and Teamwork Graph workflows. It lets teams surface and act on Atlassian data while respecting existing user permissions.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Quire MCP?

With a standalone Quire MCP server, the agents and LLMs can only access a fixed set of Quire tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Quire and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Hermes?

Yes, you can. Hermes fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Quire tools.

### Can I manage the permissions and scopes for Quire while using Tool Router?

Yes, absolutely. You can configure which Quire scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Quire data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)