MCP Server
BETAThe Findable MCP server lets MCP-compatible agents answer questions and perform analysis against the buildings, documents, tasks, SharePoint sync state, and red flag data you already have access to in Findable.
Server URL
Use the production URL when connecting an external agent:
https://mcp.findable.aiDevelopment and staging environments use https://mcp.findable.dev.
Connect an Agent
- Open the integrations, connectors, or MCP settings in your AI agent.
- Add a custom connector and paste the Findable MCP server URL.
- Sign in to Findable when prompted.
- Authorize the agent to access your Findable account.
Using Claude Code?
Run this command from your terminal:
claude mcp add --transport http findable https://mcp.findable.aiAccess and Security
The MCP server uses OAuth 2.1 with PKCE. Access is tied to your Findable user account, and every tool call is checked against the same permissions as the Findable app.
- Agents only see buildings and documents your user can access.
- Access is currently private beta and requires customer admin access.
- You can revoke connected agents from Findable settings.
- Most tools are read-only. The only write tool is red flag regeneration.
In the Findable app, go to Settings > AI agents to copy the environment-aware server URL, view connected agents, or revoke access.
Available Tools
The server exposes Findable-specific tools for resource discovery, document search, Q&A, task lookup, SharePoint status, and red flag reporting.
Account and navigation
whoamifind_resourcesget_customerget_buildingget_portfolioget_projectget_collectionLists and discovery
list_buildingslist_portfolioslist_projectslist_collectionslist_userslist_integrationsTasks
list_tasksget_taskDocuments and Q&A
search_documentslist_folder_childrenget_documentget_document_metadataask_findableSharePoint
list_sharepoint_documentsget_sharepoint_sync_statuslist_sharepoint_subscriptionsRed flag
get_red_flaglist_red_flag_itemsget_red_flag_itemgenerate_red_flagWRITEInteractive Results
In hosts that support MCP Apps — such as Claude — many tools return an interactive widget alongside their text answer instead of a plain list. In hosts without widget support, the same tools return clean text and the agent behaves exactly as before.
- Document search renders as a grid; selecting a result opens the actual document, not just a thumbnail.
- Buildings and portfolios render as cards you can drill into for detail, then search their documents or ask a scoped question.
- Red flag reports render as compliance cards you can drill from theme to finding to the evidence documents behind each finding.
- Widgets follow your Findable language preference and match the host's light or dark theme.
Same permissions
Every action inside a widget — opening a document, drilling into a building — is a fresh tool call, re-checked against your Findable access just like the agent's own calls. Widgets never surface data you could not already reach.
Recommended Flow
Agents should resolve names before fetching detail. Start with whoami to inspect access, use find_resources to resolve customers, buildings, portfolios, projects, or collections, then call the specific getter, list, search, or Q&A tool needed for the task.
Schema updates
MCP clients cache tool schemas at session start. If a newly released Findable capability is missing, restart the agent connection so it can reload the current tool list.
Related Docs
- API authentication - API keys and session tokens for direct API integrations
- Ask endpoint - Build your own Q&A flow without MCP
- Search endpoint - Query Findable documents directly