Terms

These terms govern your purchase of the Claude Desktop Cavalry MCP (“CavalryMCP”) and your right to use it. They are written in plain English on purpose: you should be able to read them once and know exactly what you get and what you may do with it. This store is operated from Germany.
Dies sind die Allgemeinen Geschäfts- und Lizenzbedingungen (AGB) für CavalryMCP. Sie sind auf Englisch verfasst, da sich dieses Angebot überwiegend an ein internationales, englischsprachiges Publikum richtet; Englisch ist damit auch die Vertragssprache.

1. Who you are dealing with

CavalryMCP and this store are provided by:

Referred to below as “I”, “me” or “my”. “You” means the person buying or using CavalryMCP. See also the Impressum.

Payments are handled by Dodo Payments as the merchant of record. Dodo Payments acts as my reseller: it sells CavalryMCP to you in its own name, collects the money and takes care of sales tax and VAT worldwide. Your purchase contract for the payment is therefore concluded with Dodo Payments and is additionally subject to their buyer terms. Those terms put it the same way: you purchase the product from Dodo Payments, but the product is licensed to you by me.

The license to actually use the software — sections 6 to 8 below — is granted to you directly by me. So: Dodo Payments handles the money, I make the software and stand behind it. Everything in these terms that concerns the software, the money-back guarantee and support is a commitment from me to you, and you can always come to me first.

This split describes who does what. It does not divide up your rights: nothing in these terms decides, limits or shifts which of us you can bring a statutory claim against, and you do not lose a claim because this page describes our roles in a particular way. See section 12.

2. What you are buying

You are buying a license to use CavalryMCP, an MCP (Model Context Protocol) server for the Claude Desktop app that installs a small bridge script inside the third-party animation application Cavalry. CavalryMCP is digital content: it is delivered as a download, not on a physical medium, and it is licensed to you rather than sold to you as a piece of property.

What CavalryMCP does, what it needs in order to run, and where its limits are is described on the product page — including a “Known Limitations” section. That description is the information I give you about the product before you buy it, and it is what I am aiming to deliver. I put the limitations in front of you rather than leaving you to discover them afterwards.

In particular: CavalryMCP hands prompts and scene data to Claude, a large language model, and lets it run generated code inside your Cavalry project. Its output is probabilistic and depends on your prompts, your project and the model behind it — I cannot promise a particular result, that Claude will use a particular feature correctly, or that a given prompt will produce what you had in mind. That is not a corner case; it is how the product works, and the product page explains it before you buy.

To be clear about what that does and does not mean: telling you about a limitation is information, not a waiver. German law lets a digital product fall short of the standard you could otherwise expect only if you were told about that specific point beforehand and agreed to that specific deviation expressly and separately (§ 327h BGB). Unless such an agreement was actually made, the ordinary statutory standard applies on top of my description, and section 12 says what happens if something is genuinely wrong.

You need a working installation of Cavalry and of Claude Desktop, together with an active Claude subscription or other access to Claude Desktop's model features, to use CavalryMCP. Cavalry, Claude Desktop and the underlying Claude models are not mine and I have no influence over them; see section 14. CavalryMCP does not include a Cavalry license, a Claude subscription, or any API credit — you obtain and pay for those separately, directly from their respective providers.

To buy, you must be legally able to enter into this purchase under the law that applies to you. If you are a minor, you may only buy CavalryMCP with whatever consent that law requires — in Germany, that of the people with parental responsibility for you.

3. How a purchase comes about

The presentation of CavalryMCP on this website is an invitation to you to make an offer, not yet a binding offer from me. The purchase itself is concluded with Dodo Payments, through their checkout, and it is their checkout that tells you the steps for placing your order and when it becomes binding. Once the purchase has gone through, you get your download link by email, and the license in section 6 is yours.

Before you pay, you will see the product, the total price and the tax included in it in the checkout, and you can correct your entries there.

As the seller, Dodo Payments sends you the confirmation of the contract together with your receipt by email. That email is your copy of the contract on a durable medium and your proof of purchase — please keep it, together with the email containing your download link. If you ever need it again, write to info@splines.me and I will help you get it back.

4. Price, taxes and payment

The price on the product page is quoted in euro and is a gross price — it already includes the VAT or sales tax due in your country, and that amount is shown separately in the checkout and on your receipt. There are no shipping or handling costs, because CavalryMCP is a download.

The binding total is the one shown in the checkout before you pay. If you choose a currency other than euro there, Dodo Payments converts the amount at its own rate and may add a currency-conversion fee, so the figure can differ slightly from the euro price on the product page. Your own bank or card issuer may charge a foreign-transaction fee on top of that; both of these are outside my control. You always see the final amount before you confirm the payment.

Dodo Payments collects and remits the tax and issues your receipt or invoice. The available payment methods are the ones offered in the checkout. If a payment is reversed or charged back through no fault of mine, the license granted in section 6 is suspended until the payment is settled.

5. Delivery

After a successful payment you receive an email with a download link for CavalryMCP, normally within a few minutes. The download is an .mcpb file (MCP Bundle) for Claude Desktop. Installation instructions are on the product page and in the email.

The download link is personal to you. If the email does not arrive, please check your spam folder first and then write to info@splines.me — I will send you a new one.

6. Your license: what you may do

Once you have paid, I grant you a perpetual (i.e. not time-limited), worldwide, non-exclusive license to use CavalryMCP, personal to you and subject to these terms:

• One license, one person. A license is for a single named user: you. You may install and use CavalryMCP on as many devices as you personally work on (for example your desktop and your laptop), as long as you are the only person using it.
• Teams need one license per person. If several people in a studio, company or institution use CavalryMCP, each of them needs their own license. Shared machines used by several people also need a license for each person using CavalryMCP on them.
• Commercial use is included. You may use CavalryMCP in paid, commercial and client work, without any extra fee or royalty. I do not claim any rights in your project files or other output you create using CavalryMCP — scenes, animations, code you have Claude generate for your project. Any rights in such output are determined by applicable law and, where relevant, the terms of the third-party services you use, such as Anthropic's terms for Claude.
• Backups. You may make copies for your own backup and archiving purposes.

All rights in CavalryMCP itself, including copyright, remain with me and with the authors of the open-source and third-party components in section 8. You get the rights listed here; rights not granted are reserved.

7. What you may not do

Please do not do any of the following, and please do not help others to do it:

• No sharing. Do not pass CavalryMCP, your download link or your purchase confirmation to anyone else, do not upload it to a public or shared location, and do not make it available to third parties — not as a download, not on a network share, not in a repository, not through a rental, lending or “software as a service” arrangement. (Handing your own copy on for good is a different thing; see the third point below.)
• No reselling or redistribution. Do not sell, sublicense, redistribute or bundle CavalryMCP or parts of it, whether on its own, in a collection, or as part of another product, and whether for money or for free — again, other than the complete, one-off handover described below.
• No passing it around. Your license is meant for you, so please do not lend it out, run it on someone else’s behalf, or split it between several people.
  Nothing here is meant to block a handover that mandatory law allows you to make anyway — and for perpetual software licenses bought outright, the law sometimes does. If you are entitled to pass your license on, then please do it properly: hand over the whole thing rather than a copy of it, make sure the other person accepts these terms, and stop using CavalryMCP and delete every copy you still have. What is not allowed is keeping a copy for yourself, handing out your personal download link, or turning one license into two.
• No removing of notices. Do not remove or obscure copyright notices, license texts or author attributions contained in CavalryMCP or its files.
• No circumvention. Do not bypass or disable any technical limitation, license check or protective measure in CavalryMCP, except where the law expressly permits it (see section 7.1).
• No unlawful use. Do not use CavalryMCP in breach of applicable law, or in breach of the terms of the third-party services described in section 14 — including Anthropic's and Scene Group's own usage policies for Claude and Cavalry.

7.1 Reverse engineering

Except where the law expressly allows it, you may not decompile, disassemble or otherwise reverse-engineer CavalryMCP, reconstruct its source code, or modify it in order to pass the result on to others.

The law allows quite a lot, though, and I am not trying to take any of it away from you. Whatever the sentence above might suggest, you keep at least these rights:

• making a backup copy where that is necessary to secure your future use (§ 69d (2) UrhG);
• observing, studying and testing how CavalryMCP works in order to work out the ideas and principles behind it, while you load, display, run, transmit or store it as you are entitled to (§ 69d (3) UrhG);
• decompiling it where that is indispensable to make it work together with other programs (§ 69e UrhG);
• the acts necessary to use it as intended, including correcting errors (§ 69d (1) UrhG).

The first three are not mine to take away: under § 69g (2) UrhG a contractual provision conflicting with § 69d (2), § 69d (3) or § 69e is void, so if any wording on this page ever read that way, the statutory rule wins. The last one works a little differently: § 69d (1) applies unless something specific has been agreed to the contrary — and nothing here is meant to be that, so you keep it too. The same goes for any right under the law applying to you that cannot lawfully be excluded, and the open-source and third-party components in section 8 carry their own, broader permissions.

8. Bundled third-party content

The download contains two kinds of content that are not my own work, bundled so that Claude can look things up about Cavalry without a network round trip for every question. Both are listed, with their attribution and license texts, in THIRD-PARTY-NOTICES.txt, included with the download.

• Open-source components, such as TypeScript type definitions for the Cavalry scripting API (@scenery/cavalry-types, MIT licensed), used to build the MCP server and to let Claude look up exact API signatures. These remain under their own licenses, reproduced in full in THIRD-PARTY-NOTICES.txt.
• Cavalry’s own user documentation. CavalryMCP bundles a converted (HTML-to-Markdown) copy of Cavalry’s public documentation from cavalry.studio/docs, so that Claude can search and read it offline. That documentation is not my work; it remains the copyrighted content of Scene Group Ltd, the maker of Cavalry, reproduced here only to let CavalryMCP describe Cavalry’s own interface and scripting API accurately. I claim no ownership in it, and CavalryMCP is not affiliated with, endorsed by or sponsored by Scene Group Ltd; see section 14.

Where an open-source license grants you more rights in a component than these terms do — for example the right to copy, modify or redistribute that component on its own — that license governs for that component. So section 7 restricts my own work and CavalryMCP as a package, but it does not reach into what a third-party license already allows you to do with that component. The bundled Cavalry documentation is not licensed to you by me at all: your right to it, if any, comes from your own relationship with Scene Group Ltd, such as your Cavalry license or your access to their public docs site, not from your CavalryMCP purchase.

9. Updates and lifetime upgrades

New versions are announced on the product page. Installing an update is your decision. An update may change an individual feature where there is a good reason for it — keeping CavalryMCP working, secure, or compatible with the software around it — and I will try my best to keep things backwards-compatible.

Three honest limits on this promise, please read them carefully:

• “Lifetime” describes the update policy, not a service guarantee. It means that whenever I release a new version of CavalryMCP, you receive it at no extra cost, for as long as I keep developing and commercially offering the product. It is a promise about the price of future versions, not a promise that a new version will ship on any particular schedule, or at all in a given period. If I ever stop working on CavalryMCP entirely, your license to the versions you already have remains in effect permanently — you simply stop receiving new ones, and there is no refund of the purchase price for that.
• An update does not guarantee compatibility with newer Cavalry or Claude Desktop releases. CavalryMCP runs inside two pieces of third-party software that I do not control: Cavalry and Claude Desktop (including the Claude models it uses). Both are updated on their own schedules, and either of them can change its scripting API, extension format or behavior in a way that breaks CavalryMCP. Getting free updates means that when I ship a fix or a new version, it is yours at no extra cost — it does not by itself mean that CavalryMCP already works, or will keep working, with whichever version of Cavalry or Claude Desktop you happen to be running at a given moment.
• What I actually commit to. While I am actively developing and commercially offering CavalryMCP, I intend to track new Cavalry and Claude Desktop releases and to release compatible updates where I can. This is a statement of intent, not a contractual promise of a particular response time or outcome: I cannot control if, when or how those third parties change their software, and I may discontinue development of CavalryMCP at any time as described above.

My statutory obligation to supply the updates needed to keep the product in conformity with the contract (§ 327f BGB) remains unaffected by all of this.

10. 14-day money-back guarantee

This is a voluntary guarantee I give you on top of your statutory rights — it does not limit them in any way, and sections 11 and 12 apply regardless of it. It is a separate promise, not a restatement of the statutory right of withdrawal: it applies whether or not you still have that right, and none of the conditions in section 11 have to be met for you to use it. The details:

• Send your request to info@splines.me from the email address you used at checkout, or include your order number. A sentence is enough.
• The 14 days start on the day of purchase. I will confirm your request and issue the refund through Dodo Payments, normally within a few working days; the money goes back to the payment method you used, including the tax you paid.
• With the refund, your license ends. Please delete CavalryMCP and any copies of it, and stop using it. Anything you already created with it stays yours — you do not have to undo your own work.
• The guarantee covers one refund per person. It is meant for people who genuinely tried the product and decided against it, not for buying, refunding and buying again. I may decline a repeat request or an obviously abusive one.

11. Your statutory right of withdrawal

If you are a consumer in the EU, you normally have a statutory right to withdraw from a distance contract within 14 days without giving reasons. For paid digital content that is not supplied on a physical medium, that right can end early — but only if all four of the following actually happened (§ 356 (6) no. 2 BGB):

1. performance of the contract has begun;
2. you expressly agreed that it should begin before the withdrawal period is up;
3. you confirmed that you know you lose your right of withdrawal by agreeing to that; and
4. you were given the confirmation of the contract on a durable medium, such as the confirmation email (§ 312f BGB).

Downloading on its own is not enough: if any one of those four steps was missing, the right does not expire early. The law decides that, not this page.

Because Dodo Payments is the seller in the payment contract, the withdrawal information, and anything you are asked to agree to, comes from them — in their checkout and in their buyer terms. Whether those steps add up to what § 356 (6) requires is for the law to judge, and I am not going to certify it here on their behalf. So if you are ever unsure whether your right of withdrawal is still open, assume it is. If you want to withdraw, address it to the seller named in your order confirmation; you can also write to info@splines.me and I will pass it on and help sort it out.

In practice you do not need to work out which of these applies to you. The statutory right of withdrawal and the money-back guarantee in section 10 are two separate things, and the guarantee is mine to give: it runs for 14 days from your purchase, on its own terms, whether or not you still have a statutory right of withdrawal at that moment. So you have a full two weeks to change your mind either way.

12. Defects and statutory rights

The statutory rules on defects apply — for consumers, the rules on digital products in §§ 327 ff. BGB. If CavalryMCP does not work as it should, you have the statutory remedies, and nothing in these terms takes them away, shortens them or makes them harder to use.

Because Dodo Payments sells to you and I license and build the software, the two of us carry different obligations towards you. Which claim you have against whom is a question the law answers, and I am deliberately not answering it here.

That said, please just write to me at info@splines.me first. I wrote the software, I am the one who can fix it, and I would much rather send you a working version than have you go through a support queue. That is a request, not a hurdle: you never have to contact me before exercising a statutory right, and not contacting me costs you nothing.

One thing to keep in mind when judging whether something is actually broken: CavalryMCP is a specialized tool built around a large language model, and the limitations described on its product page (see section 2) — including that outputs are probabilistic and not guaranteed to match what you asked for — are part of what it is, not surprises that appeared later. The same goes for Cavalry or Claude Desktop changing underneath it — section 9 says what I will do about that.

That is not me declaring those cases defect-free. I cannot decide what counts as a defect just by writing it on this page. All I am saying is that the product description is what I promised you, so it is the measure of whether CavalryMCP works as it should.

13. Support

I am happy to help. You can reach me at info@splines.me, and there is a comment section on the product page. I usually answer, but I am one person doing this next to other work, so support is offered as a courtesy: apart from my statutory obligations under section 12 and my update commitment under section 9, there is no contractual entitlement to support, to a particular response time, or to individual feature requests being implemented.

14. Third-party software and services

CavalryMCP runs as an extension for Claude Desktop, a product of Anthropic, and installs a bridge script inside Cavalry, an application by Scene Group Ltd. Using CavalryMCP means sending parts of your project and prompts to Claude, which processes them under Anthropic's own terms and policies. Claude Desktop, the underlying Claude models, and Cavalry are independent third-party offerings. This project is not affiliated with, endorsed by or sponsored by Anthropic or Scene Group Ltd; their names and trademarks belong to their respective owners and are used here only to describe compatibility. Section 8 covers the Cavalry documentation content bundled with the download.

I have no influence over those third parties, their terms, their availability, their pricing, or the behavior or output of their software, and I am not responsible for the operation, availability, pricing, terms or behavior of those third-party products and services themselves. When you use them through CavalryMCP, their own terms and privacy notices apply, and you use them at your own risk. If one of them changes in a way that breaks compatibility, section 9 applies. This does not affect my own obligations under these terms, including section 12.

What happens to your data on this website is described in the privacy policy. What happens to your project data and prompts once CavalryMCP sends them to Claude is governed by Anthropic's own privacy policy and terms, not by me.

15. Liability

I am liable without limitation wherever the law says liability cannot be limited — in particular for damages arising from injury to life, body or health, for damages caused intentionally or by gross negligence, where I have given a guarantee or fraudulently concealed a defect, and under the German Product Liability Act (Produkthaftungsgesetz) to the extent that it applies.

In cases of slight negligence, I am liable only for the breach of an obligation whose fulfillment is essential to the proper performance of the contract and on whose observance you may regularly rely (a "cardinal obligation"). In that case, liability is limited to the damage that was foreseeable and typical for this kind of contract at the time it was concluded. Any further liability is excluded.

In particular, and to the extent permitted by the limits above: I am not liable for the content that Claude generates or the code it executes in your Cavalry project through CavalryMCP. Claude's output is not authored or reviewed by me before it reaches you, and you remain in control of and responsible for reviewing and applying it — the product is designed so that you stay in the loop rather than have code run without your knowledge.

Liability for the loss of data is limited to the effort that would have been needed to restore it if you had backed it up regularly and in a way appropriate to its importance. Please do keep backups of your Cavalry projects, especially before letting Claude modify them.

The same limits apply to anyone acting on my behalf in performing this contract. They do not affect your statutory rights in respect of defects (section 12) or the guarantee in section 10, and they do not apply to the extent that liability cannot legally be limited.

16. How long the license lasts

Your license is permanent. It does not expire, it does not need renewing, and I cannot take it away from you because I changed my mind.

I may only end it for good cause — that is, if you seriously or repeatedly breach section 7 (for example by distributing CavalryMCP) and do not stop after I have asked you to and given you a reasonable deadline. Advance warning is not needed only where the breach is so serious that waiting cannot reasonably be expected of me, for example where you are publishing the software. The license also ends if you use the money-back guarantee (section 10) or withdraw from the contract, and it is suspended for as long as a payment of yours has been charged back and not settled (section 4).

If the license ends, you must stop using CavalryMCP and delete your copies of it. Work you already created with it remains yours and unaffected. You can end the license yourself at any time by deleting the software; there is no refund for that beyond section 10.

17. Your feedback

If you send me ideas, bug reports or suggestions, I may use them to improve the product without owing you a fee or an attribution — that is simply how a bug report becomes a fix. You keep every right you have in what you sent, I claim no exclusive rights in it, and I will not publish your name or your message without asking you first.

18. Changes to these terms

The version of these terms that you accepted at checkout is the version that governs your purchase. I may change these terms at any time for future purchases, but a later version does not apply retroactively to what you have already bought: the license you hold for the versions of CavalryMCP you already have keeps the terms you agreed to, and your continued use of them is not treated as consent to anything new. The date at the bottom of this page tells you when this text last changed.

A new version of CavalryMCP may come with new terms. The lifetime-upgrade promise in section 9 gives you future versions at no extra cost; it does not freeze this text forever. But new terms never arrive silently and never reach back: if a future version is offered under different terms, I will say so and make those terms available to you before you install it, and whether they end up applying to you is settled by whatever the download or installation process asks of you at the time. Installing is always your decision (section 9) — if you do not like the new terms, keep the version you have, which stays yours under the terms you accepted. Whatever such terms say, they cannot cut into rights the law does not let me take away.

19. Applicable law and disputes

German law applies, excluding the UN Convention on Contracts for the International Sale of Goods. If you are a consumer with your habitual residence in another country, this choice of law does not deprive you of the protection of the mandatory consumer provisions of that country: whatever your own law guarantees you, you keep.

There is no special agreement on the place of jurisdiction for consumers; the statutory rules apply. If you are a merchant, a legal entity under public law or a special fund under public law, and the statutory requirements for agreeing on a venue are met, the place of jurisdiction is Heidelberg, Germany.

I am not willing to participate in dispute resolution proceedings before a consumer arbitration board (Verbraucherschlichtungsstelle), and I am not obliged to be: I employ ten or fewer people, so § 36 (3) VSBG exempts me from the general information duty in § 36 (1) no. 1 VSBG. Any statutory duty to inform you once a specific dispute has actually arisen (§ 37 VSBG) is unaffected, and I will comply with it. In the meantime, if something goes wrong, please write to info@splines.me — in a shop this small, an email genuinely is the fastest route to a solution.

20. Final provisions

What CavalryMCP is contractually meant to be and do is set out in these terms, in the product information shown to you before you buy, and in the license texts included with the download. That is not an exhaustive list that lets me disown everything else I have said: what I state publicly about the product, in advertising or anywhere else, counts too, exactly as the law provides. Your payment contract with Dodo Payments is additionally subject to their terms.

If any provision of these terms is or becomes invalid, the rest remains in force. The invalid provision is replaced by the statutory rules.

And the catch-all behind everything above: no sentence on this page is meant to exclude a right that cannot legally be excluded. If one accidentally reads that way, treat it as not written and the law as controlling.

Questions about these terms? Write to info@splines.me.

Last updated: September 20, 2026