Terms of service

These terms are a contract between megamcp, operating from Boca Raton, Florida, United States, which operates megamcp ("we", "us", "megamcp"), and the person or organization that opens an account, buys a connector, or uses a connector URL ("you").

You accept these terms by creating an account, completing checkout, or using a connector. If you accept on behalf of a company, you confirm you are authorized to bind it, and "you" means that company.

The service is sold for business use to people who are at least 18 years old. It is not a consumer product and is not intended for personal or household use.

Done-for-you engagements booked through customconnectors.ai are separate work under a separate written agreement. These terms cover the self-serve megamcp product only.

You name a piece of software. We produce a connector document: a declarative mapping from that software's API to MCP tools, where each tool carries a classification, a safety mode, the fields it may touch, and a rate limit.

Every connector runs on one shared engine and is reached at a hosted URL of the form https://mcp.megamcp.ai/c/{connection id}. A connector is not custom code we run for you. The mapping schema is the boundary: it cannot express arbitrary computation, and it cannot reach hosts it does not name.

At runtime, a call from your AI client is authenticated, checked against your guardrails and rate limits, sent to the upstream API with the credential you supplied, and the result is returned to your client. We are the pipe and the guardrails. Your software remains the system of record.

A connector acts only when your AI client calls it. MCP connectors cannot react to events inside your software, ours included, so nothing in these terms promises event triggers, background jobs, or inbound webhooks from your systems.

Your subscription includes maintenance. Upstream APIs change and the MCP specification ships revisions on a schedule; we track both and ship the fixes centrally. That ongoing maintenance is the substance of what you are buying.

You are responsible for everything done under your account and through your connector URLs, including by your AI clients and by anyone you give a URL to. Treat a connector URL and its token like a password.

In Solo mode, one credential is used and anyone holding that URL acts as the connected account. In Team mode, each member connects their own upstream identity on their own connection, and each additional member connection is billed as a seat.

You supply the upstream credential or complete the upstream authorization grant. Credentials are encrypted at rest with AES-256-GCM, are never returned by any tool, and are decrypted server-side only. The current handling, including what we do not have yet, is described in full on the security page.

You can pause or revoke any connector or any member connection yourself at any time. Tell us promptly at support@megamcp.ai if you believe an account, a connector URL, or a credential has been compromised.

Every paid plan starts with a 14-day trial. No payment method is collected at checkout. If you add one before the trial ends, the paid subscription starts when the trial ends; if you do not, the subscription cancels at the end of the 14 days and the connector deactivates.

The trial includes a budget of 3 successful write calls. Read tools run live against your real system, and each write is previewed in plain language and executes only on your explicit approval. Once the budget is spent, write tools lock and reads keep working. Only writes that actually succeed count against the budget; a call the guardrails refuse does not.

Nothing is charged unless you add a payment method. If you added one and cancel before the trial ends, you are not charged.

One trial per connector. We may decline or shorten a trial where an account repeatedly re-trials the same software instead of subscribing.

Prices are the ones published on the pricing page at the time you check out, stated in US dollars and exclusive of any tax we are required to collect. At this version: Copilot (formerly Connector) is $79 per month or $790 per year, Autopilot (formerly Connector Pro) is $149 per month or $1,490 per year, and each additional Team connection is $19 per month or $190 per year.

Volume pricing applies automatically in two steps. From your third live connector onward, new standard-tier checkouts use $59 per month or $590 per year. From your fifth live standard connector, every standard subscription on the account moves to that same rate at its next billing cycle, with no proration; five connectors therefore come to $295 per month. Autopilot is not volume priced. Reductions are never reversed automatically: if you later drop below five, the connectors you keep stay at the lower rate.

Subscriptions renew automatically for the same interval until cancelled, charged to the payment method on file. Payment is processed by Stripe. We do not receive or store your full card details.

We may change prices. A change takes effect for you at your next renewal after we tell you, and you are free to cancel before that renewal.

The guarantee as offered: for the first 25 builds of software we do not already have on file, your connector is live and passing its own test panel within 5 business days, or your first month is free.

It covers builds of software that does not already carry a ready, production-verified spec or mapping in our index. Systems already on file deploy in minutes and are not covered, because they do not need it. Comped pilot builds are not covered and do not consume the 25.

It is conditional on you. Provide the credentials we ask for and answer build questions within one business day. The 5-day clock runs only while we have what we need from you, and pauses while we do not.

The remedy is that we extend the trial or credit your account so you are not billed for time before the connector was live. That extension or credit is the entire remedy under this guarantee. It is not a refund of other charges and not a claim for damages.

It does not apply where the software has no accessible API, blocks programmatic access, requires a bespoke engagement, or where the upstream vendor refuses, restricts, or revokes access.

The 25-build cap is a measurement window, not a countdown. When it closes we publish what we measured, and the guarantee stated on the pricing page at that time governs new builds from then on.

You can cancel at any time from the billing portal in your dashboard. Cancellation takes effect at the end of the current billing period, and we do not prorate a partial period.

Fees already paid are non-refundable, except where the launch guarantee applies or where the law requires a refund.

If a payment fails, our payment processor retries it. During those retries the connector keeps serving reads and writes are paused. If the retries run out, the connector stops serving.

A subscription cancelled for non-payment is treated as a lapse rather than a departure: we pause the connector and keep the stored material so support can restore your access instead of destroying it over an expired card. Nothing serves while it is parked. Email support@megamcp.ai to bring it back.

Pausing is not cancelling. Pausing stops every connection instantly and keeps your configuration, but it does not change your subscription and billing continues until you cancel.

When a cancellation takes effect, or on trial expiry or revocation, connector URLs deactivate and the stored upstream credentials for that connector are destroyed. The delete is a hard delete, not a soft delete.

We do not call your provider to revoke an authorization grant. Destroying our copy of a token stops it working here; to end the grant itself, remove megamcp's access in that provider's own account settings. The same applies per member: revoking one connection destroys that person's stored credential and touches nobody else.

Activity log rows survive cancellation. There is no export and no scheduled purge yet, so those rows remain until we build both. This is stated the same way on the security page and will be updated in both places when it changes.

This is the clause that matters most, so it is said plainly: connecting a piece of software to megamcp does not transfer your obligations to that software's vendor.

You confirm that you have the right to connect that software, to authorize access with the credential you supply, and to allow an AI client to read and, under the guardrails you control, write through that access.

You are responsible for complying with the upstream vendor's terms of service, API terms, developer policies, rate limits, and data policies, including any restriction on automated access, on data extraction, and on resale. We do not review those terms on your behalf and we are not a party to them.

We are independent of the vendors we connect to unless a specific page says otherwise. We are not affiliated with, endorsed by, or sponsored by them. Their names and marks belong to them and are used only to describe what a connector connects to.

If a vendor blocks, restricts, or withdraws access, or changes an API in a way we cannot map safely, we may have to change or disable your connector. Section 12 covers changes of that kind.

You are responsible for what your AI does with the access you allow: the tools you leave on, the fields you allow, the previews you approve, and any autonomous mode you unlock.

Use the service for legitimate work on systems you are entitled to access. Specifically, you agree not to do any of the following.

Systems that hold protected health information, consumer financial records, or similar regulated data are not available self-serve at this version. We try to detect them at intake and route you to a compliance conversation with our done-for-you team, where a business associate agreement and the appropriate infrastructure commitments are handled per engagement.

Detection is a control, not a guarantee. You must not enter regulated data into a self-serve connector regardless of what intake did or did not flag, and you are responsible if you do.

These terms create no business associate relationship and no obligation on us to hold regulated data. A data processing agreement and the current subprocessor list are available on request.

Maintenance is the product, and maintenance means change. We may update a mapping, rename or reshape a tool, change a default, tighten a classification, or disable a tool in order to keep a connector safe or working when an upstream system changes.

We upgrade the shared engine to new MCP specification versions centrally, and your connector comes along with it. That currency is part of what the subscription buys.

We may add, change, or remove features. We will not intentionally remove a capability you are paying for without telling you. If we do remove one, you may cancel and section 7 applies.

The service is provided as is and as available. At this version there is no service level agreement and no uptime commitment. If we publish one later, it will be a separate document that says so.

We do not warrant that the service will be uninterrupted, timely, secure, or error free; that a connector will cover every capability of an upstream API; or that an automatically built mapping is complete or free of misclassification.

We do not warrant that any upstream vendor will keep their API stable or available, or that they will allow your connection to continue.

We do not warrant the behaviour or the output of your AI client. A confirmation preview is a control that puts a human in the loop before a write reaches your system; it is not a promise that the proposed call is correct. Read previews before you approve them.

To the fullest extent the law allows, we disclaim all implied warranties, including merchantability, fitness for a particular purpose, title, and non-infringement.

Neither party is liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, or loss of goodwill, even if that party was told such damages were possible.

Our total liability for all claims relating to the service is limited to the greater of the fees you paid us in the twelve months before the event giving rise to the claim, and one hundred US dollars.

These limits do not apply where the law does not permit them. Where a jurisdiction disallows an exclusion, that exclusion applies as far as it lawfully can and the rest of this section stands.

The price of this service assumes this allocation of risk. It is part of the bargain, not fine print.

You will defend and indemnify us against third-party claims arising from your use of the service, the data you send through it, your breach of these terms, your breach of an upstream vendor's terms, and any regulated data you introduce into a self-serve connector.

We will tell you promptly about any such claim, let you control the defense, and not settle it without your consent.

We may suspend or terminate a connector or an account immediately if fees go unpaid, if section 10 is breached, if there is a security risk to you, to us, or to an upstream system, if the law or a court requires it, or if an upstream vendor requires us to stop.

Where it is practical and not itself a security or legal risk, we will tell you first and give you a chance to fix the problem.

You can terminate at any time by cancelling. Section 8 describes what happens to URLs, credentials, and logs.

Sections that should outlive the agreement do: fees already owed, acceptable use, your responsibility for upstream terms, the disclaimers, the liability limits, indemnity, and the governing law and disputes sections.

You keep ownership of your data. We use it to operate the service, support you, and keep it secure, and for nothing else. We do not sell it, and we do not use your business data or the contents of your tool calls to train machine learning models.

We do not store the data your systems return through a connector. The activity log records the call rather than the response: who, what, when, and result, with tool arguments recorded at the redaction level you choose (full arguments, field names only, or hashes).

The activity log is append-only by construction. The application role holds insert and select and nothing else, and the database refuses updates, deletes, and truncates.

Log content is not copied into any analytics pipeline, internal or third party. Storage is single-region at this version. Each connector carries a retention setting, but it is currently recorded rather than enforced, because the scheduled purge is not built yet.

We treat your connector configuration, your credentials, and your logs as confidential and disclose them only to the subprocessors that operate the service, or where the law requires. You agree to treat non-public information we give you about the platform as confidential.

We may update these terms. The current version always lives at www.megamcp.ai/terms with the date it took effect.

For a material change we will tell you by email to your account address or in the dashboard before it takes effect. Continuing to use the service after that date is acceptance. If you do not accept, cancel before then.

These terms are governed by the laws of the State of Florida, United States, without regard to its conflict of law rules. the state and federal courts in Palm Beach County, Florida have exclusive jurisdiction over any dispute, and both parties consent to that venue.

Before filing anything, email support@megamcp.ai with the details and give us 30 days to work it out. Most disputes end there.

These terms, together with any order form or written agreement we sign with you, are the entire agreement about the service and replace earlier discussions. Where a signed agreement conflicts with these terms, the signed agreement wins.

A delay in enforcing a right is not a waiver of it. If a provision is unenforceable, the rest stands and that provision is enforced as far as it lawfully can be.

We may assign these terms to a successor in a merger, acquisition, or sale of assets. You may not assign them without our written consent.

Neither party is liable for a delay or failure caused by events beyond its reasonable control, including upstream vendor outages and hosting platform outages.

Notices to you go to the email address on your account. Notices to us go to support@megamcp.ai and to 160 W. Camino Real, Unit #559, Boca Raton, FL 33432, United States.

The parties are independent contractors. Nothing here creates a partnership, an agency, or an employment relationship.

You confirm that you are not subject to sanctions that would prohibit this service, and that you will not use it where the law forbids it.