FinDash Docs · Reviewed 2026-08-09
MCP Setup for ChatGPT and Claude
Connect ChatGPT, Claude, Claude Desktop, or Claude Code to your FinDash firm through the hosted remote MCP server, then verify access before using client data or write tools.
Where setup lives in FinDash
Open Firm Settings → MCP AI Tools. This page shows the canonical MCP URL, platform-specific connection instructions, the representative tool catalog, a browser smoke test, and Connected MCP Apps. Copy the production URL shown there; the in-browser test may use a local proxy during development, but external clients must use https://findash.ai/api/ai/mcp.
Who can connect and what they can see
A FinDash firm admin or advisor must complete OAuth. The connection does not become a universal firm credential: an advisor remains limited to the advisor's assigned or shared client book, while firm-admin-only tools remain hidden from advisors. The available tool list is filtered again by OAuth read/write scope and is discovered by the client at connection time.
Read tools, write tools, and previews
FinDash publishes MCP annotations that distinguish read-only tools from tools that can change data. Write tools require the mcp:write scope, and the client may show an approval prompt before a call. Many FinDash write tools accept dryRun=true for a preview and an idempotencyKey to make retries safer; read the returned target, warnings, and diff preview before applying a real change.
Choose the right client record
Resolve a person before writing when names are ambiguous. client_accounts_create creates a full FinDash login account plus its linked CRM contact; contacts_upsert creates or updates a contact-only CRM record. For existing clients, pass a stable clientId or contactId when possible instead of relying on a name match.
Connection lifecycle and revocation
FinDash issues short-lived access tokens and supports refresh tokens for connected apps. Review connections under Firm Settings → MCP AI Tools → Connected MCP Apps. Revoke one grant or use Revoke All/Revoke Mine to stop future refreshes. A token already issued before revocation can remain valid until its roughly one-hour expiration, so also disconnect the connector in ChatGPT or Claude when access must be removed.
What you can ask it to do
Common capabilities include resolving clients, reading contacts and client accounts, retrieving notes, documents and meeting transcripts, reviewing tasks, workflows and opportunities, and reading financial planning context. Depending on role and scope, write tools can create or update contacts, notes, tasks, workflows, opportunities, documents, goals, cash-flow scenarios, and manual account data. The discovered tool list in your connected client is the source of truth.
Use MCP for custom reports, not the built-in export
For an ad hoc report, resolve the exact client and combine read-only tools such as client_brief_get, client_financial_snapshot_get, client_investment_positions_list, client_cashflow_summary_get, client_transactions_list, client_goals_list, and tasks_list. Require the AI client to preserve asOf, sourceCoverage, resolvedRefs, filters, row counts, and pagination. MCP does not open the dashboard Report Builder or generate its branded Exact PDF or PowerPoint; use the Dashboard Reports & MCP Exports guide when you need the official FinDash deliverable or copy-ready custom-report prompts.
Troubleshooting
If the connector control is missing, check ChatGPT or Claude workspace policy. If discovery fails, confirm the URL ends in /api/ai/mcp and remove any stale connector before adding it again. If OAuth says access denied, sign in with a FinDash firm admin or advisor account. If a tool is missing, check the authorizing user's role and whether the grant includes write scope. For support, email hello@findash.ai.
Step by step
- Check transport and auth: Ask: “Call the Findash ping tool and tell me the server version.” This confirms MCP routing without reading client records.
- Run one bounded read: Ask for your next five open tasks or resolve one known test client. Confirm that the result matches the authorizing user's expected access.
- Inspect a proposed write: Use a non-production record and request dryRun=true when supported. Verify the resolved client, changed fields, warnings, and diff preview.
- Review and revoke: Return to Firm Settings → MCP AI Tools → Connected MCP Apps. Confirm the app name and authorizing user, then test Revoke only when you are ready to reconnect.
Open this guide in FinDash Docs