SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to connect POMA Grill to Claude

Connect Claude Web, Desktop and Cowork 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

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your POMA Grill account to Claude via Composio Connect, enabling it to retrieve prompt-ready context for onboarding docs, search indexed specs for API breaking changes, summarize recent contract clauses from POMA Grill, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate POMA Grill with

ChatGPTHermesAtomic Agent

Connecting POMA Grill to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your POMA Grill account

Back in Claude, ask it to connect to POMA Grill or give it any POMA Grill-related task.

For example, ask Claude to:

  • "Retrieve prompt-ready context for onboarding docs"
  • "Search indexed specs for API breaking changes"
  • "Summarize recent contract clauses from POMA Grill"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your POMA Grill account is ready to use.

What is the POMA Grill Claude Connector, 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.

Troubleshooting

1. Why does Claude not use the Composio connector for POMA Grill?

The connector can show as connected, but Claude must use it in each POMA Grill conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to POMA Grill again.

2. Why does Claude show an MCP server error before POMA Grill connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for POMA Grill.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect POMA Grill.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the POMA Grill authorization link not work?

The Composio connector is one server. Your POMA Grill account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the POMA Grill connection.
  • Composio creates a fresh POMA Grill authorization link.
  • Open that link in your browser and finish the POMA Grill sign-in.

4. Why do POMA Grill actions fail after they worked before?

The POMA Grill connection can expire or lose permission.

  • Ask Claude to inspect the POMA Grill connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the POMA Grill account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in POMA Grill.
  • If the action still fails with a permission error, check that the connected account has that permission in POMA Grill itself.

5. How do I switch to a different POMA Grill account?

Claude can manage the POMA Grill connection for you.

  • Ask Claude to disconnect or delete the current POMA Grill account.
  • Ask Claude to connect POMA Grill again.
  • Open the new Composio authorization link for POMA Grill.
  • Sign in with the other POMA Grill account in the browser.
  • After the account connects, ask Claude to retry the POMA Grill task.

6. Why is my POMA Grill connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your POMA Grill connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If POMA Grill tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect POMA Grill.
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

Hermes logo

Hermes

Use POMA Grill MCP with Hermes

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