Ask your AI assistant about your frontline operations.
Connect Claude, ChatGPT, or any MCP-compatible assistant straight to your Nimbly account — sites, audits, issues, schedules — read-only, scoped to your organization. No data exports required.
- 12 tools
- Read-only
- OAuth 2.1 + PKCE
- Streamable HTTP
- Single-organization scope
Runs on the Nimbly public API — requires API access on your plan. Talk to your account team to get access.

Your operations data, in the conversation
The data already exists in Nimbly. What used to take a request to ops, a pulled export, and a wait, now takes a question typed into the assistant your team already has open.
Audits and compliance
Pull submitted reports with their scores, questions, answers and photos over any date range, and summarise compliance by site, department or questionnaire.
Issues and corrective actions
Filter findings by status, severity, priority, site, assignee or due date, and read the full activity trail of any single issue to see how long it sat where.
Sites, people and plans
Resolve site, user, department and questionnaire names into records, and check audit schedules — planned, in progress, completed or overdue — across a date range.
Frontliner & customer interaction
Process frontline conversations data to track promotion, upsell, and service execution.
Store traffic intelligence
Analyze foot traffic, store visits, and dwell time to identify conversion opportunities across your stores.
What people actually ask
Things people ask once Nimbly is connected to an assistant.

- “Show me the five sites with the most open issues this month.”
- “List the audit reports submitted last week and summarise compliance rates.”
- “Which auditors completed the most reports in July?”
- “How long did our critical issues in Jakarta take to close last quarter?”
- “Which scheduled audits were missed at facility sites in the last 30 days?”
- “Give me the full detail of issue X, including its status history and photos.”
12 tools across seven data domains
Every tool is read-only and carries its own OAuth scope, so
you grant exactly the access you want. The usual pattern is a list_ call to find an
identifier, then a get_ call for full detail.
Sites
list_sites— stores, branches and outlets with their departments, city and timezone. Filter by site name, department, city or location.get_site— one site in full: address, timezone, departments and assigned users.
Audit reports
list_reports— submitted reports with scores and completion metadata. Filter by site, department, questionnaire, submitter, city, status and date range.get_report— one report in full: every question, answer, score and attached photo.
Issues
list_issues— findings and corrective actions. Filter by status, severity, priority, origin, site, department, category, creator, assignee, city and date range, with sorting.get_issue— one issue in full: status, severity, priority, assignees, due date, linked report and photos.get_issue_status_history— the chronological activity trail, with real status transitions separated from comments and reassignments.
Users
list_users— active users with role, email and status, searchable by name or email.get_user— one user: name, email, role, status, language and onboarding state.
Questionnaires
list_questionnaires— audit checklists in your organization, most recently updated first, with the question count of the latest version.
Schedules
list_schedules— the audit plan over a date range, each schedule with its date and status (not started, in progress, completed or overdue), plus per-status counts.
Departments
list_departments— departments defined in your organization, including disabled ones, with their status.
Built to answer accurately
Responses are shaped for assistants, not just for programs: the date window actually applied comes back with the results, partial pages say so, and filters backed by a fixed set of values are declared as such — so an assistant cannot quietly answer “none” when it means “not that filter”.
How to add Nimbly to your assistant?
Nothing to install. Nimbly runs as a hosted MCP server your assistant connects to directly, over Streamable HTTP. Point your assistant at the endpoint, sign in with your Nimbly account — the connection is authorised with OAuth and limited to the scopes you approve.
https://api-public-v2-bgd5wvtq7a-df.a.run.app/mcpClaude (web, desktop and mobile)
- Open Settings → Connectors.
- Choose Add custom connector.
- Paste the Nimbly MCP server URL.
- Sign in with your Nimbly account and approve the scopes.
Custom connectors are available on Claude Pro, Max, Team and Enterprise plans. Our listing in the Claude Connectors Directory is in review; the steps above work today either way.
ChatGPT
- Open Settings → Connectors (or Apps & Connectors).
- Add a connector using the Nimbly MCP server URL.
- Complete the OAuth sign-in to your Nimbly account.
Connector support depends on your ChatGPT plan and workspace settings; on some plans it lives behind developer mode. Our submission to the OpenAI app directory is in progress.
Claude Code and other MCP clients
claude mcp add --transport http nimbly \
https://api-public-v2-bgd5wvtq7a-df.a.run.app/mcpPrefer a service credential over an interactive login? Any client can send a Nimbly organization API key instead:
claude mcp add --transport http nimbly \
https://api-public-v2-bgd5wvtq7a-df.a.run.app/mcp \
--header "x-api-key: <your-api-key>"Generic client configuration
{
"mcpServers": {
"nimbly": {
"type": "http",
"url": "https://api-public-v2-bgd5wvtq7a-df.a.run.app/mcp"
}
}
}Need an API key, or not sure whether your plan includes API access? Ask your Nimbly customer success manager, or talk to us.

Built to be safe to turn on
The MCP server is the same public API your integrations already use, exposed through a protocol assistants understand. It's read-only, limited to a single organization, and stores nothing — no new write paths, no new data stores.
No writes, ever
All 12 tools are reads. Nothing in the MCP surface creates, edits or deletes a site, report, issue, user or schedule.
One organization per connection
Every request is bound to the organization that authenticated it. No tool can reach another organization's data, whatever it is asked.
Scoped consent
Seven scopes, one per data domain. A token missing a scope is refused for the tools that need it, so you can grant issues without granting users.
Modern OAuth
OAuth 2.1 with PKCE (S256), dynamic client registration, short-lived access tokens, refresh token rotation and revocation.
No copy of your data
The server holds no cache or copy of your records. Each tool call reads live from the platform and returns the result to your assistant.
Fair-use limits
Requests are rate limited per organization on the same budget as the REST API — one tool call costs one request. Tool discovery is not metered.
For IT and security
| Server URL | https://api-public-v2-bgd5wvtq7a-df.a.run.app/mcp |
|---|---|
| Transport | Streamable HTTP (POST /mcp), stateless — no session header required |
| Protocol revisions | MCP 2026-07-28 (handshake-free) and the 2025-era initialize flow, served by the same tool catalog |
| Authentication | OAuth 2.1 (PKCE S256, dynamic client registration, refresh rotation, revocation), or a Nimbly organization API key via x-api-key or Authorization: Bearer |
| Protected resource metadata | /.well-known/oauth-protected-resource (RFC 9728), advertised on 401 via WWW-Authenticate |
| Scopes | read:sites read:reports read:issues read:users read:questionnaires read:schedules read:departments |
| Tools | 12, all annotated read-only, non-destructive and idempotent |
| Rate limiting | Per organization, default 10 requests per second with a burst bucket; one tool call = one request. initialize and tools/list are unmetered |
| Dates | YYYY-MM-DD. Issue and report listings default to the last 7 days and report the window they applied |
Frequently Asked Questions
Can the assistant change anything in Nimbly?
No. The MCP server exposes reads only. Creating an issue, editing a report or reassigning work still happens in the Nimbly app.
Who can see our data?
Only the assistant you connect, on behalf of the account that signed in, for the organization that account belongs to. Access ends when you revoke the connection in your assistant or the token is revoked on our side.
Do we need a paid Nimbly plan?
The MCP server runs on Nimbly's public API. If your plan includes API access you can connect today; if you are not sure, ask your customer success manager.
Is it available in the Claude and ChatGPT directories?
Directory listings are in review with both Anthropic and OpenAI. Until they are live you can add Nimbly as a custom connector with the same URL and get the same tools.
Which assistants work with it?
Any MCP client that speaks Streamable HTTP — Claude, Claude Code, ChatGPT connectors, and the growing set of third-party clients and IDE agents that support remote MCP servers.
What about data residency and retention?
The MCP server stores nothing. Records are read live from the Nimbly platform under your existing agreement; see our privacy policy and service level agreement.
Put your operations data one question away
Connect Nimbly to your assistant in a couple of minutes, or talk to us about rolling it out across your team.







