Swiftype MCP. Programmatic Search and Index Management
Swiftype connects your AI client directly to enterprise search engines, letting you manage complex indexing logic without touching a web dashboard. It lets your agent run precise queries against core data sources, list all available indexes, track top user clicks, and even programmatically create or delete entire sets of documents.
Claude 
ChatGPT 
Cursor 
Gemini 
Windsurf 
VS Code 
JetBrains 
Vercel Give Claude and any AI agent real-world access
List all available search engines and map schema blueprints to understand what data sources are connected.
Fire complex, raw queries into specific content engines and pull back structured JSON results for immediate analysis.
Bulk create new documents or permanently delete stale records to keep your index clean and accurate.
Retrieve concrete metrics on what users are searching for most often, and which specific pages they click through after a search.
Extract stored metadata to audit document types and ensure your data map adheres to established rules.
Ask an AI about this
Waiting for input…
What AI agents can do with Swiftype: 10 Tools for Search Management
These tools give your agent the power to query, write, read, and audit every aspect of your enterprise search index.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Swiftype MCPSt.create Documents
Adds new structured records, such as billing information, to your active data map.
St.delete Documents
Permanently removes cached pages and associated metrics from the search index.
St.list Documents
Retrieves a list of all stored metadata, tracking IDs for every document type in...
St.list Domains
Verifies the limits set by the automated crawler across specific index scopes.
St.list Engines
Identifies all active, isolated search engines bound to your platform tenant.
St.post Search
Runs a raw query against a specific engine and returns detailed JSON results including property extraction.
St.post Suggest
Provides predictive, spelling-tolerant suggestions for users without querying the main index.
St.analytics Top Clicks
Finds and reports on the precise pages that receive the most clicks after a search.
St.analytics Top Searches
Inspects internal data to discover which keywords are being searched for across your...
St.list Doc Types
Extracts the schema blueprints, showing exactly what types of data maps are...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Swiftype integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Swiftype, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Swiftype / Elastic App Search. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Tired of Web Dashboards?
Today, checking your site's performance means navigating to the analytics portal. You click through tabs labeled 'Searches,' then another tab for 'Clicks.' If you want to know which search term led to a high-value page conversion, you have to pull data from three separate reports and manually cross-reference timestamps—it’s tedious, slow, and prone to human error.
With this MCP, your agent handles that entire process in a single conversation. You simply ask it to correlate user intent with performance metrics. It runs the necessary sequence of commands, like `st.analytics_top_searches` followed by `st.analytics_top_clicks`, and gives you one clean answer.
Swiftype: Direct Access to Your Search Data
The biggest pain point today is that data lives behind complex APIs and proprietary web interfaces. To audit the structure, you might have to guess which endpoints are correct or spend hours calling internal teams for schema documentation.
Now, your agent directly interrogates the core system using tools like `st.list_doc_types` and `st.list_engines`. You don't ask a person; you talk to the database structure itself. It’s immediate, verifiable, and accurate.
What Swiftype MCP does for your AI
Swiftype gives your conversational AI the ability to act as an internal data architect for your organization's search infrastructure. Instead of opening a dozen different web portals just to check indexing status or run analytics, you let your agent interact directly with the core Swiftype endpoints. Your client can list every active index and scope, ensuring you know exactly what data exists.
It handles everything from running raw queries against specific engines to tracking real-world user behavior by retrieving top searched terms and identifying high-conversion click paths. This capability moves search administration out of clunky web forms and straight into your prompt environment. By utilizing the Vinkius catalog within your agent, you gain secure, programmatic access to read, write, and audit structured data maps on demand.
019d760f-aa0f-71da-9603-6e7eee2418d3 
How to set up Swiftype MCP
The bottom line is that you get full, programmatic control over the entire lifecycle of your enterprise search index, without ever needing a web login.
You attach the Swiftype MCP to your AI client through Vinkius, specifying your API credentials for secure access.
Your agent then uses specific commands—like listing available engines or running a search query—to gather necessary data points.
The results return structured JSON data directly into your chat window, allowing your agent to summarize complex findings like top clicks and document counts.
Who uses Swiftype MCP
This MCP is for technical roles and data owners who spend time validating complex information systems. If you're tired of clicking through multiple dashboards or writing boilerplate API calls just to check index status, this is for you.
Using the MCP, they can programmatically audit and validate structured data maps, ensuring new content adheres to strict indexing rules.
They use it to pull real-world analytics, identifying exactly which search queries lead to high-conversion clicks, guiding content creation efforts.
This role uses the MCP to programmatically test and audit isolated data maps, finding index bugs or schema mismatches before they break production.
Benefits of connecting Swiftype MCP
You get immediate visibility into site performance. Instead of manually checking a web dashboard, your agent runs st.analytics_top_searches to tell you what users are searching for right now.
Manage data integrity on the fly. Need to update records? You can use st.create_documents or st.delete_documents directly through conversation, keeping your index clean.
Understand your search scope instantly. Use st.list_engines to see all available isolated indexes and confirm that every required data source is connected.
Deep dive into user conversion paths. Instead of guessing, the MCP executes st.analytics_top_clicks to pinpoint exactly which documents drive actual traffic.
Audit your content structure easily. Running st.list_doc_types provides a schema blueprint view, ensuring new content always fits your data map rules.
Swiftype MCP use cases
Debugging Missing Content
A Data Analyst notices search results are missing documentation for the 'billing' section. They ask their agent to first run st.list_engines to confirm all relevant indexes exist, then use st.list_doc_types to check if a billing schema was ever defined. This quickly diagnoses whether the problem is connectivity or definition.
Optimizing Marketing Copy
A Content Manager wants to know which product pages perform best. They ask their agent to run st.analytics_top_clicks and instantly see a list of the top-performing pages, allowing them to rewrite titles for better SEO.
Auditing Index Changes
A Search Architect needs to prove that old, obsolete policy documents are gone. They ask their agent to use st.delete_documents on a specific set of records and confirm the action using the API wrapper.
Testing New Keywords
A developer wants to test if a new product keyword works well without committing to a change. They ask their agent to run st.post_suggest on the internal wiki engine, getting instant feedback on relevant completions.
Swiftype MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Over-reliance on Guesswork
Trying to search for data that might exist in an index but isn't correctly defined or connected. This results in vague, unactionable error messages.
Always start by checking the available scope. Use st.list_engines first to confirm the engine exists, then use st.list_doc_types to validate the required schema before running a search query with st.post_search.
Treating Data as Black Box
Manually exporting data and trying to figure out which records are outdated or need cleanup, wasting hours on Excel sheets.
Use the tools to make the system tell you what's wrong. Run st.list_documents to see all stored metadata, then use that list to programmatically identify keys for removal using st.delete_documents.
Writing monolithic queries
Attempting to extract every single piece of data in one giant query, which often fails due to scope limits or complexity.
Break down the task using specific tools. First, use st.list_domains to verify crawler limits, then run smaller, targeted queries with st.post_search for distinct pieces of information.
When to use Swiftype MCP
Use this MCP if your core problem is programmatic control over a complex, multi-faceted indexing pipeline. You need to audit schemas (st.list_doc_types), manage content lifecycle (using st.create_documents and st.delete_documents), or pull deep analytics beyond basic search results. Don't use this if you just need simple text retrieval; a standard document storage connector will suffice. Also, don't use it if your only goal is to read one specific field from one single record; those tools are overkill. This MCP is for the system administrators and power users who manage how data gets into the search engine and what metrics that data generates.
Frequently asked questions about Swiftype MCP
How do I check what search engines Swiftype can access? +
You run st.list_engines. This tool extracts a list of every active index bound to your account, giving you an immediate overview of all available data sources.
Can I use st.post_search for simple keyword searches? +
Yes, st.post_search fires raw queries into a specific engine and returns detailed JSON results. This means you can ask complex questions that go beyond just matching keywords.
What is the difference between st.analytics_top_searches and st.analytics_top_clicks? +
st.analytics_top_searches tells you what people are looking for, while st.analytics_top_clicks tells you which documents they actually clicked on after searching.
How do I add new data to my index using Swiftype? +
You use the st.create_documents tool. This allows your agent to inject new, structured payload data into the system in bulk without you needing to upload a file.
Does Swiftype MCP help me audit old records? +
Yes. You can use st.list_documents to dump all stored metadata and track IDs, helping you identify which documents are stale and need cleaning up or deletion using st.delete_documents.