Provider

A Provider is the underlying service or platform that an MCP tool interacts with to perform its tasks. The provider is typically an external SaaS API or a local data source.

Relationship to MCP

An MCP Server acts as the interface or "wrapper" around the Provider.

• Example: A "GitHub MCP Server" (Server) connects to the "GitHub API" (Provider) to list issues (Tool).

The distinction is important because one MCP server could potentially manage connections to multiple providers to satisfy a single user request.

Questions & Answers

What is a "Provider" in the MCP ecosystem?

A Provider is the underlying service or platform (e.g., Salesforce, Slack, or a local database) that an MCP tool connects to to fulfill a request. It is the original source of the data or capability.

How does an MCP server relate to a provider?

The MCP server acts as a standardized wrapper around the provider. It translates common JSON-RPC protocol messages into the specific API calls or queries required by the provider's unique interface.

Can one MCP server manage multiple providers?

Yes. A single MCP server can be designed to coordinate actions across multiple underlying providers to satisfy a complex user request, acting as a unified interface for several distinct services.