How to integrate POMA Grill MCP with Atomic Agent

Connect Atomic Agent 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.

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

Atomic Agent is an open-source AI agent that runs on your machine and supports local models through llama.cpp. Connect it to 1,500+ apps through Composio, including POMA Grill.

This guide uses Atomic Agent's built-in Composio integration. You need Atomic Agent v0.5.6 or later, your own Composio API key, and a POMA Grill account. See the Atomic Agent documentation for installation instructions.

Also integrate POMA Grill with

How Atomic Agent connects to POMA Grill

Atomic Agent connects to Composio's Tool Router over Streamable HTTP MCP. It discovers the tools needed for your request, and Composio handles account authentication.

Execution and account-connection tools follow Atomic Agent's configured approval policy. Review any approval prompt before allowing an action on your connected account.

Connect POMA Grill to Atomic Agent

  1. Sign up or sign in to the Composio dashboard. Copy your API key.
  2. In Atomic Agent, open the Integrations tab and select Composio. Select API key, press e, paste the key, and press Enter. The tools become available immediately, without a restart.
  3. Ask Atomic Agent to do something in POMA Grill. It searches Composio for the right tool.
  4. On first use, open the sign-in link returned in the chat. Connect your POMA Grill account, then return to Atomic Agent to continue.

Headless setup

Add the following line to ~/.atomic-agent/.env, replacing YOUR_COMPOSIO_API_KEY with your key. Start Atomic Agent after saving the file.

bash
COMPOSIO_API_KEY=YOUR_COMPOSIO_API_KEY

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.

Use POMA Grill from Atomic Agent

With your account connected, ask Atomic Agent to work with POMA Grill in natural language. You can connect more apps through the same Composio integration as you need them.

Visit the Atomic Agent website or inspect the Atomic Agent source code.

Troubleshooting

Why is my API key rejected?

Copy the key directly from the Composio dashboard. Atomic Agent requires ASCII characters because it sends the key in an HTTP header. Remove any extra characters introduced when copying.

Why are Composio tools unavailable after saving a key?

Check that you use Atomic Agent v0.5.6 or later and that Composio is enabled in your configuration. A "composio": { "enabled": false } setting disables the integration while keeping the saved key on disk.

Does Composio have a free plan?

The Hobby plan includes 100,000 tool calls per month. Composio-managed OAuth apps have a lower included allowance. See Composio pricing for the current limits that apply to your connection.

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.

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