Your stack is never just one thing. Jira for issues, Notion for docs, GitHub for code, Supabase for data — whether you're a freelancer juggling client projects or a team spread across tools. MCP Express now includes tools from official provider repositories, so you can add Atlassian, Notion, GitHub, Nuclino, and Supabase integrations directly — and let your AI handle them instead of learning every tool yourself.
Supported Official Providers
The following providers are available today as upstream integrations in MCP Express:
- Atlassian — Jira and Confluence tools from Atlassian's official MCP repository
- Notion — Pages, databases, and search
- GitHub — Repositories, issues, pull requests, and more
- Nuclino — Workspace and item management
- Supabase — Database queries and project management
More providers will be added as their official MCP repositories become available.
Bring Your Own MCP Server
The supported providers cover the most common tools, but you're not limited to them. MCP Express includes an External MCP integration that lets you connect any MCP-compatible server — as long as it exposes an OAuth flow, you can bring it in.
All you need is the MCP server URL. Authentication, tool discovery, and access control all work the same way as with any official provider. If you've built your own MCP server, or a provider you use isn't on the supported list yet, External MCP is how you connect it.
Every provider exposes a range of tools — Atlassian alone covers Jira issue management, Confluence search, project administration, and more. When your AI loads all of those at once, most of them are irrelevant to any given task. That's context window noise the model has to work through on every request, and it compounds when you're pulling from multiple providers at the same time.
With MCP Express, you decide which tools from each provider to surface on your server. A workflow focused on Jira sprint management might only need issue creation, status updates, and sprint queries — not Confluence search, not Jira admin tools. A GitHub-heavy workflow might need pull request tools and issue tracking, with repository admin left out entirely.
You select the tools once during setup. Everything else stays excluded, and your AI works with a tighter, more purposeful toolset from the start — less noise in context means the model can reason over what's actually relevant more effectively.
Provider tools behave like any other tool on your MCP Express server. RBAC applies the same way — you assign roles, define which tools each role can invoke, and provider tools fall under that governance automatically.
In practice,, this means you can give a support rep read-only access to Jira issues without exposing Confluence or any write operations. A developer on the same server can have broader access — pull request tools, issue creation, sprint management — while an external collaborator sees only what they need for their specific task. The provider's tool definitions are fixed, but who can reach them on your server is entirely up to you.
This also means you can build role-based MCP servers tailored to specific tasks — a support server, a developer server, a data server — each with exactly the tools that role needs. Simpler access control, and a more focused context for the AI to work from.
If you're new to access control on MCP Express, Role-Based Access Control covers how roles and permissions work.
Adding a Provider Integration
Adding a provider works the same way as any other integration on MCP Express. Select the provider from the integrations list, authorise via OAuth, and the tools they expose become available for you to configure. From there, select which tools to surface on your server and assign them to the relevant roles.
Putting It All Together
Say your workflow spans Jira, Notion, and Supabase. Add all three from the integrations list, select the tools each team member actually needs, and they're all available on the same MCP Express server. Your AI can pull the open Jira ticket, check the relevant Notion spec, and query the Supabase table in one flow — same experience as any other integration you've set up.
Available with MCP Express. Get started today!
Add your first MCP Server →
Further Resources:
- Documentation — MCP Server configuration and supported providers.
- Contact Us — Questions before signing up? Drop us an email.
- Open a Support Ticket — Already inside the app and something's not working? Open a ticket directly from your dashboard.
