Your sales workspace, available to your agent.

If your agent can work in an authorized DM Faster source checkout, this prompt authorizes local setup only. Account access still requires your approval in the focused browser page.

Set up the DM Faster developer preview from this authorized source checkout for the current agent only.

1. Install repository dependencies and run the agent package build.
2. Use the official DM Faster CLI browser login. Let me compare and approve the confirmation code in the focused DM Faster page myself.
3. Add the built local DM Faster MCP server and the complete plugins/dmfaster/skills/dmfaster directory only to the current agent. Preserve unrelated configuration.
4. Verify remote authentication and run one read-only workspace briefing.

Never ask me to paste a DM Faster token, browser cookie, or extension credential into chat. Do not use browser automation on the DM Faster dashboard. The current developer preview is read-only; do not imply that it can create, edit, launch, send, schedule, or spend.

1. 1Builds only the local agent packages
2. 2Opens focused browser authentication
3. 3Preserves unrelated agent configuration
4. 4Verifies access with a read-only briefing

From the repository root, build the private workspace packages. Until public distribution is available, run the CLI directly from its built file or link it locally yourself.

npm ci
npm run build:agents

node packages/cli/dist/bin.js auth login --json

Login prints a short confirmation code and opens an app.dmfaster.com/connect/agent/… page. Compare both codes before approving. The browser never receives or displays the resulting credential.

node packages/cli/dist/bin.js auth status --json
node packages/cli/dist/bin.js workspace briefing --json
node packages/cli/dist/bin.js campaigns list --status Running --limit 10 --json
node packages/cli/dist/bin.js auth logout --json

On macOS the CLI stores an approved credential in Keychain. On supported Linux desktops it uses Secret Service through secret-tool. Unsupported credential stores fail closed instead of writing a plaintext token. DMFASTER_TOKEN remains an explicit developer fallback and takes precedence when set.

Authenticate once with the CLI, then configure the built stdio server. It reads the same OS-stored credential, keeps MCP protocol messages on stdout, and sends diagnostics only to stderr.

{
  "mcpServers": {
    "dmfaster": {
      "command": "node",
      "args": ["/absolute/path/to/dmfaster/packages/mcp-server/dist/bin.js"]
    }
  }
}

Replace the path with your checkout’s absolute path and restart the host if it cannot reload MCP configuration. For local development or self-hosting only, set DMFASTER_API_URL; production defaults to https://app.dmfaster.com.

During the source-only developer preview, configure the built MCP server separately and install the complete plugins/dmfaster/skills/dmfaster directory through your host’s local skill mechanism. Keep the skill’s references and agents folders together.

• ✓The skill prefers DM Faster MCP tools, then the CLI with structured JSON.
• ✓It treats browser cookies and extension worker credentials as forbidden fallbacks.
• ✓It refuses writes and external actions that the current interface does not expose.
• ✓Installing the skill grants no account access by itself.

The CLI and local MCP server use the same scoped Agent API. Seven tools cover the information an agent needs to understand current outreach without changing anything.

Lost a device or stopped using an agent? Open the private connected agents page to revoke its access immediately. That page lists and disconnects existing connections only; it cannot create credentials.

This page documents the active developer-preview contract. It is not a public installation announcement. There is currently no published npm package, hosted remote MCP endpoint, marketplace plugin, Windows credential-store integration, or write-action toolset.

Public distribution will add signed packages and a supported installer. Remote MCP, if offered later, will use Streamable HTTP with OAuth. Until then, use only an authorized source checkout and the focused browser login described here.