How to Connect Claude, ChatGPT, and Cursor to Company Apps for a Whole Team

Last updated ·Reviewed by Karim Rahme·Read as Markdown
Answer

Connect the apps once in an MCP gateway rather than in each assistant. Set up the integrations your team needs, allow them for the team's group, and have each person sign in and connect their own account. Each person then adds one MCP URL to Claude, ChatGPT, Cursor, or Copilot, and the same approved tools appear in all of them. With Metorial, that URL is a Magic MCP URL, and every call is logged with the person it ran for.

Every major AI assistant now supports the Model Context Protocol, so the hard part is no longer whether Claude can reach Salesforce. It is doing it for twenty people across three assistants without twenty sets of API keys.

If your team is
Use
One person testing one app
A local MCP server in that assistant
Several people sharing the same apps
A gateway with per-user sign-in
Using more than one assistant
A gateway, so one URL works in all of them
Including people who do not write code
A gateway with a portal instead of config files

Why not configure each assistant directly?

It works for one person. For a team, each person adds each server to each assistant, and most servers expect an API key in a config file. That is one setup per person per app per assistant, and keys end up copied between laptops.

How do you connect them?

1. Set up the integrations once. In Metorial, add the apps the team needs from the 1,000+ integrations, and choose which of each app's tools to expose. Start with read tools.

2. Allow them for the team. Create a group for the team and allow it on each integration. Groups can match the groups in your identity provider.

3. Publish them in a portal. A portal is where team members find the approved tools and connect their own accounts.

4. Each person signs in and connects. People open the portal, sign in, and authorize each app with their own account. Their agent can then reach only what they can reach in that app.

5. Add one URL to each assistant. Each person copies their Magic MCP URL into Claude, ChatGPT, Cursor, or Copilot. The same tools appear in each.

6. Check the first calls. Ask for something specific, such as "list my open Linear issues", then look at the call in Tracing. It should show the tool, the arguments, and the person's name.

What changes when someone switches assistant?

Nothing on the admin side. They add the same URL to the new assistant, and their access, permissions, and logs carry over.

What about apps that are not in the catalog?

Link a remote MCP server you already run, or deploy your own server code as a custom provider. Both sit behind the same group access and logging.

Frequently asked questions

Do I have to set up each app separately in each assistant?

Not with a gateway. You set the app up once, and every assistant that supports MCP reaches it through the same URL. Without a gateway, each person configures each server in each client.

Does each person need their own API key?

No. Each person signs in to the app with their own account through OAuth, and the gateway stores and refreshes the token. Nobody copies a key into a config file.

What if different people on the team use different assistants?

That is the case this setup is for. A designer in ChatGPT, an engineer in Cursor, and a manager in Claude all get the same approved tools under their own permissions.

Can the team use a remote MCP server we already run?

Yes. Metorial can link a remote MCP server or deploy your own server code, and it then sits behind the same access rules and logging as the catalog integrations.

How do I see what the assistants did?

Every tool call through the gateway is recorded with the tool, arguments, result, session, and the person it ran for. In Metorial, that is in Tracing and in each account's operations view.

Sources

  1. Model Context Protocol specification
  2. Metorial documentation: Set up a Magic MCP server
  3. Metorial documentation: Link a remote MCP server

Ready to build with Metorial?

Connect any AI agent to any tool or data source. Govern every action.