Skip to content
MEGA
Get your Blueprint
Proof

The first documented run

On 1 August 2026 a megamcp connector performed a real OAuth consent, a live read, and a confirmed write against a live HubSpot portal. This page is the record of that run: the actual scopes, timestamps, and activity log rows from production.

The consent asked for less than it could
The connector registry had four HubSpot scopes available: contacts read and write, companies read, and deals read. The tool list needed only contacts, so the OAuth consent requested only contacts. Companies and deals were never asked for. The grant is computed from the job, not from what the provider would allow.
Two tools, because two were needed
search_contactsreadautonomous

GET /crm/v3/objects/contacts. Runs without confirmation, because reading is what reads are.

create_contactwriteconfirm_mrtr

POST /crm/v3/objects/contacts, limited to three fields: email, first name, last name. Every call pauses on a preview and waits for a human.

Twenty-one seconds, three log rows

These are the three rows the run left in the production activity log, in order.

  1. 13:54:32 UTC
    search_contactsok

    The live read. Claude asked for contacts; the engine called the HubSpot API on the vaulted token and returned real CRM data.

  2. 13:54:52 UTC
    create_contactinput_required

    The pause. The write did not execute. The engine stored the exact arguments under confirmation c5702441 and returned a plain-language preview to approve or deny.

  3. 13:54:53 UTC
    create_contactok

    The approval, 1.17 seconds later. Same confirmation id, round trip 1. The engine executed the stored arguments, not resubmitted ones, and the contact existed in HubSpot.

The result in HubSpot: a real contact, mcp-e2e@megamcp.ai, record id 529732977371. In the log rows themselves the arguments read [redacted], because this connector stores field names only. That is the redaction control doing its job in the very log we are quoting.

What this run does not prove

  • It was our own HubSpot portal, run by the founder. No customer was involved, which is why no customer is quoted.
  • HubSpot is a famous system with a clean API. This run proves the engine, the consent flow, and the confirmed write. It does not prove build times for software we have never built before, which is exactly why the first 25 builds of software not already on file carry the launch guarantee: live in 5 business days or your first month is free.
  • The mapping for this run was authored by hand. The automated spec pipeline exists and gates every self-serve build, but it did not produce this connector, so this page does not claim it did.

Run the same twenty-one seconds on yours.

Name your software, describe the job, and see your Connector Blueprint before you pay anything.

Get your Blueprint