integrations-external-tools.md

Integrations + External Tools

Issue: #24

Terminology: these are integrations (Excel runtime toggles), not Agent Skills. See Agent Skills interop for the standards mapping.

What shipped

• Tools & MCP manager UI (/tools, or /extensions → Connections)
  • enable/disable integration bundles per session and/or workbook
  • clear warnings for network/tool access
  • active integrations shown in the status bar
• Global safety gate: external.tools.enabled
  • default: on
  • when disabled, blocks all external integration tools
• Web Search integration
  • tools: web_search, fetch_page
  • providers: Jina (default, no key required), Serper.dev, Tavily, Brave Search
  • configurable provider + provider-specific API key in /tools
  • fallback: if a configured keyed provider fails with auth/rate-limit/server/network errors, search retries with Jina for that request and surfaces a warning
  • result output includes explicit Sent: attribution and provider/transport metadata
• MCP integration
  • tool: mcp
  • server registry (mcp.servers.v1) configurable in /tools
  • add/remove/test server URL + optional bearer token
  • bearer tokens are stored in the shared connection store (connections.store.v1, record builtin.mcp.servers) with legacy mcp.servers.v1 token fallback/migration

Runtime model

Integrations are resolved as:

1. session-scoped enabled integrations
2. workbook-scoped enabled integrations
3. union of (1) and (2), ordered by catalog
4. if external.tools.enabled is false → active external integrations become empty

Active integrations contribute both:

• tools (web_search, fetch_page, mcp)
• system prompt guidance (## Active Integrations section)

Notes

• External requests may be sent directly or routed via the existing proxy settings (proxy.enabled, proxy.url).
• MCP transport uses HTTP JSON-RPC requests against the configured server URL.
• Tool execution policy classifies web_search, fetch_page, and mcp as read-only/non-workbook operations.