Source control MCP
Repository, issue, pull-request, code-search, and project workflows exposed to AI clients.
Explore common MCP server categories and understand how Model Context Protocol connects AI clients with tools, resources, and external context.
MCP is the interoperability layer in the AI stack. A server exposes tools, resources, or prompts through a common protocol; a client decides how those capabilities appear inside an AI workflow.
Browse
6 entries
Repository, issue, pull-request, code-search, and project workflows exposed to AI clients.
Structured access to database schemas, queries, metadata, and data workflows with scoped permissions.
Browser automation, page inspection, navigation, and web research capabilities for agent workflows.
Expose files, documents, folders, or knowledge resources to clients through a controlled context layer.
Connect messaging, support, collaboration, and notification systems to repeatable agent tasks.
Cloud, deployment, logs, observability, and operations capabilities exposed to development agents.
An MCP server exposes tools, resources, or prompts through the Model Context Protocol so compatible AI clients can discover and use them through a standard interface.
No. MCP exposes capabilities and context. A skill defines repeatable task behavior: the steps, constraints, validation, and expected output. A skill can call tools exposed by MCP.
Not automatically. MCP standardizes capability access, while a plugin can package authentication, permissions, product-specific workflows, and user experience around one or more integrations.