mcpField
V
Vernclaw Connect Cli

Vernclaw Connect Cli

Local
vernclaw.comBusiness & Marketing0Updated 3w ago

About Vernclaw Connect Cli

Vernclaw Connect Cli is a command-line interface for AI agents and automation scripts to discover and run Vernclaw connectors. Its JSON-first output and packaged Agent Skills cover SEO, social and video research, web search, URL extraction, and image generation.

Key features

  1. 01List and inspect connectors
  2. 02Invoke connectors from the CLI
  3. 03JSON-first output for agents
  4. 04Browser or API-key login
  5. 05Agent Skills for connectors
  6. 06Check asynchronous job status

Use cases

  1. 01Retrieve SEO metrics for a domain
  2. 02Research videos and social posts
  3. 03Search the web and extract URL content
  4. 04Run image generation from an agent

MCP support

The README lists MCP Servers among the Agent Skill ecosystem, but does not describe MCP server connections or MCP-specific behavior.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"vernclaw-connect-cli-dc369e": {
"command": "npx",
"args": [
"-y",
"skills"
]
}
}
}
Run commandnpx -y skills

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmskills

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

vernclaw-connect-cli

Official command-line interface for Vernclaw Connectors. Vernclaw Connect CLI gives AI agents and automation scripts JSON-first access to SEO metrics, YouTube research, X/Twitter readers, Product Hunt discovery, web search, URL extraction, and AI image generation.

npm Node.js License: MIT skills.sh

Install

npm i -g vernclaw-connect-cli

Use as Agent Skills

Each connector ships as an Agent Skill (a SKILL.md under skills/). Install them straight into your AI agent:

npx skills add hekmon8/vernclaw-connect-cli

Listed on the agent-skill ecosystem: skills.sh · AgentSkillsHub · MCP Servers.

Authentication

Browser login (recommended for interactive use):

vernclaw-cli login

Opens your browser for device-code authorization. Credentials are stored locally at ~/.vernclaw-cli.json.

API key login (for CI/CD and headless environments):

vernclaw-cli login --api-key YOUR_API_KEY

Generate an API key at vernclaw.com/settings/connectors (sign in → Connector Settings → Create API Key).

By default, the CLI targets https://vernclaw.com. For local or self-hosted environments, pass --api-base-url or set VERNCLAW_CLI_API_BASE_URL.

Managed Connector Access

Most CLI users only need Vernclaw authentication. Connector access is managed by Vernclaw, so individual CLI users do not need to configure separate service credentials.

Local Development Against a Local Vernclaw App

pnpm dev:connectors:local
pnpm install:cli:local
vernclaw-cli login --api-base-url http://localhost:3000 --api-key YOUR_API_KEY
vernclaw-cli list

The login command stores the local apiBaseUrl in ~/.vernclaw-cli.json, so follow-up commands keep targeting your local app until you log in again against another environment.

Commands

CommandDescription
vernclaw-cli loginAuthenticate via browser or API key
vernclaw-cli logoutRemove stored credentials
vernclaw-cli listList available connectors
vernclaw-cli describe <connectorId>Show connector details and parameters
vernclaw-cli invoke <connectorId> [flags]Run a connector and print connector output
vernclaw-cli job get <jobId>Check status of an async job
vernclaw-cli statusDisplay current login, subscription, and credit status

list prints a human-readable connector table by default. Use vernclaw-cli list --json when an agent or script needs the structured catalog payload.

Available Connectors

Connector IDCategoryModeSkill
generate.imageAIasyncSkill
seo.website-trafficSEOsyncSkill
seo.backlinksSEOsyncSkill
seo.serp-google-organicSEOsyncSkill
seo.google-trendsSEOsyncSkill
seo.keyword-search-volumeSEOsyncSkill
seo.keyword-suggestionsSEOsyncSkill
seo.site-keywordsSEOsyncSkill
seo.site-technologiesSEOsyncSkill
seo.backlinks-summarySEOsyncSkill
seo.domain-rank-overviewSEOsyncSkill
seo.domain-whoisSEOsyncSkill
seo.domain-authoritySEOsyncSkill
read.x.postSocialsyncSkill
read.x.repliesSocialsyncSkill
read.x.articleSocialsyncSkill
search.xSocialsyncSkill
search.tiktokSocialsyncSkill
read.tiktok.videoSocialsyncSkill
search.instagramSocialsyncSkill
read.instagram.postSocialsyncSkill
social.tiktokSocialsyncSkill
social.douyinSocialsyncSkill
social.instagramSocialsyncSkill
social.linkedinSocialsyncSkill
social.redditSocialsyncSkill
social.threadsSocialsyncSkill
social.wechatSocialsyncSkill
social.weiboSocialsyncSkill
social.xiaohongshuSocialsyncSkill
social.youtubeSocialsyncSkill
social.zhihuSocialsyncSkill
search.youtubeVideosyncSkill
read.youtube.videoVideosyncSkill
search.producthuntProductsyncSkill
list.producthunt.launchesProductsyncSkill
search.webSearchsyncSkill
extract.urlExtractsyncSkill

Quick Examples

# Check domain authority
vernclaw-cli invoke seo.domain-authority --domain example.com

# Estimate website traffic
vernclaw-cli invoke seo.website-traffic --domain example.com

# Expand a seed keyword
vernclaw-cli invoke seo.keyword-suggestions --keywords "openai" --market us --language english
vernclaw-cli invoke seo.keyword-suggestions --keywords "openai" --market us --limit 20

# Review a domain's keyword footprint
vernclaw-cli invoke seo.site-keywords --target openai.com --market us --language english
vernclaw-cli invoke seo.site-keywords --target openai.com --market us --all

# Inspect live Google organic results
vernclaw-cli invoke seo.serp-google-organic --keyword "openai" --market us --language english --device desktop --os windows --depth 5

# Inspect keyword trend trajectory
vernclaw-cli invoke seo.google-trends --keywords "openai" --market us --language english
vernclaw-cli invoke seo.google-trends --keywords "openai" --market us --points 50
vernclaw-cli invoke seo.google-trends --keywords "translator" --market us --language english --time-range past_7_days --type web --item-types google_trends_queries_list
vernclaw-cli invoke seo.google-trends --keywords "mcp server,translator" --market us --language english --time-range past_30_days --item-types google_trends_graph

# Fetch backlink summary snapshot
vernclaw-cli invoke seo.backlinks-summary --target openai.com

# Check domain rank overview
vernclaw-cli invoke seo.domain-rank-overview --target openai.com --market us

# Detect public technologies
vernclaw-cli invoke seo.site-technologies --target openai.com

# Inspect Whois timestamps
vernclaw-cli invoke seo.domain-whois --target openai.com

# Read an X/Twitter post
vernclaw-cli invoke read.x.post --url "https://x.com/user/status/123"

# Search YouTube videos
vernclaw-cli invoke search.youtube --query "AI agent workflows" --limit 5 --order date --region-code US

# Read YouTube video metadata; replace VIDEO_ID_HERE before running
vernclaw-cli invoke read.youtube.video --url "https://www.youtube.com/watch?v=VIDEO_ID_HERE"

# Search Product Hunt launches
vernclaw-cli invoke search.producthunt --query "AI agents" --limit 5

# Search the web or extract a URL
vernclaw-cli invoke search.web --query "Vernclaw connector CLI" --limit 5
vernclaw-cli invoke extract.url --url "https://vernclaw.com/connectors"

# Generate an image (async — returns a job ID)
vernclaw-cli invoke generate.image --prompt "sunset over mountains"
vernclaw-cli job get img_abc123

# Check account status
vernclaw-cli status

Output Contract

Connector success and provider responses are JSON-first: a compact JSON envelope with status and data is printed to stdout by default. Add --pretty to print human-readable terminal text instead. Local invoke parameter validation errors also return compact JSON by default. Error codes are exposed through the top-level errorCode field and, for API responses, the x-error-code header.

Connector output is optimized for agents: default invoke responses omit connector metadata, echoed input, provider names, and full upstream raw payloads. Metric tools return data.summary plus data.metrics; list tools return data.summary, data.stats, and data.items; trend tools return data.stats, data.metrics, and data.series; extract tools return data.document. Use vernclaw-cli list --json for structured catalog discovery.

Exit Codes
CodeMeaning
0Success
1Business rejection (e.g. insufficient credits)
2Authentication failure
3Invalid parameters
4Provider failure

Development

npm install
npm run build

Compiles src into dist.

Testing

npm test
VERNCLAW_E2E_RUN=1 VERNCLAW_E2E_API_KEY=your_key npx vitest run __tests__/e2e.production.test.ts
VERNCLAW_E2E_RUN=1 VERNCLAW_E2E_API_KEY=your_key pnpm test:e2e:cli:local
VERNCLAW_E2E_API_KEY=your_key pnpm test:e2e:cli:prod

Use VERNCLAW_E2E_RUN=1 together with VERNCLAW_E2E_API_KEY and optionally VERNCLAW_E2E_API_BASE_URL to enable the live e2e smoke test. pnpm test:e2e:cli:local assumes a local app is already running on http://127.0.0.1:3000, preferably via pnpm dev:connectors:local.

pnpm test:e2e:cli:prod now runs as a production success gate: it forces VERNCLAW_E2E_RUN=1, defaults VERNCLAW_E2E_EXPECT_SUCCESS=1, and fails fast when VERNCLAW_E2E_API_KEY is missing.

Publish / Deploy

npm pack --dry-run
npm publish

npm publish triggers prepack, which rebuilds dist before publishing. dist is treated as a generated publish artifact and is not tracked in git.

Links

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.