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

# Tool reference

> The nine Condense MCP tools, what each one does, and which one changes your environment.

Condense MCP has nine tools. You do not call them yourself: your AI tool picks them by reading their descriptions. This page lists them, so you know what you can ask for and which tools to leave switched on when you approve a connection or set up governance.

Your AI tool is the final word on what it can use. It shows the tools that your role, your approved permissions and your administrator allow, which can be fewer than the nine below.

> [!NOTE]
>
> Every tool works in a workspace. If you name a workspace in your request, your AI tool uses it. If you do not, it reuses the workspace from earlier in the conversation, or asks you to pick one.

## Pipelines and connectors

These six tools are in the **Connectors & Logs** permission group.

* `get_current_pipeline`: Gets the pipeline in a workspace: its connectors, the connections between them and resource usage.
* `get_connector_config_deployed`: Gets the configuration of a deployed connector. It can also open a deployed custom (Application) connector as an editable application.
* `get_connector_configs_to_deploy`: Lists the configuration fields you need to deploy a prebuilt connector.
* `get_custom_connector_configs`: Lists the configuration fields you need to deploy a custom connector or application.
* `deploy_connector`: Deploys a prebuilt or custom connector with the configuration you give it. **This is the one tool that changes your environment.**
* `get_connector_logs`: Gets the logs of a deployed connector.

## Workspaces

* `ensure_workspace`: Picks the workspace for the request: the one you named, the one already in use, or asks you to choose. It is in the **Connectors & Logs** permission group.
* `get_all_workspaces`: Lists all workspaces you can access in the connected environment. It is an internal tool that is always on. Your AI tool calls it on its own to find your workspace, and it cannot be disabled or paused.

## Documentation

* `query_docs`: Searches the Condense documentation and returns the most relevant sections. It can rerank the results. It is in the **Documentation** permission group.

## The tool that changes your environment

`deploy_connector` is the tool that deploys a connector. Three things to know before you ask your AI tool to use it:

* **Your role decides.** You need a Condense role that lets you deploy in that workspace. Approving a connection does not add to it.
* **An environment can block it.** If an administrator set the environment to Strict read-only, any action that changes state is blocked, whatever your role allows. See [Scope and permissions](https://docs.condense.io/condense/v3.0.0/mcp/scope-and-permissions.md).
* **You can leave it out.** Clear `deploy_connector` on the approval page, or later on the AI Tools page, if an AI tool should only read.

Before you deploy, ask for the configuration fields first with `get_connector_configs_to_deploy` or `get_custom_connector_configs`, and read the values your AI tool is about to send.

## Related

> [card] [Ask Condense MCP](https://docs.condense.io/condense/v3.0.0/mcp/ask-condense-mcp.md)
>
> Example requests for each tool, and what each one needs.

> [card] [Usage and limits](https://docs.condense.io/condense/v3.0.0/mcp/your-connected-ai-tools.md#usage-and-limits)
>
> The limits that apply to all tools, shared by your organization.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.