Loading...

Documentation

MangoApps for Claude

Connect MangoApps to Claude — setup, scopes, tools, security, and admin controls.

At a glance

Endpoint

https://mcp.iq.mangoapps.com/api/v1/mcp

Protocol

Model Context Protocol (MCP) 2025-06-18, Streamable HTTP transport

Authentication

OAuth 2.1 with PKCE; Dynamic Client Registration (RFC 7591) — Anthropic's connector backend registers itself with our authorization server, then the end user signs in to their MangoApps tenant to consent.

Tools available

Up to 885 tools across 80 product domains — Forms, Tasks, News Feed, Surveys, Reporting, Scheduling, Recognition, OKRs, Compensation, and more. The actual set surfaced to Claude in any given session is filtered by (a) the apps your tenant has enabled, (b) the scopes you grant during consent, and (c) your individual access rights inside MangoApps.

Rate limits

5,000 reads/hour per access token. 200 write operations/hour per (connector × tenant). 60 token refreshes/minute per source IP.

Audit

Every tool call recorded with the calling client, the user, the tool, the call latency, and the truncated arguments. Visible to tenant admins at /admin/connectors.

Availability

The MangoApps connector is enabled per-tenant by a MangoApps administrator. It's not gated by pricing tier — trial tenants, design partners, and any customer whose admin has flipped the switch can use it. If you can't authorize the connector, ask your tenant administrator or your MangoApps account team to enable it for your tenant.

Setup

For end users (one-click connect)

  1. In Claude.ai, open Settings → Connectors.
  2. Find MangoApps in the directory and click Connect. (If you don't see it in the directory yet, choose Add custom connector and paste https://mcp.iq.mangoapps.com/api/v1/mcp.)
  3. You'll be redirected to a "Which MangoApps tenant?" page. Enter your tenant slug — the part of your MangoApps URL before .workforce.mangoapps.com. For example, if you sign in at acme.workforce.mangoapps.com, enter acme.
  4. Sign in to MangoApps if you're not already.
  5. The consent screen lists every MangoApps domain Claude is requesting access to (Forms, Tasks, etc.). Review and click Authorize.
  6. You're returned to Claude with the connector active. Start a new chat and ask anything — "list my recent form submissions", "summarize last week's surveys", "what's overdue on my OKRs?"

For Claude Desktop

Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) and add:

{
  "mcpServers": {
    "mangoapps": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcp.iq.mangoapps.com/api/v1/mcp"]
    }
  }
}

Quit Claude Desktop fully (Cmd+Q) and relaunch. The first connection opens your browser for the OAuth consent flow, then the connector is ready.

For administrators

Tenant-level controls

Tenant administrators can manage every active connector from https://<your-tenant>.workforce.mangoapps.com/admin/connectors:

  • See who connected — Each row shows the OAuth client (e.g., "Claude.ai"), the user who authorized it, the scopes granted, and the last-used timestamp.
  • Revoke access — One-click revokes every active token issued to that connector for your tenant. The connector cannot reconnect without a new user authorization.
  • Audit log — Bottom of the page lists the most recent MCP tool calls (tool name, status, latency). Retained per the tenant's audit retention policy.

App-level controls

Disabling a marketplace app in MangoApps automatically removes its tools from the connector's catalog. For example, if your tenant disables the "Sites" app, Claude can no longer list, create, or modify Sites pages even if the user had previously consented to those scopes.

User-level controls

The connector inherits each user's permissions in MangoApps. A user without permission to view payroll data cannot use Claude to view payroll data, regardless of the OAuth scopes granted.

Visibility groups apply: if your tenant restricts an app to a specific group (e.g., "HR Managers only"), a user outside that group will not see the app's tools in their connector even if they request the scope.

Privilege gate for broad access

The mcp:all_tools scope — which grants Claude access to every domain — can only be authorized by tenant administrators (super_admin, admin, owner roles). Non-admin users must request per-domain scopes (read:forms, write:tasks, etc.) and can only authorize the scopes their role allows them to exercise in MangoApps.

Tools and scopes

The connector exposes 885 tools across 80 product domains. Each tool declares whether it is read-only or destructive via standard MCP annotations (readOnlyHint, destructiveHint), and Claude.ai surfaces these badges in the consent screen and tool-call approval dialogs.

Scope naming

Scopes use the pattern read:<domain> and write:<domain> for every product domain that exposes tools. For example:

  • read:forms — View forms and your submissions
  • write:forms — Create forms and submit form data
  • read:tasks / write:tasks — Tasks app
  • read:reporting — Run reports and view dashboards
  • mcp:all_tools — Broad access to every domain (admin-only; see "Privilege gate" above)

The complete scope list is published at /.well-known/oauth-authorization-server on every MangoApps tenant.

Sample prompts

What Claude can do, with the right scopes:

  • "List the 5 most recent form submissions for the new-hire onboarding form."
  • "Create a feedback survey for the new field-team app, set it to expire in 14 days."
  • "What's overdue on my OKRs? Group by quarter."
  • "Summarize last month's engagement survey — top themes broken down by department."
  • "Find every shift this week that conflicts with an approved time-off request."
  • "Post to the news feed announcing the Q3 results, with highlights from the attached board deck."

Security and privacy

Data boundaries

  • Claude can access only the data the consenting user could see in MangoApps directly.
  • Each access token is bound to a single MangoApps tenant. Tokens issued for tenant A cannot read or write tenant B's data — enforced by a tenant_id field on every issued token, checked on every request.
  • Tool call inputs and outputs are not used by MangoApps to train AI models, build user profiles, or feed analytics beyond per-tenant usage metering.

Transport and origin

  • All connections require HTTPS.
  • The MCP server validates the HTTP Origin header against an allowlist (claude.ai, claude.com, MangoApps tenant subdomains) to defend against DNS-rebinding attacks.
  • OAuth 2.1 with PKCE (S256 only) prevents authorization-code interception.
  • Token endpoint, registration endpoint, and tool endpoint each have separate per-IP rate limits.

Once data reaches Claude

When the user invokes a tool, the tool output is returned to Claude's runtime so it can compose a response. From that point, the data is subject to Anthropic's privacy policy: anthropic.com/legal/privacy. MangoApps does not control retention or downstream use by Anthropic.

Audit trail

Every tool call writes an audit record with the tool name, calling client name (e.g., "Claude.ai"), the consenting user, the timestamp, the call latency, and a truncated copy of the call arguments. Audit records are tenant-scoped and accessible only to tenant administrators. They are retained per the tenant's configured audit retention policy.

Full privacy policy

See the MangoApps Privacy Policy, specifically the section "AI Assistants and MCP Connectors".

Troubleshooting

"I authorized but Claude says no tools are available"

The most common cause is that your tenant has disabled some or all marketplace apps, so even with broad scopes the catalog is empty. Ask your admin to check /admin/marketplace_apps for app enablement. If you're on a non-admin role, you may have requested scopes that exceeded your visibility — try a narrower scope like read:forms first.

"Tool call returns 'not accessible'"

The corresponding app was disabled for your tenant, or your user account is outside the app's visibility group. Ask your tenant administrator.

"OAuth flow doesn't complete in Claude Desktop"

For dev tenants that use self-signed TLS certificates, set NODE_TLS_REJECT_UNAUTHORIZED=0 in the env block of your claude_desktop_config.json. Never use this in production.

"I want to revoke a connector immediately"

End users: in Claude, open Settings → Connectors → MangoApps → Revoke. Tenant admins: from MangoApps, open /admin/connectors, find the application row, click Revoke. Either path invalidates the token immediately.

Contact

Questions, security disclosures, or feedback on the connector.

Product or setup questions: support@mangoapps.com
Security disclosures: security@mangoapps.com
Privacy questions: privacy@mangoapps.com

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?