Search the documentation
50 pages for historical.
Titles and paths first, then pages whose text carries it. Each row opens that page as this site last read it. Cut at 50, so a narrower query shows the rest.
Create an instance of the Claude API client
Claude Developer Platform · in the page
about-claude/use-case-guides/ticket-routing
…iarity with, your existing support ticketing system * A sample set of historical support tickets for testing ## Define whether to use Claude for ticket routing Here are some key indicators that you…
PDF Processing
Claude Developer Platform · in the page
agents-and-tools/agent-skills/best-practices
…o longer supported. </details> ``` The old patterns section provides historical context without cluttering the main content. ### Use consistent terminology Choose one term and use it throughout the…
advisor-tool
Claude Developer Platform · in the page
agents-and-tools/tool-use/advisor-tool
…ontains `advisor_tool_result` blocks. The request is accepted and the historical blocks are preserved; the model cannot call the advisor on that turn. You must still send the `advisor-tool-2026-03-01`…
Compliance API
Claude Developer Platform · in the page
api/compliance
…or path was updated. - `"platform_memory_version_redacted"` A historical version of an agent memory document was redacted. Redaction scrubs the stored content of a specific version while prese…
Activities
Claude Developer Platform · in the page
api/compliance/activities
…or path was updated. - `"platform_memory_version_redacted"` A historical version of an agent memory document was redacted. Redaction scrubs the stored content of a specific version while prese…
Query compliance activities
Claude Developer Platform · in the page
api/compliance/activities/list
…or path was updated. - `"platform_memory_version_redacted"` A historical version of an agent memory document was redacted. Redaction scrubs the stored content of a specific version while prese…
First request
Claude Developer Platform · in the page
manage-claude/claude-code-analytics-api
…` customers (Pro/Team plans). ### What's the data retention period? Historical Claude Code analytics data is retained and accessible through the API. There is no specified deletion period for this d…
compliance-org-data
Claude Developer Platform · in the page
manage-claude/compliance-org-data
…anization. Removed users are dropped from the list immediately. Their historical activity remains queryable through the Activity Feed for the full retention window, indexed by the same `user_...` ID.…
First request
Claude Developer Platform · in the page
manage-claude/usage-cost-api
…e Usage & Cost Admin API provides programmatic and granular access to historical API usage and cost data for your organization. This data is similar to the information available in the [Usage](https:/…
workspaces
Claude Developer Platform · in the page
manage-claude/workspaces
…lipsis menu (**...**) and select **Archive**. Archiving: * Preserves historical data for reporting * Deactivates the workspace and archives every API key created for it * Cannot be undone <Warning>…
DCF Model Rubric
Claude Developer Platform · in the page
managed-agents/define-outcomes
…ubric: ```markdown # DCF Model Rubric ## Revenue Projections - Uses historical revenue data from the last 5 fiscal years - Projects revenue for at least 5 years forward - Growth rate assumptions are…
memory
Claude Developer Platform · in the page
managed-agents/memory
…esponse schema. ### Redact a version Redact scrubs content out of a historical version while preserving the audit trail (who did what, when). Use it for compliance workflows such as removing leaked…
claude-sonnet-3-5
Claude Developer Platform · in the page
release-notes/system-prompts/claude-sonnet-3-5
…information about controversial topics and research areas, explaining historical atrocities, describing tactics used by scammers or hackers for educational purposes, engaging in creative writing that…
Explore the .claude directory
Claude Code CLI · in the page
claude-directory
…| Historical totals shown by `/usage`…
Configure your terminal for Claude Code
Claude Code CLI · in the page
terminal-config
…ing for this is usually labeled "Use Option as Meta Key"; Meta is the historical Unix name for the key now labeled Option or Alt. <Tabs> <Tab title="Apple Terminal"> Open Settings → Profiles →…
Design Principles
Model Context Protocol · in the page
community/design-principles
…r serves the ecosystem. This means accepting some inconsistency, some historical accidents, and some decisions we might make differently with hindsight. ## Standardization over innovation MCP standa…
SEP Guidelines
Model Context Protocol · in the page
community/sep-guidelines
…of the specification repository. Their revision history serves as the historical record of the feature proposal. ## When to Write a SEP The SEP process is reserved for changes that are substantial e…
Example Servers
Model Context Protocol · in the page
examples
…ervers that are no longer actively maintained. They are provided for historical reference only. ## Official integrations Visit the [MCP Servers Repository (Official Integrations section)](https://g…
SEP-1024: MCP Client Security Requirements for Local Server Installation
Model Context Protocol · in the page
seps/1024-mcp-client-security-requirements-for-local-server-
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1034: Support default values for all primitive types in elicitation schemas
Model Context Protocol · in the page
seps/1034--support-default-values-for-all-primitive-types-in
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1036: URL Mode Elicitation for secure out-of-band interactions
Model Context Protocol · in the page
seps/1036-url-mode-elicitation-for-secure-out-of-band-intera
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1046: Support OAuth client credentials flow in authorization
Model Context Protocol · in the page
seps/1046-support-oauth-client-credentials-flow-in-authoriza
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1302: Formalize Working Groups and Interest Groups in MCP Governance
Model Context Protocol · in the page
seps/1302-formalize-working-groups-and-interest-groups-in-mc
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1303: Input Validation Errors as Tool Execution Errors
Model Context Protocol · in the page
seps/1303-input-validation-errors-as-tool-execution-errors
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1319: Decouple Request Payload from RPC Methods Definition
Model Context Protocol · in the page
seps/1319-decouple-request-payload-from-rpc-methods-definiti
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1330: Elicitation Enum Schema Improvements and Standards Compliance
Model Context Protocol · in the page
seps/1330-elicitation-enum-schema-improvements-and-standards
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1577: Sampling With Tools
Model Context Protocol · in the page
seps/1577--sampling-with-tools
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1613: Establish JSON Schema 2020-12 as Default Dialect for MCP
Model Context Protocol · in the page
seps/1613-establish-json-schema-2020-12-as-default-dialect-f
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1686: Tasks
Model Context Protocol · in the page
seps/1686-tasks
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1699: Support SSE polling via server-side disconnect
Model Context Protocol · in the page
seps/1699-support-sse-polling-via-server-side-disconnect
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1730: SDKs Tiering System
Model Context Protocol · in the page
seps/1730-sdks-tiering-system
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1850: PR-Based SEP Workflow
Model Context Protocol · in the page
seps/1850-pr-based-sep-workflow
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-1865: MCP Apps - Interactive User Interfaces for MCP
Model Context Protocol · in the page
seps/1865-mcp-apps-interactive-user-interfaces-for-mcp
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2085: Governance Succession and Amendment Procedures
Model Context Protocol · in the page
seps/2085-governance-succession-and-amendment
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2106: Tools `inputSchema` & `outputSchema` Conform to JSON Schema 2020-12
Model Context Protocol · in the page
seps/2106-json-schema-2020-12
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2133: Extensions
Model Context Protocol · in the page
seps/2133-extensions
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2148: MCP Contributor Ladder
Model Context Protocol · in the page
seps/2148-contributor-ladder
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2149: MCP Group Governance and Charter Template
Model Context Protocol · in the page
seps/2149-working-group-charter-template
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2164: Standardize Resource Not Found Error Code
Model Context Protocol · in the page
seps/2164-resource-not-found-error
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2207: OIDC-Flavored Refresh Token Guidance
Model Context Protocol · in the page
seps/2207-oidc-refresh-token-guidance
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2243: HTTP Header Standardization for Streamable HTTP Transport
Model Context Protocol · in the page
seps/2243-http-standardization
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2260: Require Server requests to be associated with a Client request.
Model Context Protocol · in the page
seps/2260-Require-Server-requests-to-be-associated-with-Client-requests
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2322: Multi Round-Trip Requests
Model Context Protocol · in the page
seps/2322-MRTR
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2468: Recommend Issuer (iss) Parameter in MCP Auth Responses
Model Context Protocol · in the page
seps/2468-recommend-issuer-claim-for-auth
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2484: Require Conformance Tests for Standards Track SEPs to Reach Final Status
Model Context Protocol · in the page
seps/2484-conformance-tests-required-for-final-seps
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2549: TTL for List Results
Model Context Protocol · in the page
seps/2549-TTL-for-list-results
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2567: Sessionless MCP via Explicit State Handles
Model Context Protocol · in the page
seps/2567-sessionless-mcp
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2575: Make MCP Stateless
Model Context Protocol · in the page
seps/2575-stateless-mcp
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2577: Deprecate Roots, Sampling, and Logging
Model Context Protocol · in the page
seps/2577-deprecate-roots-sampling-and-logging
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…
SEP-2596: Specification Feature Lifecycle and Deprecation Policy
Model Context Protocol · in the page
seps/2596-spec-feature-lifecycle-and-deprecation
…iv> <Note> This SEP has reached Final status and is preserved as a historical record of the design as accepted. Changes made to the protocol after finalization are not reflected here. Refer to…