Documents and answers
Search documents, open a file, and ask Findable a question that comes back with the source document.
- “Find the latest fire strategy for Building A.”
- “What does the ventilation O&M manual say about filter changes?”
Works with Claude & ChatGPT
Findable's MCP server lets the AI assistant your team already uses search your building documentation, answer questions with sources, and look up tasks and red flags. Everyone signs in with their own Findable account, so the assistant sees exactly what they can see in Findable, and nothing more.
Developer docs: MCP server
The Model Context Protocol (MCP) is an open standard that lets AI assistants use tools in other systems. The Findable MCP server is Findable's connector for it: add the server URL as a custom connector in Claude, ChatGPT, Microsoft Copilot Studio, Cursor or another MCP client, sign in with Findable, and the assistant can work with your buildings and documents in the middle of a conversation.
Claude
Web, desktop and Claude Code
ChatGPT
Through connectors
Microsoft Copilot Studio
Native MCP connector
Cursor, VS Code
And other MCP clients
What you can ask
The assistant picks the right Findable tool for each question. A few examples of what teams ask:
Search documents, open a file, and ask Findable a question that comes back with the source document.
Find buildings, portfolios, projects and collections by name, and see what sits in each.
Read tasks, routines and checklists. Where enabled, the assistant can propose a change that you approve in Findable.
Read the red flag snapshot and its items: the documentation gaps Findable has found.
Check the SharePoint sync status and list the documents synced from SharePoint.
Connect Claude & ChatGPT
Server URL
https://mcp.findable.ai
Using Claude Code? Run:
claude mcp add --transport http findable https://mcp.findable.ai Step-by-step guides for each client are in the developer docs. Developer docs: MCP server
Security and access
People connect with their own Findable sign-in through OAuth 2.1 with PKCE. There are no shared API keys or client secrets to hand out.
Every tool call is checked against the same permissions as the Findable app, so an assistant only reaches the buildings and documents its user can open.
Administrators decide what each person can see in Findable access control, and the assistant sees nothing more. Connected assistants can be revoked from Findable settings at any time.
Most tools only read. Where changes to tasks and routines are enabled, the assistant prepares them and they run only after someone approves them in Findable.
Any assistant that supports remote MCP servers with OAuth sign-in. That includes Claude on the web, Claude Desktop and Claude Code, ChatGPT connectors, Microsoft Copilot Studio through its native MCP connector, and Cursor. In assistants that support MCP Apps, such as Claude, many results appear as interactive cards; elsewhere the same data arrives as text.
No. The assistant acts as the person who signed in. Every request is checked against that person’s Findable permissions, so it can only find buildings, documents and tasks they can already open in Findable.
Findable returns the result of each tool call to the assistant, and the AI provider behind the assistant processes it under your organisation’s agreement with that provider. Choose an assistant and plan that meet your organisation’s data requirements.
There is nothing to switch on. Anyone with access to an organisation, portfolio, building, project or collection in Findable can connect: they add the server URL https://mcp.findable.ai in their assistant and sign in. What the assistant can reach follows that person’s existing access.
Book a demo and we will connect Findable to Claude or ChatGPT on your own documents. Already a customer? Sign in to Findable and connect from your settings.