Docs / Reference
What every server supports
The MCP versions and features every Sokie server speaks, and how a server gets new ones.
Every Sokie server runs on the same runtime, so every server speaks the same versions of MCP and offers the same features, with nothing in your spec or tool files to change. When a release adds a version or a feature, a server gets it on its next deploy: a push, sokie deploy, or Redeploy on its Deploys tab. The server's Overview says when a newer runtime is out and what it brings; Redeploy without new code has the details.
Protocol versions
A server answers each of these at https://<slug>.sokie.cloud/mcp, and at any custom domain of yours:
2026-07-28. The client asks what the server speaks withserver/discover, then names the version on each request.2025-11-25,2025-06-18,2025-03-26,2024-11-05and2024-10-07, agreed withinitialize. A client that asks for a version not listed here gets2025-11-25.
How a server answers
Over Streamable HTTP: one POST to /mcp for each message, and a JSON answer to each. A server keeps no session and opens no stream of its own, so a client's GET to /mcp is refused, and so is a batch of several messages in one request. Who has to sign in, and how, is in How clients sign in.
Tools with hints
Every operation you keep is a tool, with a title and the hints clients use to decide when to ask before calling it: whether it only reads, whether it can delete, whether running it twice does the same as once, and whether it reaches past your API. Sokie sets them from what each operation does, and you can set each tool's risk yourself.
Asking the person
When a call needs the person's yes, because it's set to Ask first, or needs their own key or sign-in to your API, the server asks through their client. On 2026-07-28, a client that can show a form asks in place for a tool that reads or writes. Everything else is a link the client opens. A client that can do neither gets the link as text, for the agent to pass on.
Large APIs
Past 40 tools, sokie init and the New server page set "discovery": "search", and the server offers three tools instead of the whole list: searchTools, getToolDefinition and useTool. Many operations explains how search ranks.
Smaller answers
A tool's project: keeps only the fields an agent needs from your API's answer, before it reaches the agent. See Keep responses small.
Lists that page
A list tool whose file has page: ends each answer with a line saying how to get the next page, with the exact value to send, or that it was the last. sokie init writes it where the spec shows how the list pages, Link headers and Azure's next links included. See Lists that page.
Files and images
When your API answers with a file, the tool returns it: an image as MCP image content the agent can see, and any other file, such as a PDF, as an embedded resource with its bytes. Files up to 1 MiB are returned; for a larger one the agent is told its type and size. See Answers that are files.
Sending files
When an operation takes a file, such as an upload, the tool takes it from the agent as base64: a file part as content and an optional filename, and a body that is a file as the base64 string itself. Files in one call total up to 1 MiB. See Sending files.
Skills
A server hands its skills to clients that read MCP skills, as the server's own. Every other agent gets a readSkill tool that fetches them, unless you switch it off on the Skills tab.
Prompts and resources
The files in prompts/ and resources/ are served as MCP prompts and resources. See Prompts and resources.
Lists clients can keep
On 2026-07-28, a server's lists of tools, prompts and resources tell the client it may keep them for a minute. So for up to a minute after a deploy, a client can still show the list from before it.
Screens
Screens are in early access. Where a workspace has them on, a server draws tool answers as tables, cards and forms in agents that show MCP Apps screens (2026-01-26), and each answer carries its data as structured content beside the text. See Screens.
What servers don't do
- Send log messages to the client.
- Ask the client's model to write something for them (sampling).
- Tell a client when a resource changes (subscriptions).
- Declare an output schema for a tool. Answers are text, with structured content only where screens are on.