leads
Used to define and run continuous integration (CI) workflows and to schedule the agent to run autonomously via dedicated workflow files.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
agent-harness
A production-minded harness for AI coding agents and LLM features.
Getting a model to answer is easy. Getting it to behave inside a real codebase and a real product is the engineering work: what context it gets, which actions it may take, how its output is checked, and what happens when it is wrong. This repository is a working, tested reference for that layer.
What is inside
Area | Where | What it shows |
Project rules | Short, always-loaded instructions; details pushed to skills | |
Hooks |
| |
Subagents | Independent | |
Skills | Step-by-step procedures loaded on demand: structured output, new native integration, review loop | |
Permissions | Read-only tools pre-approved, shared-state writes always ask, secrets denied | |
MCP server | Lead-funnel tools with input/output schemas, | |
Structured output | Zod schema → JSON Schema → validated typed result, with a short repair turn on failure | |
Guardrails | PII redaction, prompt-injection screening, untrusted-content quoting, action allowlist and approval policy | |
Native integrations | HTTP client with token bucket rate limit, retries with backoff and jitter, | |
Scheduled agent | The same harness run headless every week, reporting through an issue |
Architecture and the reasoning behind each choice: docs/architecture.md.
Related MCP server: GoHighLevel MCP Server
Quick start
npm install
npm run test # 57 tests, no network
npm run example # inbound message -> typed decision, offline with a mock model
npm run mcp:dev # start the MCP server on stdioWith ANTHROPIC_API_KEY and HARNESS_MODEL set (see .env.example), the
example calls the real model through the same code path.
Open the folder in Claude Code and the harness is active: hooks run on every
tool call, the leads MCP server is available, and the skills and subagents
are listed.
Example: untrusted text to a safe action
const Decision = z.object({
intent: z.enum(["purchase", "support", "pricing", "cancel", "other"]),
confidence: z.number().min(0).max(1),
action: z.enum(["move_to_qualified", "open_ticket", "send_price_table", "handoff_to_human", "none"]),
reply: z.string().max(280),
});
const { text } = redactPII(message);
const result = await generateStructured({
provider,
schema: Decision,
instructions: "Triage inbound sales messages and pick one next action.",
input: quoteUntrusted("whatsapp", text),
});
if (result.ok) {
const verdict = checkAction(policy, result.data.action); // allow | approve | deny
}The result is a typed object or a typed failure, never free text, so a queue worker or an API handler can consume it directly.
Design principles
Enforce, do not ask. Rules that matter live in hooks and permissions, not only in the prompt.
Small base context. Always-loaded instructions stay short; procedures load as skills when needed.
Independent review. The agent that wrote a change does not approve it.
Schemas at every boundary. Model output and external API responses are validated where they enter the system.
The model proposes, code decides. Side effects go through a policy.
Deterministic tests. Time, randomness,
fetchand the model are injected; the suite runs offline in about a second.
Stack
TypeScript (strict, ESM) · Node.js 20+ · Zod 4 · Model Context Protocol SDK · Vitest · GitHub Actions.
Author
Leandro Silva Ferreira Junior · LinkedIn
Fictitious data only. MIT license.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Lets AI agents get leads on the phone: call, send SMS, and schedule callbacks for sales teams.
B2B lead finding, company enrichment, email discovery and funding tracking as 10 agent tools.
Read-only sales CRM for AI clients: leads, pipeline, AI-agent chats, calls, ad attribution.
Agent-native CRM. 25 tools — contacts, deals, sequences, enrichment waterfall, audit log.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides AI agents with tools for structuring and auditing cold outreach messages, building follow-up sequences, handling replies, and detecting red flags.740 npmMIT
- AlicenseBqualityDmaintenanceEnables LLM agents to operate a CRM through 114 typed tools across 24 modules, covering contacts, pipelines, calendars, messaging, invoicing, and payments. Destructive and outward-facing actions are annotated for visibility and approval.114MIT
- AlicenseNot gradedqualityCmaintenanceEnables a language model to safely query internal services through a closed set of read-only, schema-validated tools, with full auditing and refusal logging.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI clients to discover and invoke business tools for identifying inactive customers, searching internal knowledge, drafting follow-ups, and creating sales tasks.-