---
title: "MCP glossary"
description:
  "39 terms from MCP authentication and the protocol itself, each defined against the RFC or specification section it comes from."
canonicalUrl: "https://zuplo.com/learn/mcp/glossary"
sourceUrl: "https://zuplo.com/learn/mcp/glossary"
pageType: "other"
generatedAt: "2026-11-20"
---

# MCP glossary

> 39 terms from MCP authentication and the protocol itself, each defined against the RFC or specification section it comes from, and marked where the 2026-07-28 revision changed it.

Current as of MCP 2026-07-28.

## Index

Search by acronym, RFC number, or header name — every entry indexes all three. If what you have is a string a client printed at you rather than a word, use the [error reference](/learn/mcp/errors). Or [ask us about it](/support).

Each term links to the group page that defines it.

### A

- [**Audience**](/learn/mcp/glossary/authorization#aud) — The party a token is intended for. _Also written: aud claim · aud · token audience · audience validation failed_
- [**Authorization server metadata**](/learn/mcp/glossary/discovery#authorization-server-metadata) (ASM) — A JSON document, published by an authorization server, that lists its endpoints and capabilities: issuer, authorization_endpoint, token_endpoint, scopes_supported, and which registration mechanisms it supports. _Also written: RFC 8414 · oauth-authorization-server · AS metadata_

### C

- [**Client ID Metadata Documents**](/learn/mcp/glossary/credentials#cimd) (CIMD) — A registration mechanism in which the client's client_id is an HTTPS URL that resolves to a JSON document of its own metadata, so the authorization server fetches the client's details on demand instead of storing a registration. _Also written: client ID metadata document · client_id_metadata_document_supported · URL client_id · DCR replacement_

### D

- [**Deprecated, Removed, and Active**](/learn/mcp/glossary/governance#deprecated-vs-removed) — The feature lifecycle policy puts every specification feature in exactly one of three states. _Also written: deprecated · removed · feature lifecycle · deprecation policy · deprecated features registry · SEP-2596_
- [**Dynamic Client Registration**](/learn/mcp/glossary/credentials#dcr) (DCR) — A protocol, defined by RFC 7591, that lets a client register itself with an authorization server over HTTP and receive a client_id back, with no human in the loop. _Also written: RFC 7591 · registration_endpoint · dynamic client registration not supported_

### E

- [**Elicitation**](/learn/mcp/glossary/protocol#elicitation) — The mechanism by which a server asks for additional information from the user, through the client, while a request is in flight. _Also written: elicitation/create · ElicitResult · form mode · url mode_

### H

- [**HTTP+SSE transport**](/learn/mcp/glossary/transport#http-sse) — The original two-endpoint HTTP transport from the 2024-11-05 revision: the client opened an SSE stream with GET and posted messages to a separate endpoint the stream advertised. _Also written: HTTP+SSE · HTTP with SSE · SSE transport · old MCP transport · 2024-11-05 transport_

### I

- [**Identity Assertion JWT Authorization Grant**](/learn/mcp/glossary/credentials#id-jag) (ID-JAG) — An IETF draft profile of the JWT authorization grant that gives a client delegated access to a resource in another trust domain on behalf of a user, without a separate user-approval step at that domain's authorization server. _Also written: Cross-App Access · XAA · urn:ietf:params:oauth:token-type:id-jag · identity chaining_
- [**initialize handshake**](/learn/mcp/glossary/protocol#initialize) — The opening exchange of every MCP revision up to 2025-11-25: the client sent an initialize request carrying its protocol version and capabilities, the server replied with its own, and the client confirmed with a notifications/initialized. _Also written: initialize · notifications/initialized · MCP handshake · initialize request_
- [**Issuer identification**](/learn/mcp/glossary/authorization#iss) — RFC 9207 adds an iss parameter to the OAuth authorization response so a client can tell which authorization server issued the code it just received, and an authorization_response_iss_parameter_supported metadata flag to advertise it. _Also written: iss · iss parameter · RFC 9207 · authorization_response_iss_parameter_supported · mix-up attack_

### M

- [**MCP error codes**](/learn/mcp/glossary/protocol#error-codes) — MCP partitions the JSON-RPC implementation-defined error range: -32000 to -32019 is legacy, allocated by implementations before the policy existed, and -32020 to -32099 is reserved for the specification. _Also written: -32020 · -32021 · -32022 · -32002 · -32042 · HeaderMismatch · MissingRequiredClientCapability · UnsupportedProtocolVersion_
- [**Mcp-Method**](/learn/mcp/glossary/transport#mcp-method) — An HTTP header mirroring the JSON-RPC method field of the request body, required on all Streamable HTTP POST requests. _Also written: mcp method header · mirrored headers_
- [**Mcp-Name**](/learn/mcp/glossary/transport#mcp-name) — An HTTP header mirroring params.name or params.uri from the request body, required on tools/call, resources/read, and prompts/get requests. _Also written: mcp name header · tool name header_
- [**MCP-Protocol-Version**](/learn/mcp/glossary/transport#mcp-protocol-version) — The HTTP header that carries the protocol version on every Streamable HTTP POST, for example MCP-Protocol-Version: 2026-07-28. _Also written: protocol version header · unsupported protocol version_
- [**Mcp-Session-Id**](/learn/mcp/glossary/transport#mcp-session-id) — The HTTP header that carried a protocol-level session identifier in the 2025-03-26 through 2025-11-25 revisions. _Also written: mcp session id header · MCP session · no valid session ID provided_
- [**_meta**](/learn/mcp/glossary/protocol#meta) — A reserved field on MCP requests, results, and notifications that carries metadata rather than payload. _Also written: io.modelcontextprotocol/protocolVersion · clientCapabilities · clientInfo · serverInfo · meta field_
- [**Multi Round-Trip Requests**](/learn/mcp/glossary/protocol#mrtr) (MRTR) — The pattern that replaced server-initiated requests in 2026-07-28. _Also written: InputRequiredResult · resultType · input_required · inputRequests · inputResponses_

### O

- [**Official extension**](/learn/mcp/glossary/governance#official-extensions) — An optional addition to the specification that defines capability beyond the core protocol, identified as {vendor-prefix}/{extension-name}. _Also written: official extensions · MCP extensions · io.modelcontextprotocol/ui · io.modelcontextprotocol/tasks · io.modelcontextprotocol/oauth-client-credentials · io.modelcontextprotocol/enterprise-managed-authorization · MCP Apps · extensions capability_
- [**OPTIONAL authorization**](/learn/mcp/glossary/authorization#optional-authorization) — The MCP specification states that authorization is OPTIONAL for implementations, and that HTTP-based implementations SHOULD — not MUST — conform to its OAuth profile when they do support it. _Also written: authorization is optional · MCP API key auth · custom header auth MCP · is API key authentication allowed in MCP · out of scope_

### P

- [**Prompt**](/learn/mcp/glossary/protocol#prompt) — A server-defined, optionally parameterized template of structured messages and instructions for interacting with a language model, listed with prompts/list and resolved with prompts/get. _Also written: prompts/get · prompts/list · MCP prompt · user-controlled_
- [**Proof Key for Code Exchange**](/learn/mcp/glossary/credentials#pkce) (PKCE) — An extension to the OAuth authorization code flow that stops a stolen authorization code from being redeemed by anyone else. _Also written: RFC 7636 · code_challenge · code_verifier · S256_
- [**Protected resource metadata**](/learn/mcp/glossary/discovery#protected-resource-metadata) (PRM) — A JSON document, published by a protected resource, that names the authorization servers able to issue tokens for it. _Also written: RFC 9728 · oauth-protected-resource · resource metadata_
- [**Protocol revision**](/learn/mcp/glossary/governance#protocol-revision) — MCP versions are dates in YYYY-MM-DD form, naming the last date on which backward-incompatible changes were made. _Also written: MCP version · 2026-07-28 · protocol version · Draft Current Final_

### R

- [**Resource**](/learn/mcp/glossary/protocol#mcp-resource) — Data a server exposes to give a language model context — files, database schemas, or application-specific information — each identified uniquely by a URI and read with resources/read. _Also written: resources/read · resources/list · MCP resource · application-driven_
- [**Resource indicators**](/learn/mcp/glossary/authorization#resource) — RFC 8707 defines a resource request parameter that names the target service a token is being requested for, so the authorization server can audience-restrict the token it issues. _Also written: RFC 8707 · resource parameter · resource indicator missing or unknown · canonical server URI_
- [**Roots**](/learn/mcp/glossary/protocol#roots) — Filesystem locations a client tells a server it considers relevant, each identified by a file:// URI. _Also written: roots/list · MCP roots · filesystem roots · workspace roots_

### S

- [**Sampling**](/learn/mcp/glossary/protocol#sampling) — The mechanism by which a server asks the client to run a language model completion on its behalf, so the client keeps control of model access, selection, and cost, and the server needs no model API key of its own. _Also written: sampling/createMessage · MCP sampling · server requests completion_
- [**Scope**](/learn/mcp/glossary/authorization#scope) — The OAuth mechanism for expressing what an access token is allowed to do. _Also written: scopes_supported · insufficient_scope · 403 insufficient scope · step-up authorization_
- [**server/discover**](/learn/mcp/glossary/discovery#server-discover) — A method that returns a server's supported protocol versions, capabilities, and identity in a single request. _Also written: DiscoverResult · mcp discover method · supportedVersions_
- [**Specification Enhancement Proposal**](/learn/mcp/glossary/governance#sep) (SEP) — A SEP is a design document that describes a new feature for MCP or for its processes, and it is the mechanism required for any protocol change, breaking change, or governance change. _Also written: SEP-2575 · SEP-2322_
- [**Statelessness**](/learn/mcp/glossary/transport#statelessness) — MCP is a stateless protocol as of the 2026-07-28 revision. _Also written: stateless · stateless MCP · sessions removed · MCP is stateless_
- [**stdio**](/learn/mcp/glossary/transport#stdio) — The transport in which the client launches the MCP server as a subprocess and the two exchange newline-delimited JSON-RPC messages over the subprocess's standard input and output. _Also written: standard input output transport · local MCP server_
- [**Streamable HTTP**](/learn/mcp/glossary/transport#streamable-http) — The HTTP transport for MCP, introduced in the 2025-03-26 revision. _Also written: streamable http transport · MCP endpoint · remote MCP transport_
- [**subscriptions/listen**](/learn/mcp/glossary/transport#subscriptions-listen) — A long-lived request that opens a server-to-client notification stream filtered to the event types the client names. _Also written: resources/subscribe · MCP notifications stream · subscriptionId_

### T

- [**Token exchange**](/learn/mcp/glossary/authorization#token-exchange) — An OAuth grant, defined by RFC 8693, in which a client presents one token and receives a different one with a different audience, subject, or scope. _Also written: RFC 8693 · urn:ietf:params:oauth:grant-type:token-exchange · subject_token · delegation · impersonation_
- [**Token passthrough**](/learn/mcp/glossary/authorization#token-passthrough) — The anti-pattern in which an MCP server accepts a token from a client without validating that it was issued to the MCP server, then passes it through to a downstream API. _Also written: forwarding access tokens · confused deputy_
- [**Tool**](/learn/mcp/glossary/protocol#tool) — A named, schema-described capability a server exposes so that a language model can interact with an external system. _Also written: tools/call · tools/list · MCP tool · model-controlled_

### W

- [**WWW-Authenticate**](/learn/mcp/glossary/discovery#www-authenticate) — The HTTP response header field a server uses to challenge a client for credentials, defined by RFC 9110 and given its Bearer-scheme parameters by RFC 6750. _Also written: www authenticate header · 401 challenge · resource_metadata · Bearer challenge_

### X

- [**x-mcp-header**](/learn/mcp/glossary/transport#x-mcp-header) — An extension property a server puts on a parameter inside a tool's inputSchema to have the client mirror that parameter's value into an HTTP header named Mcp-Param-{Name}. _Also written: Mcp-Param · custom headers from tool parameters · tool parameter header_

## Pairs that get mixed up

Each of these is two things, and knowing which one you have is usually the whole diagnosis.

- **PRM versus ASM** — Two different documents, published by two different parties. The resource says which authorization servers can issue tokens for it; the authorization server says where its own endpoints are.
- **DCR versus CIMD** — Both get a client an identity with no human involved. DCR stores a registration at the authorization server; CIMD uses an HTTPS URL as the client ID and is fetched on demand, so nothing is stored and the ID is portable.
- **Resource indicators versus Audience** — The `resource` parameter is what the client asks for; the audience is what the issued token carries and what the server checks. An identity provider that ignores `resource` still issues a token — with the wrong audience.
- **Mcp-Session-Id versus Statelessness** — Not a rename. Protocol-level sessions were deleted, so state that has to outlive a request is now an explicit handle passed in tool arguments rather than a header the transport tracks.

## Browse a whole area

These read in the order a request does: find the authorization server, pick a transport, get a credential, have it checked, then the surface that credential buys, then the process that changes all of it.

- [Discovery](/learn/mcp/glossary/discovery) (4 terms) — How a client finds out where to authenticate, starting from a 401 it did not expect.
- [Transport and headers](/learn/mcp/glossary/transport) (10 terms) — How MCP messages travel, and the headers the 2026-07-28 revision added, changed, or dropped.
- [Credentials and registration](/learn/mcp/glossary/credentials) (4 terms) — How a client obtains a client identity and an access token before it calls anything.
- [Authorization and tokens](/learn/mcp/glossary/authorization) (7 terms) — What a server checks on the token it receives, and what it must refuse to do with it.
- [Protocol surface](/learn/mcp/glossary/protocol) (10 terms) — The primitives a server exposes, the shape of a result, and the error codes MCP defines.
- [Versions and governance](/learn/mcp/glossary/governance) (4 terms) — How revisions are numbered, how features are retired, and how any of it changes.

## Next steps

One place to enforce all of this: discovery documents, audience binding, token validation, and the 2026-07-28 headers are the same work on every MCP server. A gateway in front of them does it once.

- [Request a free trial](/contact?interest=free-trial)
- [Read the Docs](https://zuplo.com/docs/mcp-gateway/code-config/overview)
- [Back to Learn MCP](/learn/mcp)
