MCP connectors
Reusable integrations that connect an AI application to an external tool or data source over the Model Context Protocol, so the same connection works across any MCP-compatible client.
MCP connectors are packaged integrations that plug an AI application into an outside capability through the Model Context Protocol. Instead of writing custom glue for each tool, a client adds a connector and immediately gains its tools, resources, or prompts. Because the protocol is uniform, the same connector works across any MCP-compatible host, so the integration is written once and reused everywhere rather than rebuilt per application.
A connector is usually just an MCP server presented for easy installation: it advertises what it offers, handles its own authentication, and defines the behaviour behind each tool. Some connectors wrap a single service; others act as a gateway in front of many. The agent connects, lists what the connector exposes, and calls the pieces it needs, all inside its normal tool-calling loop.
Proxygate is a connector for buying API access: connect to it over MCP and an agent gets tools to search the catalogue, inspect an endpoint, check a balance, and make a paid call from one prepaid USDC balance, with each provider key injected server-side. MCP is only one way in, though. The same marketplace is reachable through the Proxygate SDK, the CLI, and a plain REST API, so a connector is the MCP-native option, not the only one.
References
Related concepts
MCP connectors: frequently asked questions
MCP connectors are reusable integrations that connect an AI application to an external tool or data source over the Model Context Protocol. A client adds a connector and gains its tools without custom glue, and the same connector works across any MCP-compatible host.
They are largely the same thing seen from different angles: a connector is an MCP server packaged for easy installation in a client. The server is the running endpoint; the connector is how a host adds and authenticates to it.
Yes. Connect to Proxygate over MCP and an agent gets tools to search the catalogue, price endpoints, check a balance, and make paid calls from one prepaid USDC balance. The same marketplace is also reachable via the Proxygate SDK, CLI, and REST API.