Markdown source

Model Context Protocol

Overview

Model Context Protocol, or MCP, is a standard pattern for connecting AI applications to tools, data, and interactive capabilities through structured servers and clients. In this wiki it also includes MCP Apps and agent-facing interfaces that expose richer actions or UI surfaces to models.

Conference Context

MCP emerged from the need to standardize how AI clients discover and call tools, access resources, and integrate with external systems. It sits in the lineage of plugin APIs, language-server style tooling, RPC, browser extensions, and developer-tool protocols.

Significance

Agents are only as useful as the tools and context they can safely access. MCP reduces one-off integrations, gives tool providers a common surface, and helps clients reason about capabilities, permissions, and interaction patterns.

Applied Use

Define focused MCP servers with clear tools, schemas, resources, and permission boundaries. Keep tool names concrete, return structured results, test with inspectors, and design for least privilege. For MCP Apps, treat UI and iframe boundaries as part of the security and product contract.

MCP is useful in IDEs, desktop assistants, enterprise data connectors, browser agents, design tools, developer platforms, and internal operations systems.

Use MCP when multiple AI clients need access to the same tools or when a tool provider wants a standard agent-facing integration. For a single narrow app, direct APIs may be simpler until reuse or interoperability matters.

Define focused MCP servers with clear tools, schemas, resources, and permission boundaries. Keep tool names concrete, return structured results, test with inspectors, and design for least privilege. For MCP Apps, treat UI and iframe boundaries as part of the security and product contract.

MCP is useful in IDEs, desktop assistants, enterprise data connectors, browser agents, design tools, developer platforms, and internal operations systems.

Use MCP when multiple AI clients need access to the same tools or when a tool provider wants a standard agent-facing integration. For a single narrow app, direct APIs may be simpler until reuse or interoperability matters.

Define focused MCP servers with clear tools, schemas, resources, and permission boundaries. Keep tool names concrete, return structured results, test with inspectors, and design for least privilege. For MCP Apps, treat UI and iframe boundaries as part of the security and product contract.

MCP is useful in IDEs, desktop assistants, enterprise data connectors, browser agents, design tools, developer platforms, and internal operations systems.

Use MCP when multiple AI clients need access to the same tools or when a tool provider wants a standard agent-facing integration. For a single narrow app, direct APIs may be simpler until reuse or interoperability matters.

Define focused MCP servers with clear tools, schemas, resources, and permission boundaries. Keep tool names concrete, return structured results, test with inspectors, and design for least privilege. For MCP Apps, treat UI and iframe boundaries as part of the security and product contract.

MCP is useful in IDEs, desktop assistants, enterprise data connectors, browser agents, design tools, developer platforms, and internal operations systems.

Use MCP when multiple AI clients need access to the same tools or when a tool provider wants a standard agent-facing integration. For a single narrow app, direct APIs may be simpler until reuse or interoperability matters.

Define focused MCP servers with clear tools, schemas, resources, and permission boundaries. Keep tool names concrete, return structured results, test with inspectors, and design for least privilege. For MCP Apps, treat UI and iframe boundaries as part of the security and product contract.

MCP is useful in IDEs, desktop assistants, enterprise data connectors, browser agents, design tools, developer platforms, and internal operations systems.

Use MCP when multiple AI clients need access to the same tools or when a tool provider wants a standard agent-facing integration. For a single narrow app, direct APIs may be simpler until reuse or interoperability matters.

Define focused MCP servers with clear tools, schemas, resources, and permission boundaries. Keep tool names concrete, return structured results, test with inspectors, and design for least privilege. For MCP Apps, treat UI and iframe boundaries as part of the security and product contract.

MCP is useful in IDEs, desktop assistants, enterprise data connectors, browser agents, design tools, developer platforms, and internal operations systems.

Use MCP when multiple AI clients need access to the same tools or when a tool provider wants a standard agent-facing integration. For a single narrow app, direct APIs may be simpler until reuse or interoperability matters.

Connections

Evidence Graph

Transcript-backed resources

Quote signals

Transcript-backed resources

Quote signals

Transcript-backed resources

Quote signals

Transcript-backed resources

Quote signals

Transcript-backed resources

Quote signals

Transcript-backed resources

Quote signals

This evidence graph consolidates scheduled talks, linked videos, transcripts, and slide-derived material connected to this topic.

Linked Sessions

Media Signals

Source Coverage

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

| Evidence type | Count | Review note |
| --- | ---: | --- |
| other | 53 | Related pages outside the main evidence categories. |
| resources | 22 | Video/resource pages; check source status before treating as primary event evidence. |
| slides | 11 | OCR or reconstructed slide evidence; mark claims as OCR-derived unless image-reviewed. |
| talks | 24 | Official schedule pages; use for titles, speakers, tracks, and stated talk framing. |
| tools | 3 | Derived inventory pages; use as entity context, not independent proof. |
| transcripts | 1 | Transcript markdown; check session matching and caption quality. |

Talks

Resources

Slides

Transcripts

Tools

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

| other | 55 | Related pages outside the main evidence categories. |
| resources | 23 | Video/resource pages; check source status before treating as primary event evidence. |
| talks | 27 | Official schedule pages; use for titles, speakers, tracks, and stated talk framing. |

Talks

Resources

Slides

Transcripts

Tools

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

| other | 61 | Related pages outside the main evidence categories. |
| resources | 25 | Video/resource pages; check source status before treating as primary event evidence. |
| talks | 29 | Official schedule pages; use for titles, speakers, tracks, and stated talk framing. |

Talks

Resources

Slides

Transcripts

Tools

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

Talks

Resources

Slides

Transcripts

Tools

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

Talks

Resources

Slides

Transcripts

Tools

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

Talks

Resources

Slides

Transcripts

Tools

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

| other | 62 | Related pages outside the main evidence categories. |
| resources | 26 | Video/resource pages; check source status before treating as primary event evidence. |
| talks | 30 | Official schedule pages; use for titles, speakers, tracks, and stated talk framing. |

Talks

Resources

Slides

Transcripts

Tools

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

| other | 63 | Related pages outside the main evidence categories. |
| resources | 27 | Video/resource pages; check source status before treating as primary event evidence. |
| talks | 31 | Official schedule pages; use for titles, speakers, tracks, and stated talk framing. |

Talks

Resources

Slides

Transcripts

Tools

This table summarizes the local evidence already linked from this topic. It is a navigation aid, not a claim that every linked page has been fully reviewed.

| other | 64 | Related pages outside the main evidence categories. |
| resources | 28 | Video/resource pages; check source status before treating as primary event evidence. |
| talks | 32 | Official schedule pages; use for titles, speakers, tracks, and stated talk framing. |

Talks

Resources

Slides

Transcripts

Tools

Active Use Cases