---
name: agentic-workers-setup
description: Connect an AI tool to Agentic Workers, verify workspace access, and plan a worker around a business outcome.
---

# Connect to Agentic Workers

Use this guide when the person asks to connect Agentic Workers from their AI tool. Read the whole guide before starting. Setup is complete when a read-only call succeeds and the person confirms the workspace.

## 1. Connect the MCP server

Use the same origin as the URL from which you read this guide. The remote HTTP MCP endpoint is `/api/agw-mcp?login=true` on that origin. For the public production site, it is:

`https://www.agenticworkers.com/api/agw-mcp?login=true`

Add that URL through your tool's supported remote MCP configuration. Use browser sign-in and consent. If you cannot change connector settings, show the person the URL and guide them through adding it. Wait for sign-in before continuing. If their tool does not support remote HTTP MCP with OAuth, explain the limitation and stop setup.

Keep credentials in the tool's private credential store. Keep tokens out of chat, source files, logs, and copied prompts.

## 2. Verify access

Discover the tools using `tools/list`, then call `agw_agents_list` as a read-only check. Tell the person which workspace and agents you can access. Ask them to confirm the workspace. Stop if it is not the intended one, or if authentication or plan access fails. Explain the returned error instead of attempting another workspace.

Prefer canonical `agw_<resource>_<action>` names and use the discovered schemas as the reference for available operations.

## 3. Plan the first worker

If the person already gave a task, use it as the starting point. Otherwise ask what business outcome they want to work toward. Help them define:

- The outcome and a measure of progress, such as new leads or content views. A goal is a target, not a promised result.
- The worker's tasks, files, connected apps, and required access.
- Where it will run, its schedule, and the actions that need human review.

Present the plan before applying it. For a worker on the person's own computer, explain that the computer must stay on and connected. Hosted workers run in the cloud; availability and plan limits still apply. Explain any costs shown by the product before asking to proceed.

Custom metrics can track values on the workspace Metrics page. They require configured metric scripts and appropriate workspace permissions. Use them to report observed values; do not infer that the worker caused a business result.

## 4. Apply approved steps and verify

Ask for explicit approval before each write, execution, or destructive operation. State the exact target and expected effect, including any external messages, scheduled work, resource creation, or cost. Setup consent alone does not approve these actions.

Use only operations discovered from the connected server. If a step requires the web app, guide the person there. After an approved change, read the affected resource or run record and report the result. Keep unavailable operations and failed checks visible.

Finish with the confirmed workspace, the worker plan, and the next step that still needs approval. If setup was part of an existing task, continue that task within the person's approved scope.