Find prospects with the agent you already use.

Paste this into the agent you already use. It can install the public, version-pinned integration and guide the campaign workflow without learning DM Faster's screens or internal tool names. Account access still requires your approval in a focused browser page.

Set up DM Faster Agent 1.0 for this agent.

1. Prefer DM Faster's hosted MCP endpoint at https://app.dmfaster.com/mcp when this host supports remote MCP with browser OAuth. Guide me through the host's normal connection flow and let me approve the DM Faster workspace and exact scopes myself.
2. For a local connection, confirm Node.js 24 and a supported OS credential store. In Codex, add the dmfaster/agents marketplace and install dmfaster@dmfaster-agents. In Claude Code, install the reviewed bundle from the same repository. Otherwise configure @dmfaster/mcp-server@1.10.0 and use @dmfaster/cli@1.10.0 browser login, or auth upgrade for new scopes, and let me compare and approve the confirmation code myself.
3. Verify the connection and run one workspace briefing. Existing grants never expand automatically.
4. For company research, discover filters, search companies, inspect profiles and website evidence, and save a private shortlist only when requested. Use company suggestions for selection; they are not an audience total. Keep exact counts for audience decisions and preserve real contact routes.
5. For Basic-plan Instagram prospecting, quote my requested account or posts and count, then start on my instruction with one stable idempotency key. Return the job ID promptly. Inspect savedCount, listUrl and settled creditCost, respect pollAfterMs, and reuse the same key and input on retries. Subscribe to completion only if I request it and this host supports MCP Events.
6. Enrichment is separately charged. Preview it and start only on my instruction within my credit budget. If credits run out, explain the exact balance and required credits. In OpenAI directory hosts, point to informational entitlement options without promoting upgrades or initiating a purchase. Never buy credits automatically or resume a blocked job just because the balance changed.
7. For a campaign goal, use grounded industry lookup, complete-plan validation, exact audience preview and an idempotent private disabled draft. Keep the complete latest campaign state on every planning call.
8. When I explicitly say to launch or pause, run the matching preflight. With my campaigns:control grant and a ready result, execute using the returned authorization. Show a browser approval or setup handoff only when DM Faster requires it. Inspect durable action receipts before claiming a message was delivered.
9. Send replies or book meetings only on my explicit instruction through the corresponding granted controls. Never treat a selected mention, extraction, enrichment or saved list as permission to contact anyone.

Never ask me to paste a DM Faster token, browser cookie or extension credential into chat. Do not silently install a browser extension, guess an audience total or bypass DM Faster's approval boundary.

1. 01Connects hosted MCP or installs the pinned local integration
2. 02Opens focused browser authentication
3. 03Researches companies and Instagram prospects
4. 04Launches only when you explicitly instruct it

Add DM Faster in a host that supports remote MCP with OAuth, using the endpoint below. Sign in to DM Faster and approve the workspace and exact permissions. Hosted connections require no local Node.js install or copied token.

https://app.dmfaster.com/mcp

Existing permissions stay in place until you approve a new grant. Company Database access follows your account entitlement; Basic-plan Instagram extraction uses your available lead credits. Revoke a connection from Agent access settings when needed.

Compatible hosts can use the Companies and campaign views, company and saved-list mentions, and subscribed completion events. Host rendering and event delivery depend on the client. OpenAI directory approval remains a separate step.

The Codex plugin bundles the DM Faster skill and local MCP server configuration. Add the public repository marketplace, install the plugin, then start a new Codex session so its skills and tools load.

Review the official public source on GitHub before installing.

codex plugin marketplace add dmfaster/agents
codex plugin add dmfaster@dmfaster-agents

Claude Code can install the same reviewed bundle from the same public repository. A Claude subscription is not required to use DM Faster through Codex or a generic MCP host.

claude plugin marketplace add dmfaster/agents
claude plugin install dmfaster@dmfaster-agents

Prefer the plugin when your host supports it. For Hermes, another MCP host, or a shell-only workflow, use the pinned MCP or CLI commands below instead of cloning DM Faster's private product repository.

The public DM Faster plugin includes the portable Agent Plugins files that describe the skill and MCP connection together. Compatible clients discover the root plugin.json, the skills/ directory, and the schema-backed mcp.json; Codex, Claude Code, and Cursor manifests remain alongside them for host-specific installation.

dmfaster/
├── plugin.json
├── mcp.json
└── skills/
    └── dmfaster/
        └── SKILL.md

Agent Plugins standardizes package discovery, not a universal installer or authentication flow. Install through your host's supported repository or plugin flow, then authenticate with the pinned CLI. Never put a DM Faster token, browser cookie, or extension credential in mcp.json.

Run the public CLI without a global install. Login prints a short confirmation code and opens an app.dmfaster.com/connect/agent/… page.

npx --yes @dmfaster/cli@1.10.0 auth login --json

Compare both codes before approving. Review the requesting client, workspace, expiry, and exact scopes. The default full profile enables the complete Agent 1.0 flow; append --access read, plan, or draft for a smaller ceiling.

npx --yes @dmfaster/cli@1.10.0 auth status --json
npx --yes @dmfaster/cli@1.10.0 workspace briefing --json

Already connected but need a different access profile? Use auth upgrade with the access profile you need. The old credential stays usable while you approve and verify its replacement. Check priorCredentialRevokedin the result; if it is false, revoke the old session in Agent access settings.

npx --yes @dmfaster/cli@1.10.0 auth upgrade --access full --json

Use doctor to check setup and access, and describe to see a command's exact input schema before calling it. Command discovery works before login.

npx --yes @dmfaster/cli@1.10.0 doctor --json
npx --yes @dmfaster/cli@1.10.0 describe campaigns list

The CLI and MCP server share the operating-system credential. macOS uses Keychain; supported Linux desktops use Secret Service through secret-tool. Unsupported stores fail closed instead of writing a plaintext token. The focused browser page never receives or displays the issued credential.

1. 01

   Brief

   The agent reads workspace priorities and turns your goal into a complete versioned campaign state.

2. 02

   Ground

   Industry lookup resolves supported TOL industries and asks you when the target is ambiguous.

3. 03

   Validate

   DM Faster checks targeting, messages, channels, delivery settings, limits, and required setup.

4. 04

   Preview

   The agent receives an exact audience total. A sample, estimate, or lower bound never substitutes for it.

5. 05

   Prepare

   List and campaign preparation create only private, disabled, retry-safe drafts.

6. 06

   Check readiness

   Preflight checks the exact campaign version, connection permissions, and browser readiness. It returns authorization or the required approval or setup handoff.

7. 07

   Act

   After your explicit launch or pause instruction, the agent uses DM Faster's short-lived, single-use authorization. A delegated connection needs no extra approval click.

If browser sending is not ready, launch preflight keeps the campaign disabled and returns one setup link plus the exact resume call. The user installs or reconnects the extension through the browser store; websites and agents cannot install it silently.

Before launch, your agent can inspect the exact saved messages and configure a LinkedIn invitation followed by a message after acceptance. If the person is already connected, the message can be sent directly. A recorded human reply on another channel for the same company stops an unsent LinkedIn message.

npx --yes @dmfaster/cli@1.10.0 campaign copy inspect CAMPAIGN_ID --json

Ask your agent to find companies using Shopify with active Meta ads. It first discovers the available Companies app filters, then searches with technology and ad-activity criteria together. It can inspect full company profiles, financials, technology evidence, social profiles, and decision-makers. Search supports every current Companies app filter; country-specific availability and data freshness still apply.

{
  "filters": {
    "technologies": ["shopify"],
    "metaAdsActiveOnly": true
  },
  "pageSize": 50
}

Save this JSON as company-search.json, then run the command below. Your agent can prepare the file for you. Use the returned query signature and revision when paging; a page size is not the total matching audience.

npx --yes @dmfaster/cli@1.10.0 companies search --input company-search.json --json

Saved company lists preserve available real email, LinkedIn, phone, Instagram, and Facebook contact routes. Decision-maker names and roles stay with their respective email, LinkedIn, or phone contact. Companies without contacts remain useful research rows; generated company identities are never Instagram targets. Saving a research list creates no campaign and sends nothing. Contact data is a stored snapshot, not proof of deliverability. Older lists are not automatically backfilled with contacts that were previously lost.

Say “Find 1,000 followers of this account.” Your agent can quote the work, start on your instruction and return a job ID promptly. Your available lead credits determine how many profiles you can request.

{
  "type": "followers",
  "identifier": "ACCOUNT_HANDLE",
  "count": 1000,
  "idempotencyKey": "my-followers-request-001"
}

Use the same input and key to recover a request. Start a new request only for new work. Inspect the returned job for saved profiles, the private list link and settled cost. One saved profile costs one lead credit. Collected profiles and reserved credits are progress, not final results; unused reservations are returned.

Enrichment has its own preview and separate cost: one successfully enriched missing profile costs one credit. When credits run out, your agent explains the exact available and required balance. OpenAI directory hosts can point to information about entitlement options, without starting a purchase or promoting an upgrade. You manage credits in DM Faster. A top-up alone does not resume a blocked request.

For a requested completion update, a compatible hosted MCP client can subscribe to the exact job. Clients without MCP Events use status reads. Native ChatGPT completion delivery remains unverified. Extraction and enrichment create no campaign and send no messages.

Your agent can inspect and update an ongoing Instagram campaign’s daily cap, pacing, and automatic sending window. It reads the current revision, applies your requested changes, and verifies the saved result. Pacing accepts 12–3,600 seconds. Daily caps are validated against the account’s current limit; provider limits still apply. Windows use the returned workspace timezone and can be toggled on or off.

Updating delivery settings does not launch a stopped campaign. A launch receipt or browser acknowledgement is not evidence that a message was delivered: the agent checks operation status and sending health before reporting success.

Configure the signed stdio server before or after CLI login. It starts without a credential and exposes connection_status so you can see missing access. After browser approval, it reads the new OS-stored credential without a server restart. The configuration below is the portable Agent Plugins mcp.json format: its schema and transport type tell compatible hosts how to discover the server. MCP protocol messages stay on stdout; diagnostics go to stderr.

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
  "mcpServers": {
    "dmfaster": {
      "type": "stdio",
      "command": "npx",
      "args": ["--yes", "@dmfaster/mcp-server@1.10.0"]
    }
  }
}

Restart the host if it cannot reload MCP configuration. Agent 1.0 requires MCP 2026-07-28 and intentionally does not downgrade to the 2025 protocol. Hosts that have not implemented that revision can use the version-pinned CLI with structured JSON instead.

The server is stateless: each planning call carries the complete latest campaign state. Durable campaign data, permissions, idempotency, exact counts, and approvals remain on DM Faster's server.

Hosted MCP, the CLI and the local MCP server expose the same 78 domain tools. MCP adds a connection check, Companies and campaign views, and app-only context mentions for compatible hosts. Prospecting, enrichment, company research, saved lists, replies, meetings, campaign controls and reporting are available. Full live-app parity is still in progress.

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.

Agent 1.0 is public as signed, provenance-backed npm packages and a repository marketplace for Codex and Claude Code. The public plugin also includes the portable Agent Plugins package for compatible clients. The local CLI and stdio MCP server work on macOS and supported Linux desktops with Node.js 24.

The hosted endpoint is https://app.dmfaster.com/mcp. Local Windows credential-store integration remains unavailable. Each client controls how it installs and lists Agent Plugins; Cursor requires its separate marketplace review. The GitHub catalog and npm release do not publish a universal ChatGPT/Codex directory listing. Native composer rendering and ChatGPT Events completion are not yet verified.