SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate POMA Grill MCP with Hermes

Connect Hermes to POMA Grill MCP. Retrieve prompt-ready context for onboarding docs, search indexed specs for api breaking changes, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
POMA Grill logoPOMA Grill
Api Key

POMA Grill is a project-scoped context engine for ingesting and indexing documents. Use it to manage indexed content and retrieve prompt-ready context for LLMs.

17 Tools

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 POMA Grill 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 POMA Grill with

ChatGPTClaude CoworkAtomic Agent

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,500+ 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.

Integrating POMA Grill 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
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to POMA Grill

Ask your agent to connect to POMA Grill, or simply request any POMA Grill-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new POMA Grill connection.

Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to POMA Grill or request any POMA Grill-related task. It will prompt you to authenticate and authorize access.

5. Done!

What is the POMA Grill MCP server, and what's possible with it?

The POMA Grill MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your POMA Grill account. It provides structured and secure access so your agent can perform POMA Grill operations on your behalf.

Way Forward

With POMA Grill 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 or check out the Docs for deeper configuration options.

TOOLS

Supported Tools

Every POMA Grill action and event your agent gets out of the box.

Cancel Bucket Ingest Task

Irreversibly cancel a non-terminal POMA Grill bucket-ingest task.

Cancel Ingest Job

Request best-effort cancellation and removal of an ingestion job.

Delete Document

Permanently delete one deliberately selected indexed document, including its vectors and stored assets.

Get Bucket Ingest Task

Get the current state, progress, processing rate, credential status, and recent failures for a POMA Grill bucket-ingest task.

Get Document

Get metadata for one indexed document by its document ID.

Get Ingest Job

Get an ingestion job's current status and usage; poll this after Ingest Document until status is done, failed, or blocked.

Ingest Document

Upload one file or provide one public remote URL for asynchronous indexing, and return the ingestion job ID to poll with Get Ingest Job.

List Bucket Ingest Failures

Return one page of failed items for a bucket ingest task, ordered by item ID, with an opaque cursor for the next page.

List Documents

List one page of document metadata from the connected project.

Pause Bucket Ingest Task

Pause a non-terminal bucket ingest task in paused_user state.

Preview Bucket Ingest

Validate S3 or GCS credentials and preview matching source objects without creating a bucket-ingest task.

Resume Bucket Ingest Task

Resume a bucket ingest task paused by the user, restoring its pre-pause state and waking processing for the next scheduler tick.

Retry Bucket Ingest Failures

Retry all or selected failed items in a bucket ingest task that is in done_with_errors or materialising.

Search Documents

Search indexed content across the project or within one document, returning either prompt-ready context or structured matching chunks.

Submit Bucket Ingest

Create an asynchronous task to ingest matching objects from an S3 or GCS bucket into POMA Grill, optionally delivering results to another bucket.

Update Bucket Ingest Credentials

Replace and validate the source credentials for an active bucket ingest task.

Update Document Attributes

Set, change, or remove selected typed attributes on one indexed document.

FRAMEWORKS

How to build POMA Grill MCP Agent with another framework

ChatGPT logo

ChatGPT

Use POMA Grill MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use POMA Grill MCP with Claude Cowork

Atomic Agent logo

Atomic Agent

Use POMA Grill MCP with Atomic Agent

FAQ

Frequently asked questions

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

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 POMA Grill tools.

Yes, absolutely. You can configure which POMA Grill 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.

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 POMA Grill data and credentials are handled as safely as possible.

Start with POMA Grill.It takes 30 seconds.

Managed auth, hosted MCP servers, and every POMA Grill tool your agent needs.Free to start.

Start building