Skip to content

feat(printr): add printr plugin v0.16.0 #447

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
alanrsoares wants to merge 1 commit into
base: main
Choose a base branch
from
+457 −0
Draft

feat(printr): add printr plugin v0.16.0 #447

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions skills/printr/.claude-plugin/plugin.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
{
"name": "printr",
"description": "Token launchpad built for holders. Deploy, fund, sign, stake, and graduate tokens across EVM chains and Solana via the Printr MCP server.",
"version": "0.16.0",
"author": {
"name": "PrintrFi",
"email": "alan.s@printr.money"
},
"homepage": "https://printr.money",
"repository": "https://github.com/PrintrFi/printr-mcp",
"license": "Apache-2.0",
"keywords": [
"token-launch",
"launchpad",
"solana",
"evm",
"base",
"cross-chain",
"mcp"
]
}
183 changes: 183 additions & 0 deletions skills/printr/LICENSE
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,183 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.

"Work" shall mean the work of authorship made available under
the License, as indicated by a copyright notice that is included in
or attached to the work (an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and derivative works thereof.

"Contribution" shall mean, as submitted to the Licensor for inclusion
in the Work by the copyright owner or by an individual or Legal Entity
authorized to submit on behalf of the copyright owner. For the purposes
of this definition, "submitted" means any form of electronic, verbal,
or written communication sent to the Licensor or its representatives,
including but not limited to communication on electronic mailing lists,
source code control systems, and issue tracking systems that are managed
by, or on behalf of, the Licensor for the purpose of discussing and
improving the Work, but excluding communication that is conspicuously
marked or otherwise designated in writing by the copyright owner as
"Not a Contribution."

"Contributor" shall mean Licensor and any Legal Entity on behalf of
whom a Contribution has been received by the Licensor and subsequently
incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a cross-claim
or counterclaim in a lawsuit) alleging that the Work or any Contribution
embodied within the Work constitutes direct or contributory patent
infringement, then any patent licenses granted to You under this License
for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:

(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its
distribution, You must include a readable copy of the
attribution notices contained within such NOTICE file, in
at least one of the following places: within a NOTICE text
file distributed as part of the Derivative Works; within
the Source form or documentation, if provided along with the
Derivative Works; or, within a display generated by the
Derivative Works, if and wherever such third-party notices
normally appear. The contents of the NOTICE file are for
informational purposes only and do not modify the License.
You may add Your own attribution notices within Derivative
Works that You distribute, alongside or as an addendum to
the NOTICE text from the Work, provided that such additional
attribution notices cannot be construed as modifying the License.

You may add Your own license statement for Your modifications and
may provide additional grant of rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the
Contribution, and to allow persons to whom the Contribution is
furnished to do so.

5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or reproducing the Work and assume any
risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or exemplary damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or all other
commercial damages or losses), even if such Contributor has been
advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

Copyright 2025 PrintrFi

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
141 changes: 141 additions & 0 deletions skills/printr/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,141 @@
---
name: printr
description: "Token launchpad built for holders. Deploy, fund, sign, stake, and graduate tokens across EVM chains and Solana via the Printr MCP server."
version: "0.16.0"
author: "PrintrFi"
tags:
- token-launch
- launchpad
- solana
- evm
- cross-chain
- mcp
---

# Printr

## Overview

This skill lets an AI agent launch and manage tokens on Base, Ethereum, Arbitrum, BSC, Avalanche, Solana, and other EVM and SVM chains through the [Printr MCP server](https://github.com/PrintrFi/printr-mcp). Printr's launchpad primitives are bonding-curve launches, holder staking, creator-fee distribution, and on-chain graduation to DEX liquidity once a token's curve crosses its threshold. The plugin orchestrates token creation, ephemeral deployment-wallet funding, signing (browser, encrypted keystore, or env-provided key), staking, fee claiming, and balance / transfer tooling.

Every chain is addressed by CAIP-2; every account by CAIP-10. Call `printr_supported_chains` for the canonical chain list at runtime, and `printr_get_deployments` to inspect a token's per-chain graduation status.

## Pre-flight Checks

Before invoking any command, ensure the MCP server is reachable. From a blank environment:

```bash
# Add the server to your agent config (Claude Desktop, Cursor, etc.)
# Either of:
# command: "npx", args: ["-y", "@printr/mcp@latest"]
# command: "bunx", args: ["@printr/mcp@latest"]
```

Optional credentials, all read from environment variables:

```bash
export PRINTR_API_KEY="<partner-key>" # public default works for testing
export OPENROUTER_API_KEY="<your-openrouter-key>" # enables printr_generate_image
export EVM_WALLET_PRIVATE_KEY="<hex>" # autonomous EVM signing
export SVM_WALLET_PRIVATE_KEY="<base58>" # autonomous Solana signing
export PRINTR_DEPLOYMENT_PASSWORD="$(openssl rand -base64 32)" # required for treasury-protected launches
```

Verify the agent can reach the MCP server by calling `printr_supported_chains` — it should return a populated list of chains with CAIP-2 IDs.

## Commands

### Launch (one call)

`printr_launch_token` — create and sign in one call.

- **When to use**: the user asks to launch a token or deploy a new asset, and is happy with default signing behavior.
- **Output**: `token_id`, deployment payload, tx hashes per chain.
- **Example**: launch "Moon Cat" ($MCAT) on Solana with a $10 initial buy.
- **Signing**: omit `private_key` to open a browser signer via `printr_open_web_signer`; pass `private_key` (or set `EVM_WALLET_PRIVATE_KEY` / `SVM_WALLET_PRIVATE_KEY` in env) to sign autonomously.
- **Image**: omit `image` / `image_path` to auto-generate (requires `OPENROUTER_API_KEY`).

### Launch (two-step build + sign)

Use this flow when the agent should inspect or relay the unsigned payload before signing.

1. `printr_create_token` — returns an unsigned tx payload and token metadata.
2. `printr_sign_and_submit_evm` or `printr_sign_and_submit_svm` — sign and submit the payload (or pass `private_key` for autonomous mode).
3. `printr_open_web_signer` — open a browser session (MetaMask / Phantom) when no key is available.

### Treasury-protected launch

Production flow that keeps the treasury key offline behind an ephemeral deployment wallet.

1. `printr_set_treasury_wallet` — unlock the funding source for the session.
2. `printr_fund_deployment_wallet` — create and fund the ephemeral wallet (requires `PRINTR_DEPLOYMENT_PASSWORD`).
3. `printr_launch_token` — deploy using the active wallet automatically.
4. `printr_drain_deployment_wallet` — return unused funds to the treasury. Re-callable after MCP restart; recovers from persisted state.

### Cost estimation

`printr_quote` — call this before any launch and show the user the itemized costs.

- **Inputs**: chains, initial buy mode (pick ONE of `spend_usd`, `spend_native`, `supply_percent`).
- **Output**: per-chain itemized costs in native and USD plus expected initial buy amount.

### Wallet management

| Tool | Purpose |
|------|---------|
| `printr_wallet_new` | Generate an encrypted wallet |
| `printr_wallet_import` | Import an existing key |
| `printr_wallet_unlock` | Activate a stored wallet for the session |
| `printr_wallet_list` | List wallets (private keys hidden) |
| `printr_wallet_remove` | Remove a wallet from the keystore |
| `printr_wallet_bulk_remove` | Remove multiple wallets in one call |

### Utility tools

| Tool | Purpose |
|------|---------|
| `printr_get_balance` | Native token balance |
| `printr_get_token_balance` | ERC-20 / SPL balance |
| `printr_transfer` | Send native tokens |
| `printr_transfer_token` | Send ERC-20 / SPL tokens |
| `printr_get_token` | Token metadata by ID |
| `printr_get_deployments` | Per-chain deployment status |
| `printr_supported_chains` | List all chains with CAIP-2 IDs |
| `printr_generate_image` | Generate a token avatar via OpenRouter |

### Fees

| Tool | Purpose |
|------|---------|
| `printr_get_creator_fees` | Check claimable creator fees |
| `printr_claim_fees` | Claim accumulated fees to the treasury |

### Staking

| Tool | Purpose |
|------|---------|
| `printr_create_stake_position` | Open a stake position on a Printr token |
| `printr_get_staking_positions` | List stake positions (filter by token or owner) |
| `printr_claim_staking_rewards` | Claim rewards or withdraw unlocked principal |

## Error Handling

| Error | Cause | Resolution |
|-------|-------|------------|
| `Printr API error 401 / 403` | Missing or invalid `PRINTR_API_KEY` | Set a valid partner key or fall back to the documented public default |
| `Printr API error 500: chain is unsupported` | CAIP-2 chain ID not registered with Printr | Call `printr_supported_chains` and use one of the returned IDs |
| `Printr API error 500: token not found` | Unknown `token_id` passed to `printr_get_token` / `printr_get_deployments` | Verify the ID; if you just launched, allow a few seconds for indexing |
| `OPENROUTER_API_KEY not set` | Auto image generation requested without a key | Set `OPENROUTER_API_KEY` or pass `image` / `image_path` explicitly |
| `PRINTR_DEPLOYMENT_PASSWORD not set` | Treasury-protected flow invoked without the password | Generate one with `openssl rand -base64 32` and export it before calling `printr_fund_deployment_wallet` |
| `No active wallet` | Signing tool called without a key resolution path | Call `printr_wallet_unlock`, pass `private_key` explicitly, or set `EVM_WALLET_PRIVATE_KEY` / `SVM_WALLET_PRIVATE_KEY` |
| Browser signer never returns | User closed the tab or denied the request | Re-issue the signing call; the previous session is recoverable for a short window |
| Deployment wallet drain fails after restart | Lost session state | Re-run `printr_drain_deployment_wallet` — it recovers from persisted state using `PRINTR_DEPLOYMENT_PASSWORD` |

## Security Notices

- **Risk level**: `standard`. Every transaction requires user confirmation via the browser signer flow unless the user has explicitly set `EVM_WALLET_PRIVATE_KEY` or `SVM_WALLET_PRIVATE_KEY` (autonomous mode is opt-in per env-var, never plugin-driven).
- **Private keys**: never logged, never exfiltrated. Keys live either in the user's encrypted local keystore (AES-256-GCM, password-derived via scrypt), or in environment variables the user controls, or in the user's browser wallet — Printr's servers never see them.
- **`PRINTR_API_KEY`**: the hardcoded default is a documented public `ai-integration` key intended for testing. Production usage should set a partner key.
- **Treasury-protected flow**: `printr_fund_deployment_wallet` creates an ephemeral wallet so the user's treasury key is never exposed during a launch. Call `printr_drain_deployment_wallet` after every launch to recover unused funds.
- **Token risk**: launched tokens are speculative assets. The plugin does not provide investment advice; users are responsible for the tokens they create and the funds they commit.
- **Supported chains and RPCs**: declared in `api_calls` in `plugin.yaml`. The plugin makes no network calls outside that list.
Loading