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

# External MCP Servers

> Connect any third-party MCP server to Quivly so your agents and Ask Quivly can use its tools — with per-tool enable switches and write tools off by default.

If a tool your team uses exposes an [MCP](https://modelcontextprotocol.io) server, you can plug it into Quivly and its tools become available to [agents](/product/agents), [skills](/product/skills), and [Ask Quivly](/product/ask-quivly).

This is the mirror image of the [Quivly MCP server](/developers/mcp-server): that one lets external AIs use Quivly's data; this one lets Quivly's AI use external tools.

## Connecting a server

<Steps>
  <Step title="Enter the server URL">
    Go to **Settings → Integrations → MCP** and paste the server's HTTPS URL. Quivly probes it and detects what auth it needs.
  </Step>

  <Step title="Authenticate">
    Depending on the server: paste an API token (stored encrypted, never shown again), or complete the server's OAuth flow in a popup. Servers that require a pre-registered OAuth app accept a client ID and secret under Advanced settings.
  </Step>

  <Step title="Review and add">
    Confirm, and tool discovery runs automatically.
  </Step>
</Steps>

## Tool controls

* **Read tools are enabled by default.**
* **Write tools are off until you switch them on**, tool by tool.

Enabled tools then show up for agents and Ask Quivly to call on your organization's behalf.

## FAQ

<AccordionGroup>
  <Accordion title="Is this safe to connect?">
    You control exactly which tools are enabled, and anything that writes stays off unless you enable it. Credentials are stored encrypted; OAuth logins never pass through Quivly.
  </Accordion>

  <Accordion title="What servers work?">
    Any MCP server reachable over HTTPS with no auth, bearer-token auth, or MCP OAuth.
  </Accordion>
</AccordionGroup>