SavantoAI MCP

Name: SavantoAI MCP
Author: SavantoAI

by SavantoAIversion 0.2.1i★ –iComputer or cloud

Registry nameio.github.SavantoAI/mcp-server

Install

Overview

Description from the maker (original English)

Manage your Savanto store from your AI: catalog, content, prompts, and analytics, by chat.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Marketing & social media
You need to fill in: SAVANTO_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: SAVANTO_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.savanto.ai/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "savantoai": {
      "command": "npx",
      "args": [
        "-y",
        "@savantoai/mcp-server"
      ],
      "env": {
        "SAVANTO_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http savantoai https://mcp.savanto.ai/mcp

Or run it on your computer

claude mcp add savantoai --env SAVANTO_API_KEY=your-value -- npx -y @savantoai/mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "savantoai": {
      "url": "https://mcp.savanto.ai/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "savantoai": {
      "command": "npx",
      "args": [
        "-y",
        "@savantoai/mcp-server"
      ],
      "env": {
        "SAVANTO_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "savantoai": {
      "type": "http",
      "url": "https://mcp.savanto.ai/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "savantoai": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@savantoai/mcp-server"
      ],
      "env": {
        "SAVANTO_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.savanto.ai/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SAVANTO_API_KEY secret required env
A Savanto secret API key (if_sk_…) from your dashboard. Local/stdio use only; the hosted remote uses one-click OAuth instead.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account SavantoAI, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Marketing & social mediai

More stars than 0% of the other 2985 servers in this category
Published to the registry more recently than 14% of the other 2985 servers in this category
Basic checks equal to or better than 100% of the other 2985 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is SavantoAI MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SAVANTO_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

MCP YouTube Transcript

by jkawamoto

An MCP server retrieving transcripts of YouTube videos

Runs on your computer★ 495MITUpdated 10 days ago

Install

Google Analytics MCP

by surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Runs on your computer★ 244MITUpdated 10 days ago

Install

BibiGPT YouTube Video Summarizer

by JimmyLv

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

Runs in the cloud★ 137MITUpdated 10 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@savantoai/mcp-server

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.

What it does

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:

Scope-gated at startup — the server probes /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.
Annotated — every tool carries MCP hints (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-test
onboard-wordpress / onboard-shopify – platform-specific onboarding walkthroughs
configure-chat – tune persona, special instructions, and handoff rules
configure-custom-domain – wire a custom capability (order tracking, account lookup) to MCP servers / REST APIs
audit-and-improve – the observe→refine loop: find failing chats / zero-result searches / negative feedback and fix them
debug-empty-search – diagnose why a product search returns no hits
migrate-from-competitor – bulk-import from another chat vendor's export

Requirements

Node.js 20 or later
A secret Savanto API key (starts with if_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.

Quick start

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

Remote server (preview)

In addition to the local stdio server above, the same tool surface can run as a hosted HTTP server so clients connect to a URL instead of spawning npx — no local Node, no per-machine config. This is the path toward one-click "Connect to Claude/ChatGPT" (OAuth) onboarding; today it accepts your secret key as a Bearer token.

# Each client authenticates per-request — there is NO server-wide key.

SAVANTO_API_URL=https://api.savanto.ai PORT=8080 npx -y -p @savantoai/mcp-server savanto-mcp-http

The server mounts the MCP endpoint at /mcp and a liveness probe at /healthz. Clients send their key as Authorization: Bearer if_sk_…; the tool surface is scope-gated to that key's tenant, exactly as in the stdio server. Point an MCP client that supports remote (Streamable HTTP) servers at https://your-host/mcp with that bearer token.

Auth is currently the raw secret key. A future release replaces it with

OAuth-issued, tenant-scoped tokens so customers can connect with zero key

handling — the transport and tool layer are unchanged by that swap.

Client configuration

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

"mcpServers": { "savanto": { "command": "npx", "args": ["-y", "@savantoai/mcp-server"], "env": { "SAVANTO_API_KEY": "if_sk_your_key_here" } } } }

Restart Claude Desktop. You should see a hammer/tool icon in the message bar; the Savanto tools are listed there.

Cursor

In Cursor settings → Features → Model Context Protocol → Add new MCP server:

"savanto": { "command": "npx", "args": ["-y", "@savantoai/mcp-server"], "env": { "SAVANTO_API_KEY": "if_sk_your_key_here" } } }

Cline / Roo / other VS Code agents

Add to the extension's MCP config (usually a JSON file under ~/.cline or similar):

"mcpServers": { "savanto": { "command": "npx", "args": ["-y", "@savantoai/mcp-server"], "env": { "SAVANTO_API_KEY": "if_sk_your_key_here" } } } }

OpenAI Agents / Responses API

from openai import OpenAI

from mcp import StdioServerParameters

server = StdioServerParameters( command="npx", args=["-y", "@savantoai/mcp-server"], env={"SAVANTO_API_KEY": "if_sk_your_key_here"}, )

Local MCP Inspector (for debugging)

npx @modelcontextprotocol/inspector npx @savantoai/mcp-server

The Inspector gives you a web UI to list tools, call them directly, and watch request/response payloads — great for confirming your key is wired correctly before handing the server to an agent.

Example prompts

Once the server is registered in your MCP client, try:

"Set up a new Savanto workspace for acme-store, crawl https://acme.test, give it an outdoor-adventure tone, and brand the widget around #0a7d2c." *(end-to-end onboarding)*

"Look at acme-store's last 30 days — what are visitors searching for that returns nothing, and which conversations went unresolved? Then add content to fix the top few." *(the observe→refine loop)*

"Add an order-tracking capability to acme-store backed by our MCP server at https://mcp.acme.test/orders, validate it, and test it before enabling." *(custom domain)*

"Why did this conversation get a thumbs-down?" — pull list_feedback, read the thread, and propose a fix.

The agent picks the right tools automatically (and clients can auto-approve the read-only ones). You can also invoke a Skill explicitly — e.g. in Claude Desktop, /onboard-store-end-to-end or /audit-and-improve kicks off that full playbook.

Environment variables

Variable	Default	Purpose
`SAVANTO_API_KEY`	_(required)_	Your secret API key (`if_sk_…`).
`SAVANTO_API_URL`	`https://api.savanto.ai`	Override for staging / local dev.

Security

Always use separate API keys per agent / machine — so you can revoke one without affecting the others. The API Keys page tracks the last-used timestamp of each key.
Keys are passed via environment variables, never logged. The server prints a one-line identity banner on startup (to stderr) showing the tenant id and scope list — no secrets.
The server runs over stdio and never opens a network port. It only speaks to the Savanto API host you point it at.
delete_workspace requires an explicit confirm: true parameter in the tool call — a safety gate against hallucinated destructive operations.

Local development

From the repo root:

npm install

npm run build --workspace=@savantoai/mcp-server SAVANTO_API_KEY=if_sk_… SAVANTO_API_URL=http://localhost:3001 node sdks/mcp/dist/stdio.js

Run the tests:

npm run test --workspace=@savantoai/mcp-server

License

MIT. See LICENSE.

SavantoAI MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Marketing & social mediai

Common questions

Alternatives

MCP YouTube Transcript

Google Analytics MCP

BibiGPT YouTube Video Summarizer

README from the maker

@savantoai/mcp-server

What it does

Requirements

Quick start

Remote server (preview)

Client configuration

Claude Desktop

Cursor

Cline / Roo / other VS Code agents

OpenAI Agents / Responses API

Local MCP Inspector (for debugging)

Example prompts

Environment variables

Security

Local development

License