> ## Documentation Index
> Fetch the complete documentation index at: https://docs.floral.so/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP overview

> Understand Floral's MCP server, authentication options, and workspace-bound tool access.

Floral exposes one remote Model Context Protocol server:

```text theme={null}
https://app.floral.so/mcp
```

An MCP client connects to this URL, authenticates a Floral user, discovers the tools that user can access, and calls them on the user's behalf.

## What MCP can do

Depending on the credential and workspace access, MCP tools can:

* search companies, people, meetings, Deals, and Tasks;
* read workspace context, taxonomy, members, Sources, briefings, summaries, and transcripts;
* create or update contacts, Deals, Tasks, notes, activities, owners, and tags;
* move Deals, complete or reopen Tasks, and archive or restore supported records;
* review and act on Intelligence suggestions;
* search Floral's product documentation.

The server filters its tool list for every connection. A client may see fewer tools because of token scopes, feature access, Work access, role, or workspace settings.

## Product docs and workspace Sources

Use `search_floral_docs` and `get_floral_docs_page` for questions about Floral's product, API, or MCP. These read-only tools require `context:read` and do not require Work access.

Use `list_sources`, `semantic_search_sources`, and `get_source` for the connected customer's own files, websites, policies, and other knowledge. Do not use workspace Sources to answer a product-support question. Do not include customer or workspace data in a Floral documentation search.

## Authentication choices

* **OAuth** is available to approved remote clients. You sign in to Floral and choose an eligible workspace. OAuth access is read-only.
* **Personal access token** works with clients that can send a custom `Authorization` header. You choose scopes and expiry. A token can include write scopes.

Start with [Connect an MCP client](/developers/mcp/connect), then read [Access and safety](/developers/mcp/access-and-safety) before enabling write scopes.