Manage your Savanto store from your AI: catalog, content, prompts, and analytics, by chat.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"savanto": {
"env": {
"SAVANTO_API_KEY": "if_sk_your_key_here"
},
"args": [
"-y",
"@savantoai/mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A local Model Context Protocol server that exposes your Savanto AI workspace to Claude, ChatGPT, Cursor, and any other MCP-compatible client — so you can configure, populate, and operate your store's AI assistant by talking to your own AI, instead of clicking through a dashboard.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@savantoai/mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @savantoai/mcp-server against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Autonomous spec-to-product coding-agent CLI with an MCP server exposing 34 tools over stdio.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
App framework, testing framework, and inspector for MCP Apps.
MCP Security Weekly
Get CVE alerts and security updates for io.github.SavantoAI/mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A local Model Context Protocol server that exposes your Savanto AI workspace to Claude, ChatGPT, Cursor, and any other MCP-compatible client — so you can configure, populate, and operate your store's AI assistant by talking to your own AI, instead of clicking through a dashboard.
Once configured, your agent gains a curated set of tools that mirror the Savanto REST API, spanning the full configure → observe → refine loop:
| Category | Representative tools | Scope |
|---|---|---|
| Workspaces | list_workspaces, create_workspace, update_workspace, delete_workspace | tenant:admin |
| Configuration | get_workspace_settings, update_workspace_settings, custom-domain CRUD, discover_tools, generate_domain_config, validate_custom_domain, test_domain_connection, generate_color_scheme, chat/search widget config | config:admin |
| Content | upsert_product/upsert_post (+ bulk_*, list_*, get_*, patch_*, delete_*) | admin:products, admin:posts |
| Taxonomies | upsert_taxonomy, bulk_upsert_taxonomies, list/get/delete_taxonomy | admin:taxonomies |
| Prompts | upsert_prompt, list_prompts, search_prompts, delete_prompt (+ bulk) | admin:prompts, prompts:read |
| Webhooks | create_webhook, list/get/update/delete_webhook, test_webhook, get_webhook_stats | admin:webhooks |
| Crawl | start_crawl, get_crawl_status/history/config, update_crawl_config | admin:posts |
| Search | search_products, search_posts | search:products, search:posts |
| Analytics | get_search_analytics, get_chat_analytics, get_feedback_analytics, search_search_logs, list_feedback | tenant:admin, feedback:admin |
| Threads | search_threads, get_thread, get_thread_messages, get_thread_analytics, delete_thread, bulk_delete_threads | threads:admin |
| Chat | chat | chat |
| Diagnostics | whoami, get_tenant_usage | (none) / tenant:admin |
Two things keep the surface safe and legible to clients:
/tenant/whoami and only registers tools your key can actually use. An agent is never shown a tool it would get a 403 for, and a publishable widget key sees almost nothing.readOnlyHint, destructiveHint, idempotentHint) so clients can auto-approve safe reads and flag destructive writes; deletes additionally require an explicit confirm: true.The server also exposes Skills (MCP prompts) — step-by-step playbooks for common multi-tool workflows:
onboard-store-end-to-end – create a workspace, ingest content, configure behaviour + branding, smoke-testonboard-wordpress / onboard-shopify – platform-specific onboarding walkthroughsconfigure-chat – tune persona, special instructions, and handoff rulesconfigure-custom-domain – wire a custom capability (order tracking, account lookup) to MCP servers / REST APIsaudit-and-improve – the observe→refine loop: find failing chats / zero-result searches / negative feedback and fix themdebug-empty-search – diagnose why a product search returns no hitsmigrate-from-competitor – bulk-import from another chat vendor's exportif_sk_…). Create one in the API Keys page of your dashboard.
Publishable keys (
if_pk_…) are client-side and cannot provision workspaces — the server will refuse to start with one.
No global install needed — run it with npx:
export SAVANTO_API_KEY=if_sk_your_key_here
npx -y @savantoai/mcp-server
Point to a non-production cloud (staging, local dev):
export SAVANTO_API_URL=http://localhost:3001
In addition to the local stdio server above, the same tool surface can run as a **hoste