Skip to main content
Quick summary
Connect https://developer.suki.ai/mcp to Cursor, VS Code, Claude, Claude Code, Codex, or similar tools. Agents can search the docs, read pages from a virtual filesystem, and submit documentation feedback. The server does not call Suki product APIs on your behalf.
Last updated:August 2026
The Suki developer documentation is available as a hosted search MCP server (Model Context Protocol). Connect it to your AI code editor or assistant (Cursor, VS Code, Claude, Claude Code, Codex, and similar tools) while you work in your local environment. When the connection is active, the model can search published guides, API reference, and SDK docs during a response, instead of relying only on training data or a generic web search. For the contextual menu, copy options, and one-click AI integrations on every page, use AI-optimized documentation. When you connect Documentation MCP well, it helps you to:
  • Find integration answers in the current published docs.
  • Pull full page Markdown into the chat when a snippet is not enough for an answer.
  • Discover agent skills that Suki developer documentation exposes as MCP resources, without a separate install step for discovery.
  • Report incorrect or confusing docs back to the Suki docs team from the agent.
What this server does not do
  • It does not execute any product APIs on your behalf.
  • It does not replace Partner Token or Suki Token authentication for those APIs.

​
Key benefits

Accelerate Your Development

Use the documentation as an MCP service in your AI code editor to assist coding and integration tasks.

Improve Your LLM's Responses

Retrieve information from the documentation in your AI code editor to improve response accuracy.

Reduce Manual Research

Reduce the need for manual research and documentation lookup.

Reduce LLM Hallucinations

Ground responses in current documentation instead of invented endpoints or SDK patterns.

​
MCP server URL

Use the following URL as the custom connector endpoint:
You can copy this URL from the Documentation MCP dropdown in the top navigation bar, from Copy MCP server URL in the contextual menu on any page, or from the configuration snippets below. Agents and tools can also discover the server from https://developer.suki.ai/.well-known/mcp (and /.well-known/mcp.json). Prefer the public URL above when you configure a client by hand. The screenshot below shows the Documentation MCP dropdown in the top navigation bar:
Documentation MCP dropdown in the top navigation bar with install and copy actions for Cursor, VS Code, CLI tools, and MCP URL
The panel lists one-click install actions for Cursor and VS Code, plus copy actions for CLI tools (Claude Code, Codex, Gemini CLI, and others). CLI options show a CLI badge. Use Copy MCP URL for tools that need the endpoint only.

​
How the MCP server works

When an AI application connects to the Suki documentation MCP server, it can search indexed site content and retrieve full pages as Markdown while it answers your prompt. That keeps answers aligned with what is published on developer.suki.ai.
  • AI applications can search proactively while generating a response, even if you did not ask them to search.
  • They choose which tool to call from conversation context and relevance to Suki docs.
  • Each tool call runs during generation, so the model can use up-to-date documentation.
Some AI tools support both MCP and skills. MCP gives access to your content. Skills instruct agents how to use that content. Connecting this MCP server also exposes published skill resources for discovery. For product prompts and skill URLs, refer to AI coding tools.

​
MCP server tools

When you connect the Suki developer documentation MCP server, agents can use three tools:
  1. Search: Searches across the site and returns snippets with titles and links. Use this to discover information or find pages that match a query.
  2. Query docs filesystem: Reads and navigates a virtual documentation filesystem with shell-style commands (rg, head, cat, tree, and similar). Use this to browse structure, pull exact sections, or read one or more full pages in a single call.
  3. Submit feedback: Reports a documentation issue when a page is incorrect, outdated, confusing, or incomplete. The agent supplies the page path and a description. Mintlify records that as unhelpful feedback for the docs team.
Agents decide when to use each tool. A typical flow is search first, then query docs filesystem for the best matches. If the agent finds a problem in the page, it can submit feedback.
The documentation MCP server is read-only for content retrieval, plus optional feedback. It does not call Suki product APIs, mutate your integration, or access private partner data.

​
MCP resources

The search MCP server also exposes published skill.md files as MCP resources. Connected agents can discover and read those skill descriptions without installing skills separately. For install commands and product skills, see AI-optimized documentation and AI coding tools.

​
Search parameters

The search tool supports optional parameters that AI applications may apply when your site has matching filters:
Suki developer documentation is primarily a single public English site. Your AI tool decides whether to pass these filters based on the conversation.

​
How to set up MCP integration

Open MCP Settings in Cursor

  1. Use Command + Shift + P on Mac or Ctrl + Shift + P on Windows to open the command palette.
  2. Search for Open MCP settings and select Add custom MCP. This opens mcp.json.
  3. Add the following configuration:
Or select Connect to Cursor from the contextual menu on any documentation page, or use Install in Cursor from the Documentation MCP dropdown.
Use the Documentation MCP dropdown in the top navigation bar to copy these snippets without retyping URLs or JSON.

​
Test your connection

After configuration, ask your AI tool:
You should see Suki documentation tools for search, query docs filesystem, and submit feedback. Then try:
The AI should search and return relevant documentation pages. If it needs full page text, it can use query docs filesystem on the matching paths.

​
Using multiple MCP servers

You can connect several MCP servers in one AI tool. Connected servers do not inject content until the model calls a search or read tool. Best practices:
  • Connect only the MCP servers relevant to your current work.
  • Be specific in prompts so the model searches the most relevant server.
  • Disconnect servers you are not using to reduce context usage.

​
Troubleshooting

Verify the URL is exactly https://developer.suki.ai/mcp. Check your internet connection and restart your AI tool after configuration.
Confirm the MCP server was added correctly. Try removing and re-adding the server configuration. Check your AI tool’s MCP support documentation. Tool names can be site-specific; ask the model which tools it has after connect.
Try different or more general search terms (for example, “webhook” instead of “session completion webhook payload”). Verify the MCP connection is active. Hidden or noindex pages are not available through search MCP.
If the MCP server returns HTTP 429 Too Many Requests, wait and retry. Mintlify applies per-user and per-site hourly limits on search and filesystem tools. Most clients recover automatically within an hour.

​
Additional context for AI tools

Use these URLs when an AI tool needs broader context than a single page:

​
Install skills from the MCP server

Use the following command to install every published skill that Suki developer documentation exposes as MCP resources:
You can also install the skill for a specific product from that product’s workflow or modality index hub. On hubs such as Ambient Clinical Notes, Form filling, Dictation, Patient Summary, Audio Streaming, Webhooks, and the SDK or API overview pages, an Install Skill control appears next to the page title. Open it to copy or run npx skills add for the skill that matches that hub. The screenshot below shows Install Skill on the Patient Summary index hub, including the skill version on the control:
Patient Summary index hub with Install Skill control showing New v2.4 next to the page title
The control shows the published skill version (for example v2.4). When the hub marks the skill as New or Updated, reinstall that skill so your editor gets the latest copy. Run the command from Install Skill again, or reconnect the documentation MCP server and ask your agent to install or refresh the latest skills.

​
Next steps

AI-optimized documentation - Contextual menu and copy options on every page. AI coding tools - Product prompts and skill URLs. Quickstart - Getting-started path, including AI coding prompts.
Last modified on August 20, 2026