Skip to content

MCP Server

BETA

The 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:

Findable MCP servertext
https://mcp.findable.ai

Development and staging environments use https://mcp.findable.dev.

Connect an Agent

  1. Open the integrations, connectors, or MCP settings in your AI agent.
  2. Add a custom connector and paste the Findable MCP server URL.
  3. Sign in to Findable when prompted.
  4. Authorize the agent to access your Findable account.

Microsoft Copilot Studio

Copilot Studio connects through its native MCP connector, which handles the OAuth sign-in for you.

  1. In Copilot Studio, open your agent and go to Tools > Add a tool > Model Context Protocol.
  2. Choose the option that discovers the server from its URL (labelled Dynamic discovery in current builds) and paste https://mcp.findable.ai.
  3. Create the connection. A Findable sign-in window opens — sign in and choose Allow. Let the window finish redirecting back to Copilot Studio on its own; closing it early leaves the connection incomplete.
  4. Add the connected tools to your agent and publish.

Each user connects with their own Findable account and sees only what that account can access. Single sign-on is not required. Copilot Studio limits how much a tool may return, so Findable’s search and folder tools reply with compact result lists — the agent then calls get_document to attach the one file you picked.

Access 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 in public beta. Your organisation must grant MCP access directly or through a group, or you must have customer administration access.
  • You can revoke connected agents from Findable settings.
  • 26 tools are read-only. The only write tool starts 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 27 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_collection

Lists and discovery

list_buildingslist_portfolioslist_projectslist_collectionslist_userslist_integrations

Tasks

list_tasksget_task

Documents and Q&A

search_documentslist_folder_childrenget_documentget_document_metadataask_findable

SharePoint

list_sharepoint_documentsget_sharepoint_sync_statuslist_sharepoint_subscriptions

Red flag

get_red_flaglist_red_flag_itemsget_red_flag_itemgenerate_red_flagWRITE

Compatible hosts

Findable works with standards-compliant remote MCP clients, including Claude web, Desktop and Code, ChatGPT connectors, and Microsoft Copilot Studio's native MCP connector. Interactive result widgets appear only in hosts that support MCP Apps; all other hosts receive the same data as text.

Interactive 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.

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.

Related Docs