Developers

Connect authorized AI agents to 9bot.

9bot MCP lets compatible clients query, analyze, and operate WhatsApp community resources through permission-aware tools, structured Workflows, confirmation, and auditability.

Open MCP gateway Product guide Authentication

Connection sequence

  1. Enable MCP in the 9bot Dashboard.
  2. Create an application and choose read-only or full access.
  3. Authorize the required groups and tool policies.
  4. Add the remote endpoint to a compatible MCP client.
  5. Complete OAuth authorization.
  6. Discover the tools available to that application.

Remote endpoint

https://mcp.9bot.com.br/mcp

Capability families

Groups

Groups, communities, members, administrators, settings, and authorized operational context.

Reports

Activity, engagement, behavior, trends, growth, members, and community analytics.

Workflows

Authoring, deployment, execution, scheduling, processing, delivery, and ongoing management.

Messages and schedules

Messages, summaries, broadcasts, and one-time or recurring communications.

Automations and integrations

Commands, RSS, alerts, replies, connected services, and external event triggers.

Moderation, community, and jobs

Moderation controls, hosted experiences, and status or control for long-running operations.

Governance

Applications can be restricted by scope, access mode, group, allowlist or denylist, sensitive-data policy, confirmation, tenant configuration, and rate limits. Tool discovery reflects those restrictions.

Confirmation flow

  1. The agent receives the user's intent.
  2. 9bot produces a preview or expected effect when required.
  3. The user confirms the sensitive action.
  4. The validated operation executes.
  5. The result is recorded for oversight.

Client behavior

  • Use the exact schemas returned by tool discovery.
  • Prefer read-only tools for informational requests.
  • Confirm target groups, recipients, schedules, and message content.
  • Do not claim completion while a job is queued, running, or awaiting confirmation.
  • Do not expose credentials or private tenant data.
Compatibility: use a client that supports remote MCP and the authorization flow advertised by the production metadata. Client capabilities can change independently of 9bot.