Fulldev

View saved version →

---
name: fulldev
description: Work with the person's Fulldev data and actions in their organization, through the Fulldev tools when they are connected and otherwise the Fulldev CLI, whose commands are the same tools. Use it for their tasks and projects in Fulldev Work; for their own profile and, as an owner or admin, the organization's members, invitations and teams; and for their own business tools, such as Google or Shopify, through Fulldev Connect. Also use it for what the organization's other Fulldev products add, such as websites, scans, conversations, meetings, documents and contacts, once the tools list them. What you can do comes from what the person may use.
license: MIT
compatibility: The Fulldev tools need the Fulldev connector (https://app.full.dev/mcp); the CLI needs Node.js 24 or later and network access to app.full.dev.
---

# Fulldev

Each Fulldev app has its own tools, named after it, `<app>_<verb>_<object>`, such as `work_list_tasks`, and the person gets only those they may use. Fulldev Connect's tools, such as `connect_google_calendar_events`, work on the person's own business tools.

Two routes reach the same tools with the same rules:

- **The Fulldev tools**, when the Fulldev connector is connected in this app: use them.
- **The `fulldev` CLI**, otherwise, in a terminal: `fulldev` when it is installed, else `npx -y fulldev <command>`. Each tool is a command: `<app>_<name>` is `fulldev <app> <name>`, with `-` for `_`. Add `--json` to every command whose result you read.

In a terminal, use the CLI for many changes or a large result even when the connector is connected: a script runs the commands and keeps only what you need, instead of one tool call per row through the conversation. The CLI signs in once on its own ([Sign in](#sign-in)).

| Step                              | Tool                                   | CLI command                                                    |
| --------------------------------- | -------------------------------------- | -------------------------------------------------------------- |
| What you may use                  | `account_get` and the tools you get    | `fulldev account get --json`, `fulldev tools`                  |
| A tool's input                    | The tool's input schema                | `fulldev work list-tasks --help`                               |
| Find rows by text                 | `work_search`, `contacts_search`       | `fulldev work search --query "launch plan" --json`             |
| Rows by filters, a page at a time | `work_list_tasks`                      | `fulldev work list-tasks --status open --json`                 |
| One row with all it has           | `work_get_task`                        | `fulldev work get-task --id <id> --json`                       |
| Create or change a row            | `work_create_task`, `work_update_task` | `fulldev work create-task ...`, `fulldev work update-task ...` |
| Run an action                     | `work_complete_task`                   | `fulldev work complete-task --task-id <id> --json`             |
| A service's settings and status   | `scan_list_sites`, `contacts_get_sync` | `fulldev scan list-sites --json`                               |
| A service's read-only queries     | `scan_get_findings`                    | `fulldev scan get-findings --site-id <id> --json`              |

## Start with what you may use

`account_get` gives the organizations and, in each, the person's member id and apps. With the CLI, `fulldev tools` lists every command you may use and `fulldev <app>` one app's; `fulldev <app> <command> --help` shows a tool's description and fields, and with `--json` its input schema. Read a tool's input before you use it.

When there are several organizations, name one in every call: `organization` (its slug) for a tool, `--org <slug>` for the CLI, which sends it as `organization`. Without it the server answers `ORGANIZATION_REQUIRED`. Ask the person which one when it is not clear, an

Preview of the first 4,000 characters. Read full instructions →