Built-in Connectors
Capabilities and current availability of every Connector included with Minara.
The Catalog lists every built-in Connector. The provider detail screen is the source of truth for availability in your current Minara build. A disabled Connect action includes the reason and the next step.
Productivity
Google Workspace combines five services under one Google identity:
- Google Drive
- Google Docs
- Google Sheets
- Google Slides
- Google Forms
Choosing Docs, Sheets, Slides, or Forms also grants the Drive access needed to find that content. Minara raises the Drive permission to the highest selected Workspace service level and shows the change before sign-in.
Developer
Crypto exchange
Binance is available only to foreground tool calls in the main Chat and its immediate foreground delegation. Automation, Workflow, Custom Agent, scheduled, event, signal, and non-Chat sessions cannot discover or call it. Eligible Binance CEX requests use Connector-first routing. Binance Web3 and on-chain requests remain on native Web3 tools. Withdrawals to external addresses and Agentic subaccount management are unsupported.
Binance Agentic does not currently publish an OAuth token revocation endpoint. Disconnecting therefore removes Minara's local token but cannot invalidate a copied token remotely. Before disconnecting, revoke the Authorized Application in Binance API Management. New connections start with read-only access; enable trading capabilities explicitly only when needed.
Brokerage
Brokerage Connectors provide current account context. They do not create a cross-broker accounting ledger.
Brokerage scope is limited to current cash, buying power, positions, orders, and account activity exposed by the provider. Minara may summarize a snapshot from accounts you explicitly select. It does not claim TWR, XIRR, tax lots, corporate actions, or audit-grade historical performance from those snapshots.
Trading supports eligible single-leg stock and ETF orders only. Each order requires a current account, preview, fresh confirmation, and execution receipt.
Execution paths
Minara prefers the provider's MCP tool for a supported office action. During connection preflight, Minara may assign a built-in REST adapter to an office action that the MCP server does not expose. That assignment remains fixed for the capability snapshot. A timeout, authorization error, rate limit, server error, or unknown result never triggers a runtime switch.
Custom MCP servers and all brokerage Connectors are MCP-only.