External tools

Connect Arlo to external apps through MCP

Dana4 can give Arlo an on-demand Composio MCP toolset for services such as GitHub, Linear, Notion, and Gmail. The connection is scoped by workspace configuration and is initialized only when a request needs an external app.

Current scope. This page describes Arlo’s optional Composio integration. Dana4 does not currently expose the entire workspace as a general-purpose MCP server. Use the Claude, Hermes, or Python integrations when you want an external agent to join the workspace.

Configure the workspace

Open the workspace settings page and add:

Key	Required	Purpose
`composio_api_key`	yes	Authorizes creation of the workspace’s Composio tool session.
`composio_user_id`	no	Stable Composio user identity. Dana4 derives a workspace/user-scoped value when omitted.

Workspace parameter values whose names look like secrets are masked when the workspace is read back. They are still forwarded to agents that are members of that workspace, so membership remains the important trust boundary. Use a key intended for this environment rather than a personal all-purpose credential.

Use it in conversation

Ask Arlo for an outcome and name the external service:

@arlo.dana4 review the open issues in our GitHub repository,
group them by launch risk, and write the summary into /Launch readiness.

When the request actually requires an external app, Arlo enables the MCP toolset, checks whether the relevant Composio connection exists, and initiates authentication when needed. Complete the connection flow returned in the conversation, then repeat or continue the request.

The integration is lazy by design. Ordinary workspace conversation does not create an MCP session or expose the external tool catalogue.

Good boundaries

Connect only the applications needed by this workspace.
Ask for a specific outcome and destination document.
Review external write actions before making them part of a scheduled workflow.
Keep final decisions and durable output in Dana4 documents, not only in the external tool result.
Remove the workspace parameter when the integration should no longer be available.

Bring an agent instead

MCP gives Arlo tools. An agent integration gives another runtime a workspace identity, capability schema, tasks, and return path. Choose the latter when Claude, Hermes, or your own service should act as a named collaborator: