Nimble

This connector wraps the Nimble REST API v1 (app.nimble.com/api/v1). You authorize it once, in AnythingMCP; access tokens are then renewed automatically.

Setup:

1. Sign in to https://app.nimble.com → Settings → Integrations → API → Create OAuth app, with the redirect URI https://cloud.anythingmcp.com/api/mcp-oauth/callback on AnythingMCP Cloud, or <your AnythingMCP server URL>/api/mcp-oauth/callback when you host AnythingMCP yourself. Nimble only redirects to the URI registered on the app.
2. Enter the app's client_id as NIMBLE_CLIENT_ID and its client_secret as NIMBLE_CLIENT_SECRET, leave NIMBLE_REFRESH_TOKEN empty, and install.
3. Open the connector and click Authorize with Provider. Sign in to Nimble, allow access, and you land back on the connector page with the tools ready.

Scopes: basic,contacts,deals (comma-separated, as Nimble expects), which covers every tool here.

Already have a refresh token? You can paste it into NIMBLE_REFRESH_TOKEN instead of step 3, if you obtained it yourself for the same app (authorization code from https://app.nimble.com/oauth/authorize, exchanged at https://app.nimble.com/oauth/token).

Authentication: OAuth2 — engine handles the refresh. Access token sent as Authorization: Bearer ACCESS_TOKEN.

Contact model: Nimble unifies leads + contacts + companies into a single 'Contact' object with record_type discriminator (person or company). Fields are namespaced — fields['email'][0].value, fields['first name'][0].value etc.

Pagination: page (1-based) + per_page (max 30).

Rate limits: 5 req/sec per token. 429 → exponential backoff.

Out of scope here: pipeline analytics, social-listening streams, email-sync settings, group messaging.