
Kodey Ai Mapwise Mcp
Smoke-test Smithery MCP wiring in your agent with a minimal greeting tool before you connect heavier production APIs.
Overview
ai.smithery/kodey-ai-mapwise-mcp is a Build-phase MCP server that generates personalized greetings on demand for testing Smithery-hosted agent tool chains.
What is this MCP server?
- Generates friendly personalized greetings from a simple natural-language prompt
- Smithery streamable-http MCP remote with Bearer smithery_api_key authentication
- Catalog version 1.0.0 under @kodey-ai/mapwise-mcp listing name
- Low-risk way to confirm Claude Code, Cursor, or Codex can call a hosted Smithery server
- Not a geospatial or mapping suite despite the Mapwise name—capabilities match the greeting-oriented catalog description
- Catalog server version 1.0.0
- Transport: streamable-http on server.smithery.ai/@kodey-ai/mapwise-mcp/mcp
- Auth header: Authorization Bearer {smithery_api_key} (required secret in schema)
What problem does it solve?
You are not sure your MCP client, Smithery key, and remote URL are wired correctly, and debugging that on a complex API server is painful.
Who is it for?
Solo builders taking their first Smithery MCP step who want a one-tool sanity check in Claude Code, Cursor, or Codex.
Skip if: Teams needing real mapping, GIS, or location APIs, or anyone looking for substantive production automation rather than a connectivity smoke test.
What do I get? / Deliverables
After adding the remote, you can trigger a simple greeting tool call and know your agent-to-Smithery pipeline works before production integrations.
- Confirmed MCP client configuration against a live Smithery remote (v1.0.0)
- Successful personalized greeting tool invocation from your agent
- Baseline pattern for adding heavier integrations afterward
Recommended MCP Servers
Journey fit
Lightweight demo MCP servers are installed while you stand up agent tooling and validate transport, auth, and tool invocation paths. Agent-tooling covers hello-world and scaffold servers that prove your MCP client config works end to end.
How it compares
Minimal greeting demo MCP—not Mapbox-style maps, not a location data platform.
Common Questions / FAQ
Who is ai.smithery/kodey-ai-mapwise-mcp for?
It is for developers validating MCP and Smithery setup who want a tiny callable tool before attaching larger integrations.
When should I use ai.smithery/kodey-ai-mapwise-mcp?
Use it early in Build agent-tooling when you need to confirm streamable-http, Bearer auth, and tool routing in your client.
How do I add ai.smithery/kodey-ai-mapwise-mcp to my agent?
Point your MCP client at the Smithery URL for @kodey-ai/mapwise-mcp, set Authorization to Bearer plus your smithery_api_key, and run a greeting prompt that invokes the server tool.