Completion (MCP)
What is Completion (MCP)?
Completion is a Model Context Protocol request, completion/complete, that lets a server offer IDE-like argument autocompletion for a prompt or a resource template's URI, returning up to 100 ranked suggestions per response. AdminKit's MCP gateway sits in the request path every call, including completion requests, passes through on its way to a server.
By AdminKit team, Netbase JSC · Updated
Completion, in the Model Context Protocol, is a request type — completion/complete — that lets a server offer argument autocompletion for a prompt or a resource template’s URI, the same kind of suggestion list an IDE shows while typing, within the protocol Anthropic introduced to standardize how applications feed context and tools to an LLM. Like every MCP message, completion/complete is a JSON-RPC 2.0 request, and the specification has servers answer failures — an unsupported capability, an unknown prompt name, a missing required argument — with standard JSON-RPC error codes. A client sends the argument’s name and the characters typed so far, naming which prompt or template it’s completing against, and for a request with more than one argument it can include previously-resolved values as context so later suggestions depend on earlier ones. A server that supports this declares the completions capability during initialization; its response returns a ranked array of suggested values, capped at 100 per response, with an optional total count and a flag for whether more matches exist beyond that cap. The specification recommends servers rate-limit these requests, since an endpoint that echoes back whatever matches a partial query can itself leak sensitive values.
Completion (MCP) is part of AdminKit’s AI agents & MCP cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
How many suggestions can an MCP completion response return?
Up to 100 ranked suggestions per response, with an optional total count and a flag for whether more matches exist beyond the cap.
What must a server declare to support completion?
The completions capability during initialization, before a client will send it completion/complete requests.
Why does the MCP specification recommend rate-limiting completion requests?
Because an endpoint that echoes back whatever matches a partial query can itself leak sensitive values if left unthrottled.