MCP Server Integration & Plugin Marketplace

SaaS Factory v1.0.161 introduces native support for the Model Context Protocol (MCP) — an open standard for connecting AI agents to external tools — along with a Plugin Marketplace for browsing and managing MCP server connections.

What is MCP?

Model Context Protocol (MCP) is an open standard that defines how AI models and agents communicate with external tools and data sources. Rather than hardcoding each integration, an MCP-compatible host (like SaaS Factory) can connect to any MCP server at runtime and immediately expose its tools to agents.

This means:

No platform code changes are required to add a new tool.
Any MCP server — public, third-party, or your own — can be plugged in.
All agents in the platform can access registered tools based on their permission scope.

Supported MCP Servers

SaaS Factory ships with pre-configured connectors for 200+ MCP servers. A selection of supported services:

Category	Services
Project Management	Asana, Linear, Notion
Automation	Zapier
Documentation	Confluence
Observability	Datadog, Sentry
Data & Analytics	Snowflake

The full list is available in the Plugin Marketplace.

Plugin Marketplace

The Plugin Marketplace is accessible from your workspace settings under Integrations → Plugin Marketplace.

Installing a Plugin

Navigate to Settings → Integrations → Plugin Marketplace.
Search or browse available MCP servers.
Click Install on the server you want to add.
Provide the required credentials or endpoint configuration for the server.
Click Save & Connect. The server is now available to all agents in your workspace.

Connecting a Custom MCP Server

If you have an internal API or proprietary tool you want agents to access:

Implement the MCP server spec in your service.
In the Marketplace, click Add Custom Server.
Enter your server's MCP endpoint URL and any required auth headers.
Click Test Connection to verify reachability.
Click Save. Your custom tools will be discoverable by agents immediately.

Managing Installed Plugins

View all installed plugins under Settings → Integrations → Installed.
Each plugin shows its connection status, last-used timestamp, and the agents that have accessed it.
Plugins can be disabled or removed without affecting core platform functionality.

Workspace Isolation

Plugin configurations are per-workspace. Installing a plugin in one workspace does not affect other workspaces in your account. This allows different teams to maintain different tool sets without cross-contamination.

Agent Compatibility

All SaaS Factory agents that previously relied on the hardcoded agent-tools.ts registry can now access MCP-registered tools alongside the built-in GitHub, Anthropic, Vercel, Neon, and Stripe integrations. The built-in integrations remain first-class and are unaffected by this change.

Agents discover available tools from the MCP registry at task-execution time. If a tool is available and the agent determines it is relevant to the current task, it will use it automatically — no additional configuration is required beyond installation.

Architecture Notes

The MCP bridge is a runtime adapter layer between agent task execution and external MCP servers.
Previously, all tool implementations lived in a single agent-tools.ts file (~41KB). Third-party and customer-specific tools are now registered dynamically via the MCP registry instead.
SaaS Factory is model-agnostic and interface-agnostic by design; MCP extends this to tool-agnosticism as well.

Troubleshooting

Connection test fails for a custom server

Confirm the server URL is publicly reachable from SaaS Factory's infrastructure (or configure network allowlisting).
Check that auth headers are formatted correctly for your MCP server implementation.
Review MCP server logs for handshake errors.

Agent is not using an installed tool

Verify the plugin is shown as Connected (not just Installed) in the Marketplace.
Confirm the tool's capability description in the MCP server manifest is clear — agents use semantic descriptions to determine relevance.
Ensure the workspace the agent is running in has the plugin installed.

Plugin was removed but agent still references it

Agents cache the tool registry for the duration of an active task. The change will take effect on the next task execution.