MCPifex Team Plan: Organization, Members, Instances

The MCPifex Team plan puts your MCP instances under one shared team organisation. It costs $49 a month or $490 a year and includes up to 30 instances and up to 5 members. Everyone connects through the same gateway endpoint that Free and Pro accounts use.

What's the difference between personal and team?

Every account starts in personal space. Free (3 instances) and Pro (10 instances) both stay personal, so one person owns the instances, their credentials and their API keys. Team is the only plan that moves you into a team organisation.

The price is flat. You pay $49 a month (or $490 a year) for the whole team, not per seat, so adding a teammate within the 5-member cap does not change your bill. For background on why teams centralize MCP access, see MCP for teams.

Instances are the only limit on any plan. Tool calls are unlimited. These are the current plans, and plans and limits has the full breakdown.

How do instances work on a team?

An instance looks the same on Team. Each one pairs a catalog server with its own credentials, enabled tools and API key. See instances and tools and API keys and authentication.

What changes is ownership. On Team, the 30-instance cap and every instance under it belong to the organisation, not to one person. An instance that needs a Google account, such as Google Search Console, still needs its own connection. See connected accounts.

How many members can a team have?

Up to 5. They share the same instances and the same billing. The cap is 5 whether you pay monthly or yearly. Free and Pro have no members, so choosing Team is what creates the organisation.

How do invites and admin controls work?

The Team plan lets you invite teammates into the organisation, up to the 5-member cap. Team also includes admin controls, so the people who manage the organisation can look after the shared workspace. Team organisations are built on Clerk organizations, which is where the 5-member limit is enforced.

Once teammates are in, they work in the same shared workspace as you. The instances, their enabled tools and the API keys belong to the organisation rather than to one person. That makes it easier to hand over work, because nobody has to leave a personal account behind when they move on.

How do you keep access tight on a team?

Give each instance the narrowest credential the server allows, and switch off tools an agent does not need. The gateway lists only enabled tools and refuses calls to all others, so the same rules protect every member's clients. Revoke any API key that is no longer in use. The security and data doc explains how this works, and the troubleshooting doc covers the errors a member's client might see.

Should you choose Team or Pro?

Pick Pro if you are the only person using MCPifex and 10 instances is enough. Pick Team when more than one person needs to manage the same servers, or when you need up to 30 instances under shared ownership. Tool calls are unlimited on both. Compare them on the pricing page.

What happens if you downgrade a team?

The same rule applies as on any plan change. Instances beyond the new cap are disabled, newest first, and nothing is deleted. Upgrading again re-enables them oldest first.

How do you get a team organisation?

Pick Team on the pricing page. Every account begins free and personal after registration, so moving to Team is a plan change on your existing account, not a separate sign-up. The marketplace shows what your team can connect.

← Back to docs