Meffecta Agent

An AI colleague that runs in your own Google Cloud, on your own jobs, against your own systems. It wakes on a schedule, a webhook, or an email, does a piece of real work, and reports back — then goes back to sleep costing nothing.

Work arrives finished, rather than waiting in a chat window for you to open it — though you can also just ask it something when you want to.

→ agent.meffecta.com

What it is, what you need, and the whole set-up in order. This package (@meffecta/agent) is the tool that stands one up and operates it.

What people run it for

A job is a page of plain-language instructions, so this is a sample rather than a menu — the agent does what your jobs say.

Sales — find prospects and check them against your CRM, research each company and its decision-maker, leave outreach drafts in the seller's own mailbox for them to send, and put a next step on every priority account.

Marketing — one weekly read across traffic, search, ads and campaigns. Website and search audits with fixes proposed. Ad reviews, where changes happen only on request. Watches form leads, contacts, and competitors' rankings.

Customer care — a support inbox that answers or hands over with the findings attached, learns from the conversations, and keeps help pages current as things change.

Compliance — review an ISO 27001 document set against the standard, find what is overdue or contradicts itself, and draft revisions for a person to approve — sized to your business rather than to a template's idea of one. It never records that a control is in place: that claim is what an audit tests.

Engineering — overnight error triage with fixes proposed as pull requests, a verdict on every proposed change, alerts traced to a likely cause, and weekly upkeep.

Leadership — a morning brief tailored to each person's role, daily status on what is live and in use, and weekly reviews that stay honest about flat weeks.

Assistant — email it anything: a lookup, a draft, a booking, a question. One calendar across Google and Microsoft 365. Inbox digests and the week ahead.

What it can reach

Shipped with the engine, pointed at your accounts by your jobs:

| | Reached out of the box | |---|---| | Mail & calendar | Gmail, Microsoft 365, Google Calendar | | Documents | Drive, Sheets, Docs, Slides | | Your numbers | GA4, Search Console, Google Ads, PostHog, Ahrefs | | Your data | BigQuery, Elasticsearch, MongoDB — and logs from Grafana or Coralogix | | The market | Google's live search results — real rankings, not a web search | | CRM | HubSpot, reading and writing as separate abilities | | Work & content | Linear issues and cycles; Webflow pages and CMS, staged before anything goes public | | Slack | Posts, threads and reactions — and answers when someone @-mentions it | | Infrastructure | Cloudflare, and a real headless browser for anything without an API | | Your code | any Git repo as the working directory, with pull requests as the output |

Anything else is a skill you add to your own repo — the engine never needs to know about it.

How it works

Your content repo holds the jobs, the facts about your business, and the register of which systems this deployment may touch. Every run clones it fresh. Push a changed prompt and the next run uses it; there is nothing to build and nothing to deploy.

Jobs are triggered by a schedule, a webhook, or an email to an address you name — and a job that runs out of time can hand the rest to a follow-up run of itself. Each job keeps its own memory across runs, and every prompt, result and transcript lands in a write-once audit bucket.

Built to be trusted with the keys

It runs in your GCP project, on your credentials, billed to your Claude subscription. Nothing routes through Meffecta.

A job reaches only the systems your register lists, and reading and changing are separate abilities — a reporting job loads the reader and never the writer.

One shipped skill exists to change a paid account, Google Ads, and it is the most constrained thing here: every change is validated against the live account first and only applied on a second, explicit run; budgets can only go down; a campaign can be paused but never deleted; and the limits live in the script, not in the instructions, so no wording can talk its way past them.

A job reachable by email must say who may reach it, or it refuses everyone — an omission is not consent. Secret values are never printed, by any command.

Operating it

npx @meffecta/agent help       # every command — each also takes --help
npx @meffecta/agent doctor     # the one to run when something feels wrong

Run commands from your content repo — the directory holding deployment.env, which says which project and service this deployment is, so a command can never act on the wrong one.

The version you install is the engine you deploy. Each release records the engine build published alongside it, and deploy defaults to that image, so tooling and engine cannot drift apart. meffecta-agent version tells you which pair you have.

Licence

UNLICENSED — for use by Meffecta deployments.