FAQ

Cohesive360 is a paid Model Context Protocol (MCP) connector for SmartAdvocate. Once installed, Claude Desktop can read and write your SmartAdvocate data — cases, notes, tasks, calendar, phone messages, documents — by calling SmartAdvocate's CaseSyncAPI directly from your machine.

$199 per seat per month, billed through Stripe. First-time customers get a 14-day free trial. A seat equals one SmartAdvocate username — same user across laptop + home PC + phone counts as 1 seat. Cancel anytime in the Stripe customer portal.

No. Your SA username and password live only in your local Claude Desktop config file. The MCP authenticates to your SmartAdvocate tenant directly — our service never receives, stores, or sees your SA credentials. Case data flows machine ↔ SA; it doesn't transit us.

Account metadata (email, hashed password, org name), Stripe subscription state, the license key, and an HMAC fingerprint of the device-activation for seat counting. See the privacy policy for the full list.

Not currently. SmartAdvocate's CaseSyncAPI authenticates with username + password JWT only (same endpoint their internal SPA uses). We've probed 13 standard OAuth/OIDC endpoints and all return 404. When SA adds OAuth, we'll wire it in within a week.

At peak load — month-end reporting, big exports, long-running Ajax operations — the SA server can return HTTP 429 (rate limit) or 503 (temporary overload). The MCP client:

• Respects the Retry-After header when SA sends one.
• Falls back to exponential backoff (0.5s → 1s → 2s) if no header is given.
• Retries up to 3 attempts, then surfaces a clear "try again in a minute" message.
• Doesn't retry on 4xx errors other than 429 — those indicate your request is the problem, not SA's load.

We're in contact with SmartAdvocate for published rate-limit numbers. Until then, the conservative heuristic is: don't fire more than ~60 tool calls per minute from a single seat.

No. The client has a credential circuit breaker: if SA rejects your credentials once, the MCP remembers the fingerprint of the bad creds and refuses to try again until you update any part of the username/password/URL. This was the David Aminov lockout fix — a stale password used to cause every tool call to retry until SA locked the account. Now it trips the breaker and tells you what to fix.

Just paste the same config into Claude Desktop on the new machine. On the next tool call, the new device takes over the seat and the old device is gracefully kicked (it learns within ~60 seconds on its next validate). Seat count doesn't increase — it's still one SA username.

Your license is bound to the first SA tenant it activates against. You can't point one license at two tenants. If you need to test changes on test.smartadvocate.com first and then use them on app.smartadvocate.com, email support — we reset the tenant binding on request during your trial.

Stdio-transport MCPs (the current SDK default) run as a local process on your machine — perfect for Claude Desktop but not for Claude on the web. We're migrating to HTTP+OAuth transport for Anthropic's Connector Directory (web + mobile + desktop). ETA: Q3 2026.

Cancellation takes effect at the end of your current billing period. After that, all license instances are revoked — Claude stops being able to call SA on your behalf. Your account and subscription history remain in our DB; email privacy@cohesive360.com to delete them entirely (we complete requests within 30 days).

Not currently — the license server is Cohesive360-hosted. If you're a firm with compliance requirements that prevent calling an external license service, contact sales@cohesive360.com and we'll work something out.

support@cohesive360.com. Response times: < 4 business hours on paid plans. Include your license key's first 4 characters and the error message Claude showed you.