Skip to content

Define the MCP Capability Source contract #15

Description

@ian-pascoe

Question

How must an MCP Capability Source discover, retain, namespace, and invoke downstream tools, resources, templates, prompts, completion, and compatibility-era transport behavior while preserving opaque identifiers, pagination, negotiated capabilities, notifications, cancellation, progress, and source provenance?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions