Quick Start

Quick Start: agentcentral + Grok Bot

Give a Grok Bot access to current Amazon seller data through agentcentral’s hosted MCP server.

Prerequisites

An agentcentral account with the required Amazon connections ready
A separate API key from the dashboard Keys tab
The Grok Bot app installed and signed in

1. Create a read-only key

Open Keys in the agentcentral dashboard, then choose Create key.
Name the key Grok Bot and select Full suite, read-only. Use a narrower reporting preset if the Bot only needs advertising or operations data.
Create the key, then copy the full ac_live_... value. It is shown once.

Keep the credential out of chat

Do not paste the API key or the signed Connector URL into a Bot message. The setup below uses Grok Bot’s masked secure secret request, which keeps the value out of the conversation transcript.

2. Add agentcentral as a custom server

Open a one-to-one conversation with the Bot that will use Amazon data.
Paste the setup prompt above.
Review the proposed server name and URL. The URL must be exactly:
```
https://mcp.agentcentral.to/mcp
```
Approve the add-server confirmation after the name, URL, and header name are correct.

This is a remote Streamable HTTP server. Grok Bot connects from its cloud environment; no local process or tunnel is required.

3. Enter the key through the secure secret card

Grok Bot should show a masked secret request for the complete Authorization header value. Enter Bearer followed by the full key:

Bearer ac_live_...

Use the secure card only. If the Bot asks you to paste the key into an ordinary message or save it in a file, stop and repeat the instruction to request it securely.

4. Verify the connection

Open Settings → Plugins → Yours and confirm agentcentral is installed and enabled.
Return to the conversation, type @, then attach agentcentral to the task.
Ask the Bot to confirm the marketplace and list the data areas available to it.

“Use agentcentral to confirm my marketplace, show the latest source dates, and list the Amazon data areas available to this Bot. Do not change anything.”

How access works in Grok Bot

Account-wide plugin

A custom server added in Grok Bot is available to every Bot on the same account. Use a dedicated key whose scope is safe for the full Bot roster.

One marketplace per key

Each agentcentral key is tied to one Amazon marketplace connection. Create another key and server entry when a Bot needs a different marketplace.

Read-only first

The recommended key can inspect data but cannot change Amazon. If you later enable account-changing access, keep Grok Bot approvals on and review the proposed values before allowing a change.

Recommended Bot profile

Put lasting scope and approval rules in the Bot description rather than repeating them in each task:

Review Amazon seller data through agentcentral. State the marketplace and date window used. Treat missing or stale data as a limitation. Do not change campaigns, listings, inventory, fulfillment, or account settings. Ask before any external action.

Troubleshooting

The Bot asks for the key in chat

Do not send it. Ask the Bot to use a masked secure secret request for the complete Authorization header value.

An OAuth or Authorize card appears

Cancel that flow. This guide uses a scoped key in an Authorization header. Remove the incomplete server and add it again with the header configured before Grok Bot tests the connection.

The server reports zero tools or an authentication error

Confirm the URL ends with /mcp. Re-enter the secure header value with the Bearer prefix; if the key was lost or revoked, create a replacement from the dashboard.

The custom server option is unavailable

Check Settings → Plugins. If the account does not offer Add, use Grok Bot’s support path for account access. Do not work around it by entering the key in chat.

The Bot cannot see the expected data

Check that the correct Amazon connection is ready in agentcentral, then verify the key’s marketplace and reporting areas. New connections need an initial sync before historical questions return data.

New to the platform? Read how agentcentral works. For Grok Bot’s own plugin and approval controls, see the Grok Bot documentation.

First useful tasks

Start with bounded questions that make the marketplace, date range, and source freshness easy to verify:

“Compare campaign spend, attributed sales, ACOS, and ROAS for the last 14 days. Include the source dates and any data gaps.”

“Show FBA stock, inbound units, 30-day sales velocity, and days of cover for products below 21 days of cover.”

“Break down settlement revenue, Amazon fees, refunds, ad spend, and net proceeds by ASIN for the latest closed settlement period. State what is excluded.”

“Review listing status, suppressed listings, recent content changes, and review trends for my top 20 products. Do not change anything.”

Available tools

agentcentral exposes 171 data tools across 5 domains, plus utilities for account onboarding, key status, action history, and product feedback:

Domain	Tools	Examples
Ads (read)	30	Campaign performance, portfolio rollups, campaign snapshots, DSP, Brand Store insights, budget pacing, advertising search terms, SQP, Brand Analytics search terms, ads coverage evidence, Brand Metrics, TACOS
Ads (direct API)	10	Bid recommendations, budget recommendations, ad eligibility, audience segments, DSP advertiser/entity records, live SP/SB/SD entity state, and targeting options
Ads (write)	60	Update keyword, target, ad group, campaign, budget, state, archive, audience bid adjustment, campaign/ad group/product ad/target creation, ad group/product ad lifecycle, SD archive operations, and negative targeting writes
Inventory (read)	24	FBA inventory, storage fees, listing registry, risk triage, inbound shipments, sales velocity, orders, returns, days of cover
Inventory (direct API)	7	Buy Box, pricing history, Subscribe & Save offers, FBA eligibility
Finance	5	Payment transactions, financial events, profitability review, settlement economics
Catalog	16	Product details, sales ranks, A+ Content, variations, customer feedback, listing quality, catalog cleanup, create listings and offer-only SKUs, convert existing SKUs to FBA, update listings, prices, and quantities
Fulfillment	19	MCF orders, shipping preview, create order, manage returns, FBA inbound plans, packing, placement, transportation, labels/BOLs, appointments, tracking

For the full tool reference, ask Grok Bot: “List all available agentcentral tools.”