fastn-ai/fastn-mcp

**Give your AI agents and apps secure, governed access to your customers' tools and systems through one multi-tenant MCP endpoint.**
Part of Fastn, the embedded integration platform for SaaS products and AI agents. Fastn MCP Server is a production-ready Model Context Protocol (MCP) gateway that connects AI agents and apps to Slack, Jira, GitHub, Salesforce, HubSpot, Postgres, and 200+ more services, with fully managed auth, governed multi-tenant access, and sub-second execution.
Built on the Fastn SDK, this server exposes MCP tools that any compatible AI platform can use out of the box.
Why Fastn MCP Server?
| Feature | Description |
|---------|-------------|
| **250+ Connectors** | Slack, Jira, GitHub, Salesforce, HubSpot, Postgres, Stripe, Notion, Linear, and more |
| **MCP Native** | Works with Claude Desktop, Cursor, Lovable, Bolt, v0, and any MCP-compatible client |
| **Fully Managed Auth** | OAuth 2.1 for every connector, no token management, no app registration, no refresh handling |
| **Governed Access** | Role-based permissions, audit trails, and enterprise compliance controls |
| **SOC 2 Certified** | Enterprise-grade security and compliance built into the platform |
| **Sub-Second Execution** | Direct API calls through the Fastn platform with built-in caching and connection pooling |
| **Multiple Transports** | stdio (local), SSE, and Streamable HTTP for any deployment model |
| **Production Ready** | Docker support, health checks, structured logging, and OAuth 2.1 protected resource metadata |
| **Flow Automation** | Create, manage, and execute multi-step workflows that compose tools |
Quick Start
1. Sign up at app.fastn.ai
Create an account and connect your first connectors (Gmail, Slack, GitHub, etc.).
2. Connect your MCP client
**Hosted server (recommended)**, no installation needed:
Point any MCP client at this URL. Authentication is handled via MCP OAuth 2.1 automatically. See Client Configuration for Claude Desktop and Cursor examples.
**Self-hosted**, install and run your own instance:
Connecting to the MCP Server
Endpoints
Use the hosted server (mcp.live.fastn.ai) or your self-hosted instance. Each path exposes a different set of tools:
| Endpoint | Tools |
|----------|-------|
| /shttp | All 11 tools: find_tools, execute_tool, list_connectors, list_skills, list_projects, list_flows, run_flow, delete_flow, create_flow, update_flow, configure_custom_auth |
| /shttp/tools | 5 tools: find_tools, execute_tool, list_connectors, list_skills, list_projects |
| /shttp/tools/{project_id} | 4 tools: find_tools, execute_tool, list_connectors, list_skills |
| /shttp/tools/{project_id}/{skill_id} | 3 tools: find_tools, execute_tool, list_connectors |
| /sse, /sse/tools, etc. | Same pattern for SSE transport |
**Examples with the hosted server:**
Authentication
The MCP server supports three authentication methods. Get your credentials from app.fastn.ai.
MCP OAuth 2.1 (Recommended)
Standard MCP OAuth flow with PKCE. The server bridges to Fastn's identity provider automatically. Just point your client at the URL, you'll be prompted to authenticate:
Token / API Key
Pass a Fastn auth token or API key via the Authorization header in your MCP client config:
You can also pass x-project-id to scope requests to a specific project:
For local stdio transport, pass credentials as environment variables: