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

> ## Agent Instructions
> Melso product MCP: https://melso.ai/api/mcp (OAuth; one company per grant). REST: https://melso.ai. Documentation-search MCP: https://docs.melso.ai/mcp. The docs search server does not act on customer accounts.
>
> Use the live tool schema and respect company membership. Ask the person to authorize the exact fiscal document version in the signed-in app. A professional prepares and files included returns after authorization; AI does not file alone. A prepared file or approval receipt is not evidence of filing. Never claim completion from an accepted Task or Run. Keep credentials out of chat and logs. Agents features are internal or by private invitation.

# connected_apps_connect

> Input, output and examples for the connected_apps_connect MCP tool.

<Info>Melso Agents is available only internally or by private invitation. Agents-specific features require existing access. For the autónomo fiscal service, see [Get started](/essentials/quickstart).</Info>

Ask the person to connect one app, such as gmail or google\_search\_console. An app they already have answers already\_connected with its accounts: use it and never ask again. Otherwise it returns a request: send its url (as a button with cta in a chat) and stop. The request waits on their Home until they connect the app or dismiss it, never expires, and asking again returns the same one. Connecting it wakes this chat or continues this Task. Pass another\_account only to add a different account of an app they have.

**Availability:** Autónomo / Empresa / Agents invitation.

**Catalog:** Core (`tools/list`).

The live catalog is authoritative: company type, membership, plan, connected apps and execution context can narrow this contract. [Understand access](/mcp/permissions).

## Input

### Agents / Autónomo / Company schema

```json theme={null}
{
  "additionalProperties": false,
  "properties": {
    "another_account": {
      "description": "Ask although they have an account of this app: a different account, or one to connect again.",
      "type": "boolean"
    },
    "area_id": {
      "description": "Area UUID that gets the account once it is connected.",
      "type": "string"
    },
    "toolkit_slug": {
      "description": "App toolkit slug, such as gmail or google_search_console.",
      "type": "string"
    }
  },
  "required": [
    "toolkit_slug"
  ],
  "type": "object"
}
```

## Output

A human connection link and any next-step instructions. The person completes authentication in the app.

The result uses MCP `content` blocks; JSON payloads are encoded in text and may also appear in `structuredContent`. Check `isError` before reading a success payload. The server does not currently declare an `outputSchema`, so treat additional fields as extensible. [Result handling](/mcp/results).

## Example

Use an OAuth access token issued for this MCP resource (a Run token for Run-only tools). Replace example identifiers with values from your own account. Write actions change data.

```bash theme={null}
curl --fail-with-body https://melso.ai/api/mcp \
  -H "Authorization: Bearer $MELSO_MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  --data-binary @- <<'JSON'
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "connected_apps_connect",
    "arguments": {
      "toolkit_slug": "gmail"
    }
  }
}
JSON
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.