
GTM Swag
com.gtmswagPublished by gtmswag.comOfficial publisherv1.0.0Updated Oct 24, 2026
Personalized, thoughtful gifts that help GTM teams get meetings. Agents prepare; people approve.
Overview
GTM Swag is a remote MCP server for preparing personalized gifts that help go-to-market teams get meetings, with agents preparing and people approving.
- What you can do
- Prepare personalized, thoughtful gift ideas aimed at helping GTM teams get meetings, based on the description provided. Support a workflow where the agent prepares gift options and a person reviews and approves them before anything proceeds. Connect through a remote endpoint with OAuth sign-in or an optional workspace key. No individual tools are documented, so the exact actions available are not specified.
- When to use it
- Consider it when a go-to-market or sales team wants an assistant to help draft personalized gift outreach and keep a human approval step in the loop. It is not a fit if you need documented, granular tooling, since no tools are listed.
- Requirements
- A remote MCP connection to the provider's endpoint. Authentication is required: OAuth sign-in, or an optional workspace key sent as a Bearer token in the Authorization header. No local runtime, packages or environment variables are declared.
Installation
In SourceWeft
- Open GTM Swag in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.gtmswag%2Fgtm-swag/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"gtm-swag": {
"type": "http",
"url": "https://gtmswag.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 12, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.