MCP Integration Hub
MCP Integration Hub
SaaS Factory supports the Model Context Protocol (MCP) — the open standard for connecting AI agents to external tools and data sources. The MCP Integration Hub lets you register any MCP-compatible server and make it available to agents across the entire autonomous pipeline.
Overview
Agents in SaaS Factory use a central tool layer (tools.ts) to interact with the outside world. The MCP Hub adds a pluggable registry on top of this layer. Instead of tools being hardcoded at the platform level, you can bring your own MCP servers — Notion, Linear, Datadog, Snowflake, Zapier, or any other MCP-compliant service — and agents will use them as first-class tools.
┌─────────────────────────────────────────────────┐
│ SaaS Factory Agents │
├─────────────────────────────────────────────────┤
│ Agent Tool Layer (tools.ts) │
├──────────────────┬──────────────────────────────┤
│ Built-in Tools │ MCP Registry (pluggable) │
│ (platform core) │ Notion · Jira · Datadog · … │
└──────────────────┴──────────────────────────────┘
Supported MCP Servers
The following servers are available at launch. Any MCP-compliant server can also be registered manually.
| Category | Servers |
|---|---|
| Project Management | Asana, Linear, Jira, Notion |
| Workflow Automation | Zapier |
| Observability | Datadog |
| Data Warehousing | Snowflake |
Setting Up an MCP Integration
1. Open the MCP Registry
Navigate to Settings → Integrations → MCP Hub in your SaaS Factory dashboard.
2. Add an MCP Server
Click Add Server and either:
- Select a server from the built-in catalogue, or
- Enter a custom MCP server endpoint URL for any MCP-compliant service.
3. Configure Credentials
Each server requires credentials (API keys, OAuth tokens, etc.). These are stored in the platform's environment variable manager and are never written to source code. For Vercel-deployed products, credentials are automatically synced to your Vercel project environment.
Server: Notion
Env var: NOTION_API_KEY
Value: secret_xxxxxxxxxxxx
Scope: All agents (or select specific agents)
4. Assign to Agents
Use per-agent tool scoping to control which agents can call which servers. For example:
- Feature Discovery Agent → Notion (read product wikis), Linear (read existing issues)
- Support Agent → Jira (create/update tickets), Datadog (query error rates)
- Data Agent → Snowflake (run analytical queries)
Agents that are not assigned a server cannot call it, even if the server is registered globally.
5. Test the Connection
Use the Test Connection button in the registry UI to verify that the server is reachable and credentials are valid before enabling it in the live pipeline.
How Agents Use MCP Tools
Once a server is registered and scoped, agents discover its available tools automatically via the MCP tool-listing protocol. No code changes are required. Tool calls made by agents to MCP servers follow the standard MCP request/response format:
// Example: agent calls a Notion MCP server to read a page
{
"method": "tools/call",
"params": {
"name": "notion_get_page",
"arguments": {
"page_id": "abc123"
}
}
}
Responses are returned to the agent in structured JSON and are treated identically to responses from built-in tools.
Security & Credential Management
- All MCP server credentials are stored in the existing env-vars system — the same store used for database URLs and third-party API keys.
- Credentials are injected at runtime and are never exposed in logs, PR diffs, or agent outputs.
- Vercel integration: credentials registered in the MCP Hub are automatically synced to the correct Vercel environment (preview / production).
- Access to the MCP Registry UI is restricted to users with the Admin or Developer role.
Adding a Custom MCP Server
Any server that implements the MCP specification can be registered:
- In the MCP Hub, click Add Custom Server.
- Provide the server's transport endpoint (HTTP/SSE or stdio).
- Optionally provide a display name and description for the registry listing.
- Add any required credentials as env-vars.
- Assign the server to agents and test the connection.
The platform does not restrict which MCP servers can be registered. If an MCP server exists for a tool your team uses, it can be connected.
Troubleshooting
| Issue | Resolution |
|---|---|
| "Connection failed" on test | Verify the server URL and check that credentials are correct and have not expired. |
| Agent not using a registered tool | Confirm the server is assigned to that specific agent under per-agent tool scoping. |
| Credential not synced to Vercel | Trigger a manual Vercel env-sync from Settings → Vercel Integration. |
| MCP server returns schema errors | Ensure the server implements a supported MCP protocol version. |