{ "SchemaVersion": "1", "Kind": "DirectoryIssues", "Slug": "printr", "Name": "printr", "CanonicalUrl": "https://askpod.ai/mcp/printr/issues", "ServerUrl": "https://askpod.ai/mcp/printr", "IssueTotal": 31, "Held": 20, "Issues": [ { "Title": "feat(mcp): remote MCP server hosted on Cloudflare Workers", "Excerpt": "## Motivation\n\n`@printr/mcp` today is **stdio-only** — every user installs it locally via the CLI (`bunx @printr/cli setup`). That terminal-first flow is the biggest drop-off between \"interested\" and \"agent connected\" (see #113). A **remote MCP server hosted on Cloudflare Workers** gives clients a plain URL to connect to — no local install, no runtime, no keystore on the user's box.\n\nThis is now unblocked: Epic A (#103) made `@printr/sdk` Workers-ready, so the core runs on a V8 isolate without v", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/124", "PublishedAt": "2026-06-19T23:12:01.000Z", "State": "open", "Comments": 5, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Epic A: SDK Workers-ready", "Excerpt": "## Goal\n\n`@printr/sdk` evaluates and runs cleanly on Cloudflare Workers / edge runtimes without vendoring.\n\n## Why bundle\n\nAll four sub-issues share one acceptance gate: \"a Worker importing the SDK barrel evaluates without throwing.\" Same `package.json` `exports` surgery, same Worker eval smoke test, same release. Landing them piecemeal leaves Workers consumers half-broken between releases.\n\n## Sub-issues\n\n- [ ] #96 — lazy-load `sharp` + `node:fs` in `image.ts`\n- [ ] #97 — drop `createRequire` s", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/103", "PublishedAt": "2026-05-25T22:50:33.000Z", "State": "closed", "Comments": 2, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "feat(mcp): publish Printr skill manifest for agent composition", "Excerpt": "## Motivation\n\nBankr publishes a [skills repo](https://github.com/BankrBot/skills) so any agent runtime can pull in their capabilities as a plug-and-play skill. We already have `packages/cli/skills/printr/SKILL.md` — this issue is about formalizing and publishing it so other agents (and our own users) can install Printr capabilities the same way.\n\nThe README already advertises `npx skills add PrintrFi/printr-mcp`, but the skill itself isn't surfaced as a first-class artifact alongside the MCP se", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/64", "PublishedAt": "2026-05-14T19:26:49.000Z", "State": "closed", "Comments": 2, "Reporter": "Contributor", "Rank": "top", "Extractor": "github_issue" }, { "Title": "docs: update gitbook for current MCP/SDK + cross-link with the dev docs", "Excerpt": "## Context\n\nWhile aligning the gh-pages dev docs voice to the gitbook (https://printr.gitbook.io/printr-docs/), a few gitbook pages were found **out of date** vs the current `printr-mcp` repo. Queueing a pass to fix them and to **cross-link** the gitbook (product/conceptual) with the gh-pages dev docs (https://printrfi.github.io/printr-mcp/, MCP tool + SDK reference).\n\n## Stale items found (verify + fix)\n\n- **CLI command is wrong.** `for-agents/printr-mcp.md` + `for-agents/README.md` show `bunx ", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/131", "PublishedAt": "2026-06-20T07:52:28.000Z", "State": "closed", "Comments": 1, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "setupBareExtension: generic factory for proto/openapi wrappers", "Excerpt": "## Idea\nGeneric factory that takes a class/ctor and returns a mapped-type object with uncapitalized method names. Collapses N near-identical wrapper modules (each generated proto/openapi service file) into one helper invocation.\n\n```ts\nexport function setupBareExtension any>(Ctor: T): UncapitalizeKeys> { ... }\n```\n\n## Why\n- Pairs with #83 (template-literal renaming) for ergonomic proto APIs\n- Smaller surface in `staking-api.ts` / `fees-api.ts` once ", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/84", "PublishedAt": "2026-05-17T22:50:09.000Z", "State": "closed", "Comments": 1, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Template-literal method renaming for proto wrappers", "Excerpt": "## Idea\nStrip `Request`/`Msg`/`Response` suffixes at the type level for generated proto wrappers in `fees-api.ts` and `staking-api.ts`:\n\n```ts\ntype SimplifyRequestMethod =\n T extends `${infer Base}Request` ? Uncapitalize : T;\n\ntype KeepOnlySimplifiedRequestMethods = {\n [K in keyof T as K extends `${string}Request` ? SimplifyRequestMethod : never]: T[K];\n};\n```\n\nLets the public surface expose `.claimRewards()` / `.createStakePosition()` etc. even when the ", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/83", "PublishedAt": "2026-05-17T22:49:57.000Z", "State": "closed", "Comments": 1, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "feat(sdk,mcp): use CAIP-10 token IDs for printr_transfer_token / executeTokenTransfer", "Excerpt": "## Context\n\nSurfaced in Copilot review on #56. The `printr_transfer_token` MCP tool and the SDK `executeTokenTransfer` dispatcher both accept an unqualified `token_address` and infer the execution chain from the recipient's CAIP-10 address. A caller who pastes a token contract from another chain (very common — many tokens deploy to multiple EVM chains under different addresses) will silently execute against whatever code or EOA happens to live at that address on the destination chain.\n\n`printr_g", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/58", "PublishedAt": "2026-05-05T23:46:12.000Z", "State": "closed", "Comments": 1, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Published tarball 0.16.1 ships certs/key.pem (private key) via the \"files\" allowlist", "Excerpt": "Hello,\n\nA heads-up from outside the project rather than a bug in the code.\n\n**The published tarball for `@printr/mcp@0.16.1` contains `certs/key.pem` (227 bytes) alongside\n`certs/fullchain.pem` (4108 bytes).** A 227-byte PEM next to a full chain is the shape of a TLS\n**private** key, not a public one. It is in the current latest version, so it is in every copy\ninstalled since release; `npm pack @printr/mcp@0.16.1` reproduces it in seconds.\n\nThis is not the usual packaging accident — `package.jso", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/137", "PublishedAt": "2026-08-27T19:58:16.000Z", "State": "open", "Comments": 0, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "feat(docs): generate SDK API reference (TSDoc → MDX, like onrails)", "Excerpt": "## Motivation\n\n#57 backfilled TSDoc across every public `@printr/sdk` export and MCP `register*Tool`. Now that the source carries structured doc comments, we can surface a proper **API reference** section in the docs site — the `sdk.mdx` page is currently a hand-written high-level map, not per-function reference.\n\nTarget shape: a dedicated API section like **`~/dev/onrails`** (`apps/docs/content/docs/api/{result,maybe,pattern}.mdx`) — rich per-primitive pages with twoslash examples.\n\n## Approach", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/125", "PublishedAt": "2026-06-19T23:14:49.000Z", "State": "open", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "feat(sdk,cli): extract MCP client table to @printr/sdk for web reuse", "Excerpt": "## Motivation\n\nThe only way to install the Printr MCP server today is the CLI (`bunx @printr/cli setup --client cursor`). This is a terminal-first flow that most app users never complete — it's the single biggest drop-off between \"user is in the app\" and \"user has an agent connected\".\n\nWe want a **\"Connect your agent\" button** in the main app (`printr/web`) that renders the per-client MCP config (copy-to-clipboard + deep links) directly in the UI, so install moves into the product surface where ", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/113", "PublishedAt": "2026-06-02T04:45:33.000Z", "State": "open", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Epic C: Agent trading UX", "Excerpt": "## Goal\n\nAgents using `@printr/mcp` can swap, buy, sell, and bridge — not just launch.\n\n## Why bundle\n\nBoth sub-issues:\n- Need the signer primitive from Epic B / #100\n- Ship MCP tools + SDK adapter pair\n- Require provider choice + e2e fork tests\n- Share fee-routing / quote-flow architecture decisions\n\nLanding them as one epic forces consistent UX (quote-then-confirm vs one-shot, fee model, status polling).\n\n## Sub-issues\n\n- [ ] #62 — trading tools: swap, buy, sell by ticker\n- [ ] #63 — cross-cha", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/105", "PublishedAt": "2026-05-25T22:50:37.000Z", "State": "open", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Epic B: Shared SDK primitives", "Excerpt": "## Goal\n\nLift two pieces of MCP-internal logic into shared SDK subpaths so every Printr client reuses them.\n\n## Why bundle\n\nBoth extract logic currently duplicated/inlined in MCP into `@printr/sdk` subpaths. Same review pattern (subpath export, interface, two reference impls, MCP swap). #100 unblocks Epic C signing flows.\n\n## Sub-issues\n\n- [ ] #99 — `normalizeTokenId` + token-id regex exports in `@printr/sdk/caip`\n- [ ] #100 — extract signer primitive to `@printr/sdk/signer`\n\n## Order\n\n#99 first", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/104", "PublishedAt": "2026-05-25T22:50:35.000Z", "State": "open", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "feat(sdk): processImageBytes(bytes, opts) helper", "Excerpt": "## What to build\n\n`packages/sdk/src/image.ts` exposes `processImagePath` (reads from disk via `node:fs/promises`). Add a parallel `processImageBytes(bytes: Uint8Array, opts): ResultAsync` that takes raw bytes and returns processed bytes.\n\nUse cases:\n\n- Browsers / edge runtimes / Workers — no filesystem access\n- HTTP servers that receive uploads in-memory (multipart, JSON-base64, etc.)\n- Any consumer that has already fetched the image and shouldn't have to round-trip throu", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/102", "PublishedAt": "2026-05-25T22:36:56.000Z", "State": "open", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "feat(sdk): lighter balance via direct JSON-RPC", "Excerpt": "## What to build\n\n`packages/sdk/src/balance.ts` currently pulls `@solana/web3.js` (~600KB minified) and `viem` for balance queries. For consumers that only need to read native or SPL balances, this is a heavy tax — especially on edge/Workers runtimes with bundle size limits.\n\nAdd a lighter variant that hits Solana / EVM JSON-RPC endpoints directly with `fetch` and parses responses with Zod. Same `ResultAsync` shape so the substitution is mechanical.\n\nStrategy:\n\n- Keep the ", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/101", "PublishedAt": "2026-05-25T22:34:33.000Z", "State": "closed", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "feat(sdk): extract signer primitive to @printr/sdk/signer", "Excerpt": "## What to build\n\nLift the browser-sign-by-URL session machinery out of `packages/mcp/src/server/{sessions,app}.ts` into a new `@printr/sdk/signer` subpath. Every Printr client that needs non-custodial signing — MCP today, future apps tomorrow — wants the same primitive: mint a signing session, hand the user a URL, let them sign in their wallet, poll/await completion.\n\nThis is a high-leverage upstream change: it lets a client orchestrate signing flows without ever holding a private key.\n\nShape (", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/100", "PublishedAt": "2026-05-25T22:34:25.000Z", "State": "open", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "feat(sdk): normalizeTokenId + token-id regex exports", "Excerpt": "## What to build\n\nEvery Printr client (MCP server, future apps) needs to accept user-typed token identifiers in any of these forms:\n\n- Telecoin ID hex (e.g. `0xda97f29a4c137298ed138194b39b8b81eb7889018cd9ae4ab4a053fe0bfb7ed5`)\n- EVM CAIP-10 (e.g. `eip155:8453:0x...`)\n- Solana CAIP-10 (e.g. `solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp:G6mNZ...`)\n- **Bare Solana mint base58** (e.g. `G6mNZN8o16QBcTqfuEx6FzjiWa94B1XWhfyDxjDibrrr`)\n\n…then normalize to a canonical form the API accepts. The MCP and any fut", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/99", "PublishedAt": "2026-05-25T22:34:05.000Z", "State": "open", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "feat(sdk): types-only @printr/sdk/openapi entry", "Excerpt": "## What to build\n\nAdd a `./openapi` subpath export to `@printr/sdk` that re-exports **only** the generated OpenAPI types — `paths`, `components`, `operations` — from `api.gen.d.ts`. No runtime code.\n\nToday, consumers wanting strict response types have to:\n\n1. Either import from `@printr/sdk/client`, which now pulls runtime JS (broken on Workers; see #97), or\n2. Define their own loose types and lose strict generated shapes, then cast at every API call site.\n\nA types-only entry lets clients pull s", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/98", "PublishedAt": "2026-05-25T22:33:39.000Z", "State": "closed", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "fix(sdk): emit Workers-friendly bundle, drop createRequire shim", "Excerpt": "## What to build\n\nEvery module in `@printr/sdk/dist/*` currently starts with:\n\n```js\nimport { createRequire } from \"node:module\";\nvar __require = createRequire(import.meta.url);\n```\n\nThis is Bun's bundler default for CJS interop with deps that ship CommonJS (e.g. `neverthrow`'s `.cjs.js`). Cloudflare Workers throws on evaluation because `createRequire(import.meta.url)` receives `undefined` for `import.meta.url` in some configurations and because `node:module` isn't a Workers primitive even with ", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/97", "PublishedAt": "2026-05-25T22:33:24.000Z", "State": "closed", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "fix(sdk): lazy-load sharp + node:fs in image.ts", "Excerpt": "## What to build\n\n`packages/sdk/src/image.ts` statically imports `sharp` and `node:fs/promises` at module top level. The `@printr/sdk` barrel re-exports `buildToken` from `token.ts`, which re-exports `image.ts` transitively — so importing **anything** from the SDK barrel pulls those Node-only deps into the consumer bundle.\n\nThis kills the SDK in any non-Node runtime (Cloudflare Workers, browser, Deno-without-node-compat, edge functions).\n\nMove the `sharp` and `node:fs/promises` imports inside th", "SourceUrl": "https://github.com/PrintrFi/printr-mcp/issues/96", "PublishedAt": "2026-05-25T22:33:07.000Z", "State": "closed", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Migrate signAndSubmit{Evm,Svm} to ResultAsync", "Excerpt": "## Context\nThe public signers in \\`packages/sdk/src/evm.ts\\` and \\`packages/sdk/src/svm.ts\\` still return \\`Promise\\` and throw on every failure mode (no RPC, broadcast failure, on-chain revert, confirmation timeout). This violates the project rule \"use neverthrow Result types for all failable operations\" \\([feedback\\_neverthrow\\_match\\](../blob/main/AGENTS.md)\\). Discovered during PR #92 audit.\n\n## Scope\n\n**SDK (signers + helpers):**\n- \\`signAndSubmitEvm\\` → \\`ResultAsync