feat(tools-registry): add Nitrosend - #14992
Merged
Merged
Conversation
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Collaborator
|
@auscaster changes look good but could you please sign your commits? we won't be able to merge otherwise |
auscaster
force-pushed
the
add-nitrosend-tool
branch
from
June 3, 2026 01:15
2bf65be to
d272140
Compare
Author
|
Thanks for the heads up. I've re-signed the branch and GitHub now shows both commits as verified. The remaining Vercel check appears to be the deploy authorization gate rather than a code/signing issue. Appreciate the review. |
aayush-kapoor
approved these changes
Jun 3, 2026
aayush-kapoor
added
the
backport
github-actions
Bot
removed
the
backport
Contributor
|
|
aayush-kapoor
added a commit
that referenced
this pull request
Jun 3, 2026
This is an automated backport of #14992 to the release-v6.0 branch. FYI @auscaster This backport has conflicts that need to be resolved manually. ### `git cherry-pick` output ``` Auto-merging content/tools-registry/registry.ts CONFLICT (content): Merge conflict in content/tools-registry/registry.ts error: could not apply 6e05a57... feat(tools-registry): add Nitrosend (#14992) hint: After resolving the conflicts, mark them with hint: "git add/rm <pathspec>", then run hint: "git cherry-pick --continue". hint: You can instead skip this commit with "git cherry-pick --skip". hint: To abort and get back to the state before "git cherry-pick", hint: run "git cherry-pick --abort". hint: Disable this message with "git config set advice.mergeConflict false" ``` --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Aayush Kapoor <aayushkapoor34@gmail.com> Co-authored-by: Aayush Kapoor <83492835+aayush-kapoor@users.noreply.github.com>
gr2m
pushed a commit
that referenced
this pull request
Jun 5, 2026
Adds Nitrosend to the AI SDK Tools Registry. ## Summary - **Package**: [`@nitrosend/ai-sdk`](https://www.npmjs.com/package/@nitrosend/ai-sdk) — published v0.1.0 - **Source**: https://github.com/nitrosend/ai-sdk - **Docs**: https://docs.nitrosend.com/integrations/vercel-ai-sdk Nitrosend is a multi-channel marketing platform (email, SMS, flows, campaigns). `@nitrosend/ai-sdk` wraps Nitrosend's remote MCP server as Vercel AI SDK tools so agents can send email, manage contacts, build automation flows, and run campaigns from `generateText` / `streamText` / agent loops. ## Positioning This is a tool surface, not a model provider. The package wraps `@ai-sdk/mcp` defaults, generates typed Zod schemas from the Nitrosend MCP manifest, and exposes a small typed API (`nitrosend`, `withNitrosendTools`, `pickNitrosendToolSchemas`). ## Verification - [x] `@nitrosend/ai-sdk@0.1.0` is publicly installable on npm - [x] All required `Tool` interface fields populated (slug, name, description, packageName, tags, apiKeyEnvName, installCommand, codeExample, docsUrl, apiKeyUrl, websiteUrl, npmUrl) - [x] Code example imports from `ai` and `@nitrosend/ai-sdk` only; uses `stopWhen: stepCountIs(N)` so the model can take a follow-up step after a tool call - [x] Code example uses `withNitrosendTools` to guarantee the MCP transport closes in a `finally` block - [x] `installCommand` provided for pnpm / npm / yarn / bun - [x] No claims of Vercel Marketplace availability (separate listing track) ## Notes for reviewers The package wraps a remote MCP server, so the toolset is async-loaded behind a lifecycle helper rather than synchronous-factory style like `webSearch()` / `executeCode()`. This is intentional — MCP tool discovery happens at runtime against the live server, which keeps the registry submission decoupled from server-side schema changes. --------- Co-authored-by: Aayush Kapoor <83492835+aayush-kapoor@users.noreply.github.com>
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Nitrosend to the AI SDK Tools Registry.
Summary
@nitrosend/ai-sdk— published v0.1.0Nitrosend is a multi-channel marketing platform (email, SMS, flows, campaigns).
@nitrosend/ai-sdkwraps Nitrosend's remote MCP server as Vercel AI SDK tools so agents can send email, manage contacts, build automation flows, and run campaigns fromgenerateText/streamText/ agent loops.Positioning
This is a tool surface, not a model provider. The package wraps
@ai-sdk/mcpdefaults, generates typed Zod schemas from the Nitrosend MCP manifest, and exposes a small typed API (nitrosend,withNitrosendTools,pickNitrosendToolSchemas).Verification
@nitrosend/ai-sdk@0.1.0is publicly installable on npmToolinterface fields populated (slug, name, description, packageName, tags, apiKeyEnvName, installCommand, codeExample, docsUrl, apiKeyUrl, websiteUrl, npmUrl)aiand@nitrosend/ai-sdkonly; usesstopWhen: stepCountIs(N)so the model can take a follow-up step after a tool callwithNitrosendToolsto guarantee the MCP transport closes in afinallyblockinstallCommandprovided for pnpm / npm / yarn / bunNotes for reviewers
The package wraps a remote MCP server, so the toolset is async-loaded behind a lifecycle helper rather than synchronous-factory style like
webSearch()/executeCode(). This is intentional — MCP tool discovery happens at runtime against the live server, which keeps the registry submission decoupled from server-side schema changes.