2,500+ MCP servers ready to use
Vinkius

Swiftype MCP Server for Cursor 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Swiftype and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "swiftype": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Swiftype
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Swiftype MCP Server

Empower your conversational AI with robust enterprise search capabilities by securely integrating the Swiftype (Elastic) MCP connector. Stop navigating web dashbaords to manage indexing logic; allow your LLM to act as a direct data architect interacting with your core Swiftype endpoints natively. With full support for reading, creating, and deleting JSON documents on the fly, inspecting live search engine queries, and querying direct analytical metrics like top clicks—this connector brings headless search administration straight to your preferred prompt environment.

Cursor's Agent mode turns Swiftype into an in-editor superpower. Ask Cursor to generate code using live data from Swiftype and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

  • Headless Search & Suggestions — Execute strict queries interrogating custom content engines running st.post_search and provide predictive autocompletes processing st.post_suggest.
  • CRUD Document Indexing — Pull exact active records from isolated data maps using st.list_documents, inject new payload structures in bulk operating st.create_documents, or vaporize explicit keys commanding st.delete_documents.
  • Architectural Discovery — Browse registered core scopes applying st.list_engines and parse schema blueprints identifying object hierarchies with st.list_doc_types.
  • Search Analytics & CTR — Uncover real-world operational user conversion intent evaluating actual volume via st.analytics_top_searches and calculating active hit paths invoking st.analytics_top_clicks.

The Swiftype MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Swiftype to Cursor via MCP

Follow these steps to integrate the Swiftype MCP Server with Cursor.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using Swiftype

Open Agent mode in chat and ask: "Using Swiftype, help me...". 10 tools available

Why Use Cursor with the Swiftype MCP Server

Cursor AI Code Editor provides unique advantages when paired with Swiftype through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Swiftype + Cursor Use Cases

Practical scenarios where Cursor combined with the Swiftype MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Swiftype MCP Tools for Cursor (10)

These 10 tools become available when you connect Swiftype to Cursor via MCP:

01

st.analytics_top_clicks

Identify precise active arrays spanning native Hold parsing

02

st.analytics_top_searches

Inspect deep internal arrays mitigating specific Plan Math

03

st.create_documents

Enumerate explicitly attached structured rules exporting active Billing

04

st.delete_documents

json` eliminating cached pages permanently erasing bounds metrics from search. Dispatch an automated validation check routing explicit Gateway history

05

st.list_doc_types

json` extracting schema blueprints enforcing exact map types correctly. Retrieve explicit Cloud logging tracing explicit Vault limits

06

st.list_documents

json` dumping all stored metadata physically tracking IDs per document type. Irreversibly vaporize explicit validations extracting rich Churn flags

07

st.list_domains

json` verifying automated crawler limits mapped inside explicit index scopes. Identify precise active arrays spanning native Gateway auth

08

st.list_engines

json` extracting all active isolated Elastic indices bound per tenant. Identify bounded CRM records inside the Headless Swiftype Platform

09

st.post_search

json` firing raw queries into the specific Engine returning faceted JSON hierarchies. Perform structural extraction of properties driving active Account logic

10

st.post_suggest

json` bounding predictive keys and spelling tolerant matches decoupled from main indexing. Provision a highly-available JSON Payload generating hard Customer bindings

Example Prompts for Swiftype in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Swiftype immediately.

01

"List all my available Swiftype search engines, then run a search for 'documentation' on the most relevant one and show me the top 3 analytics clicks it generated last week."

02

"List all active engines in our Swiftype account."

03

"Run a test suggestion for 'passw' in the internal wiki engine."

Troubleshooting Swiftype MCP Server with Cursor

Common issues when connecting Swiftype to Cursor through the Vinkius, and how to resolve them.

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Swiftype + Cursor FAQ

Common questions about integrating Swiftype MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Connect Swiftype to Cursor

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.