Skip to main content
If a tool your team uses exposes an MCP server, you can plug it into Quivly and its tools become available to agents, skills, and Ask Quivly. This is the mirror image of the Quivly MCP server: that one lets external AIs use Quivly’s data; this one lets Quivly’s AI use external tools.

​
Connecting a server

1

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

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

Review and add

Confirm, and tool discovery runs automatically.

​
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

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.
Any MCP server reachable over HTTPS with no auth, bearer-token auth, or MCP OAuth.