Skip to main content
MCP (Model Context Protocol) connectors let Proliferate agents call tools from external services — querying databases, scraping websites, managing tasks, and more — all through the Model Context Protocol.

​
What Are MCP Connectors

MCP is an open standard for connecting AI agents to external tools and data sources. When you add an MCP server to Proliferate, agents in your organization can discover and call the tools it exposes. This means you can give agents access to any service that speaks MCP — whether it is a managed connector from the list below or a custom server you build and host yourself.

​
Available Connectors

Proliferate includes preset configurations for popular MCP servers. Select any of these to add them to your organization.

Context7

Up-to-date library docs and code examples

PostHog

Query analytics, feature flags, and errors

Firecrawl

Web scraping and crawling for LLM-ready content

Neon

Manage serverless Postgres databases and branches

Stripe

Manage payments, customers, and subscriptions

Zapier

Automate workflows across 8,000+ apps

Supabase

Manage databases, auth, storage, and edge functions

Asana

Manage tasks, projects, and workflows

Semgrep

Static analysis and security scanning

DeepWiki

Query documentation for open-source repos

Apify

Web scraping and data extraction at scale

Playwright

Browser automation (self-hosted)

​
Adding a Custom MCP Server

You can connect any remote MCP server that exposes an HTTP endpoint. This lets you integrate internal tools, proprietary services, or any MCP-compatible server not in the preset list.
1

Get the Server URL

Your MCP server must be accessible over HTTP. This can be a public URL or an internal endpoint reachable from your Proliferate deployment.
2

Open Integrations

Navigate to Settings > Integrations in the dashboard.
3

Add Custom Server

Click Add MCP Server, enter the server URL and any required authentication headers, then save.
Custom MCP servers must implement the MCP protocol over HTTP (streamable HTTP transport). See the MCP specification for implementation details.

​
Custom Webhooks

You can also connect internal tools and event sources via webhook events. This is useful for systems that can send HTTP requests but do not implement the full MCP protocol. Common use cases:
  • Internal alerting systems
  • Deployment notifications
  • Support tools and inboxes
  • Any event source that can send a webhook
Webhooks and custom MCP servers can be combined. Use webhooks for triggering automations and MCP servers for giving agents tool access.