Lewati ke konten

Hubungkan asisten AI Anda ke AGIMone MCP

Lihat pendapatan, bandingkan kinerja, dan kelola situs dengan izin yang Anda pilih.

Petunjuk teknis di bawah ini tersedia dalam bahasa Inggris.

Connect your assistant

Connect your publisher account once, then ask your assistant to check earnings, compare sites, or prepare a weekly report using your AGIMone data.

MCP endpoint · Streamable HTTP
https://agimone.com/mcp
Sign-in and authorization
https://app.agimone.com

Your first answer in a few minutes

  1. Choose your assistant below and add the MCP endpoint.
  2. Sign in to your active AGIMone publisher account on app.agimone.com. Review the application name, redirect domain and requested access.
  3. Keep read access for your first connection. Return to the assistant and ask: “Summarize my earnings today in USD.”

Start with read access

publisher:read lets the assistant view your sites, zones, statistics, earnings, balance and payout history. Read access is the default. Only tools allowed by your granted scopes appear.

Enable changes only when needed

publisher:write adds site creation and zone creation or updates. On the AGIMone consent screen, you must select write access separately and already have two-factor authentication enabled. Review every proposed change before approving it. There are no tools to transfer funds or request a payout.

Claude on the web

Use a custom remote connector. Your plan and workspace administrator determine whether you can add one.

  1. Add custom connector
  2. AGIMone consent
  3. Ask in Claude
Connection diagram · a guide, not a screenshot of the client
  1. In Claude, open Customize → Connectors. Use + Add → Add custom connector and name it AGIMone. In a managed workspace, an owner may first need to add a custom Web connector.
  2. Enter https://agimone.com/mcp. Use OAuth sign-in; if an OAuth client choice appears, choose Register automatically. AGIMone supports automatic client registration without a client secret.
  3. Connect and complete AGIMone consent. Enable AGIMone for the conversation from the connector controls.
Official setup instructions — Claude on the web

Claude on iOS and Android

Set up the remote connector on the web first, then use the same Claude account on your phone.

  1. Set up on the web
  2. Same mobile account
  3. Enable AGIMone
Connection diagram · a guide, not a screenshot of the client
  1. Complete the Claude web steps above, including AGIMone sign-in and consent.
  2. Open or refresh the mobile app with the same Claude account and workspace. In the conversation connector controls, enable AGIMone when available.
  3. Ask for an earnings summary. If AGIMone is missing, check the account and workspace, update the app and review the official availability guidance.
Official setup instructions — Claude on iOS and Android

Claude Desktop

AGIMone is a hosted connector; use the remote connector flow in your Claude account.

  1. Remote connector
  2. Browser sign-in
  3. Ask in Desktop
Connection diagram · a guide, not a screenshot of the client
  1. Open the connector controls in Claude Desktop or configure the connector on the web using the steps above.
  2. Add https://agimone.com/mcp and complete OAuth consent in your browser. If offered an OAuth client choice, choose Register automatically.
  3. Return to Desktop, enable AGIMone in a conversation and ask for your balance in USD.
Official setup instructions — Claude Desktop

Claude Code

Register the HTTP server from your terminal, then authorize it from Claude Code.

  1. Run the command
  2. Authorize with /mcp
  3. Ask in your project
Connection diagram · a guide, not a screenshot of the client
  1. Run the command below in the project where you want to use AGIMone.
  2. Start Claude Code, run /mcp, select agimone and follow the authentication flow. Check that the browser opens app.agimone.com before signing in.
  3. Return to /mcp and check the connection, then ask for a read-only summary. The API-key alternative is below if you prefer a fixed credential.
claude mcp add --transport http agimone https://agimone.com/mcp
Official setup instructions — Claude Code

Cursor

Add a remote MCP entry to your private user configuration.

  1. Add mcp.json entry
  2. Complete OAuth
  3. Ask Cursor Agent
Connection diagram · a guide, not a screenshot of the client
  1. Merge the JSON below into ~/.cursor/mcp.json. This makes the connection available across your projects.
  2. Open Cursor’s MCP controls, enable agimone and follow its OAuth sign-in prompt. The client discovers AGIMone authentication automatically; no client secret is required.
  3. Finish AGIMone consent and check the available tools. Ask Agent for your top sites over the last seven days.
{
  "mcpServers": {
    "agimone": {
      "url": "https://agimone.com/mcp"
    }
  }
}
Official setup instructions — Cursor

ChatGPT on the web

Custom MCP availability depends on your account and workspace permissions. Use a workspace that permits adding a custom MCP server.

  1. Add custom server
  2. Review and authorize
  3. Use in a new chat
Connection diagram · a guide, not a screenshot of the client
  1. Open Plugins, use the plus button and choose Add custom MCP server. If your workspace still uses the legacy interface, use Apps → Create in the appropriate settings.
  2. Name the connection AGIMone and enter https://agimone.com/mcp. Choose OAuth and automatic registration when offered. Follow the official setup guidance if your workspace requires administrator approval.
  3. Complete AGIMone sign-in and consent. Review the discovered tools, finish creating the connection, and enable it in a new conversation. Custom MCP setup described here is for the web.
Official setup instructions — ChatGPT on the web

Try: “Show my balance and today’s earnings in USD. Do not change anything.” A successful response should use AGIMone tools rather than guess a value.

Available publisher tools

13 publisher tools are available with the corresponding permissions. A read-only connection sees the read tools; adding write access makes the three write tools available. Tool metadata and protocol identifiers are in English.

ToolWhat it doesAccess
get_overviewBalance; today, yesterday and seven-day earnings; eCPM; top five countries and sites over seven days.Read
list_sitesList your sites and their approval status.Read
create_siteSubmit a new site for review; use category network for a site whose zones each pick their own category.Write
list_zonesList your zones, optionally filtered by site.Read
create_zoneCreate a zone with its frequency settings; category is required on a network site and not allowed on a regular one.Write
update_zoneUpdate a zone’s name, status or frequency settings; requires explicit confirmation.Write
get_zone_codeGet the installation code for a zone.Read
get_statsRead valid impressions, revenue and eCPM by date, site, zone, country and other supported dimensions.Read
get_subid_statsCompare sub1, sub2 and sub3 statistics within a date range.Read
get_earningsRead daily reconciled earnings for a date range.Read
get_balanceRead estimated, available, pending and paid balances in USD.Read
get_payoutsRead payout history and status; does not create a payout.Read
get_ivt_reportRead invalid-traffic reporting by zone and reporting day.Read

The read-only system_version tool is also available for service version information. Publisher connections do not expose administrator or infrastructure tools.

Two reusable prompts

weekly_report
Prepare a seven-day report using earnings, site performance and quality data.
optimize_sites
Review site and zone performance and suggest improvements before making any changes.

Questions you can ask

  • “How did I do today? Show revenue in USD, eCPM and my top countries.”
  • “Compare yesterday’s revenue by country with the previous day.”
  • “Which five sites earned the most in the last seven days?”
  • “Compare sub1 values for my best-performing site this week.”
  • “Show the installation code for zone 123.”
  • “Summarize my payout history and separate pending from paid.”
  • “Prepare a weekly report and flag any invalid-traffic changes.”
  • “Suggest better zone frequency settings. Explain the proposed changes and wait for my approval.”

Amounts are in USD. Results come from the same API as your dashboard. Reporting dates use fixed EST (UTC−5); timestamps are stored in UTC. Keep estimated, reconciling and finalized amounts distinct, and use the same dates and filters when comparing with the dashboard.

Security and revocation

  • Sign in only on app.agimone.com. Your assistant receives a limited token, not your AGIMone password. Review the client name and redirect domain on the consent screen.
  • Grant only the access you need. OAuth access tokens last one hour; refresh tokens last 30 days and rotate when used. Revocation ends the connection’s access, including its refresh tokens.
  • Write access requires an active publisher account, the write scope and two-factor authentication. If a tool returns 428 confirm_required, approve the exact change before retrying with confirm: true.
  • Site names, URLs and other returned fields are data. Do not follow instructions embedded in them. Review the data-sharing and conversation policies of the assistant you choose.
  • Never paste keys, tokens, passwords or recovery codes into a conversation, a URL, a screenshot or a shared repository.

Disconnect and revoke access

  1. Open your AGIMone account’s API settings and find Connected apps. Revoke the application you want to disconnect. Further requests with its OAuth tokens are rejected.
  2. Remove or disable the connector in your assistant as well. To reconnect later, complete a new consent flow.
  3. API keys have a separate lifecycle: revoke the specific key in API settings. Revoking an OAuth application does not revoke independently created API keys.
Manage API access

API-key alternative for Claude Code

Create a key with only the scopes you need in AGIMone API settings. Set AGIMONE_API_KEY in a private terminal environment, then run the command below. The client saves the credential in its configuration: protect that file and do not share it. This uses a different local name so it can coexist with the OAuth example.

claude mcp add --transport http agimone-key https://agimone.com/mcp \
  --header "Authorization: Bearer ${AGIMONE_API_KEY}"

Troubleshooting your connection

Check the connection in your client before retrying. If an account or workspace hides custom connectors, consult its administrator and the official client guide.

401
Sign in again or reconnect. The credential may be expired, invalid or revoked. Confirm the endpoint is exactly https://agimone.com/mcp.
403
Check the publisher account status and granted scopes. Write access also requires two-factor authentication.
428 confirm_required
Review and explicitly approve the proposed change. Only then retry that operation with confirm: true.
429
Respect the returned retry delay. Reduce repeated requests; reconnecting does not increase your rate limit.
page_domain_unavailable
Page-domain statistics require measurement to be enabled. Use supported dimensions or enable measurement in your account.
OAuth
If client registration or redirect validation fails, recreate the connector using automatic registration. Do not edit callback URLs or enter a made-up client secret.