From c0c78ad412c36403ec70fae28f767dd0a756eaa5 Mon Sep 17 00:00:00 2001
From: ihrpr <inna@anthropic.com>
Date: Mon, 16 Jun 2025 15:04:23 +0100
Subject: [PATCH] add how to use Completions to the readme

---
 README.md | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)

diff --git a/README.md b/README.md
index 08b711c2..8d319f67 100644
--- a/README.md
+++ b/README.md
@@ -317,6 +317,32 @@ server.registerPrompt(
 );
 ```
 
+### Completions
+
+MCP supports argument completions to help users fill in prompt arguments and resource template parameters. See the examples above for [resource completions](#resources) and [prompt completions](#prompts).
+
+#### Client Usage
+
+```typescript
+// Request completions for any argument
+const result = await client.complete({
+  ref: {
+    type: "ref/prompt",  // or "ref/resource"
+    name: "example"      // or uri: "template://..."
+  },
+  argument: {
+    name: "argumentName",
+    value: "partial"     // What the user has typed so far
+  },
+  context: {             // Optional: Include previously resolved arguments
+    arguments: {
+      previousArg: "value"
+    }
+  }
+});
+console.log(result.completion.values); // ["suggestion1", "suggestion2", ...]
+```
+
 ### Display Names and Metadata
 
 All resources, tools, and prompts support an optional `title` field for better UI presentation. The `title` is used as a display name, while `name` remains the unique identifier.
@@ -870,6 +896,18 @@ const result = await client.callTool({
     arg1: "value"
   }
 });
+
+// Request completions
+const completions = await client.complete({
+  ref: {
+    type: "ref/prompt",
+    name: "example-prompt"
+  },
+  argument: {
+    name: "arg1",
+    value: "partial"
+  }
+});
 ```
 
 ### Proxy Authorization Requests Upstream