Arjunkmrm Mango Sago
Wire a minimal Smithery-hosted MCP into Claude Code or Cursor to generate personalized greetings (including optional pirate tone) while learning remote MCP setup.
Overview
ai.smithery/arjunkmrm-mango-sago is a MCP server for the Build phase that lets AI assistants create personalized greetings with an optional pirate-speak flair via Smithery’s hosted streamable-http endpoint.
What is this MCP server?
- Smithery streamable-http remote at server.smithery.ai with Bearer {smithery_api_key} authentication
- Personalized greetings by name in seconds with an optional playful pirate-speak mode
- MCP server schema 2025-09-16; catalog version 1.16.0
- Open-source reference repo at github.com/arjunkmrm/mango-sago for fork-and-customize workflows
- Low-risk sandbox for validating Smithery registry and agent MCP config before production APIs
- Catalog server version 1.16.0 per server.schema.json
- Single streamable-http remote on server.smithery.ai
- MCP schema dated 2025-09-16
What problem does it solve?
You cannot tell whether your agent’s MCP client, Smithery API key, and remote URL are wired correctly until a real server answers a simple tool call.
Who is it for?
Builders validating Smithery auth and remote MCP connectivity with a fun, zero-domain greeting server cloned from a public GitHub example.
Skip if: Teams that need production messaging, CRM outreach, or research APIs—use a purpose-built integration instead of this demo server.
What do I get? / Deliverables
After registration, your agent can invoke greeting tools on the hosted remote so you have a confirmed Smithery + MCP integration baseline before heavier services.
- Working remote MCP registration with authenticated greeting tool responses
- Verified pattern for Smithery URL + Authorization header you can reuse on production MCPs
- Optional pirate-tone greeting output for demos and onboarding docs
Recommended MCP Servers
Journey fit
Demo and sample MCP servers belong on the Build shelf under integrations because solo builders install them while connecting agents to external tools, not while researching markets or shipping production features. Integrations is the canonical subphase for registering streamable-http MCP remotes, Bearer headers, and first successful tool calls from an AI coding agent.
How it compares
Hosted MCP integration for agent tool calls, not a reusable Claude skill or local CLI greeting script.
Common Questions / FAQ
Who is ai.smithery/arjunkmrm-mango-sago for?
Solo builders and small teams testing Claude Code, Cursor, or Codex MCP setup who want a quick, low-stakes remote server before connecting billing or data tools.
When should I use ai.smithery/arjunkmrm-mango-sago?
Use it during the build phase when you first connect Smithery, need to verify Bearer token headers, or want a reference greeting tool while copying patterns into your own MCP server.
How do I add ai.smithery/arjunkmrm-mango-sago to my agent?
Register the Smithery remote URL https://server.smithery.ai/@arjunkmrm/mango-sago/mcp in your MCP client, set Authorization to Bearer plus your smithery_api_key, then restart the agent and call the greeting tools.