Organizations

Organizations let teams publish, manage, and govern MCP servers under a shared namespace. Every MCP published by an organization appears in the catalog under the organization’s name (e.g. acme-corp/my-server) instead of a personal account.

Creating an Organization

1. Log in to mcp-hub.info.
2. Click your avatar in the top-right corner and select Organizations.
3. Click Create Organization.
4. Fill in the organization details:

5. Click Create to finish.

You are automatically assigned the Owner role in the new organization.

Members and Roles

Organizations support four roles with different permission levels:

Inviting Members

1. Go to Organizations > Your Org > Members.
2. Click Invite Member.
3. Enter the user’s email or username and select a role.
4. The user receives an invitation and must accept it to join.

Changing Roles

Owners and Admins can change any member’s role from the Members page. An organization must always have at least one Owner.

Publishing MCPs in an Organization

The flow for publishing an MCP server within an organization is exactly the same as publishing one under your personal account. The only difference is that the MCP is owned by the organization instead of your personal profile.

Who Can Publish

Any member with the Owner, Admin, or Member role can create and publish MCP servers in the organization. Viewers cannot publish.

Step-by-Step

1. Navigate to Organizations > Your Org > MCPs.
2. Click Create MCP.
3. Choose your source:
   • Connect a provider – Link your GitHub, GitLab, or Bitbucket account, then browse and select a repository from the list. This is the recommended method for private repositories.
   • Enter URL manually – Paste the full Git repository URL (e.g. https://github.com/acme-corp/my-server).
4. Configure metadata – Fill in the name, description, category, and optional tags. These fields work identically to the personal MCP creation form.
5. Click Create to submit for analysis.

The platform immediately begins the automated analysis pipeline: clone, detect, scan, score, certify, and publish. This is the same pipeline that runs for personal MCPs. See Creating an MCP for full details on each step.

Naming

Organization MCPs use the organization slug as their namespace. For example, if your organization is acme-corp and you name the MCP my-server, the full reference is:

acme-corp/my-server@latest

Users install it with:

smcp run acme-corp/my-server@latest

Managing Organization MCPs

Once published, organization MCPs appear in Organizations > Your Org > MCPs. Management works the same as personal MCPs:

• Rescan – Trigger a fresh analysis after pushing code changes.
• Edit metadata – Update the name, description, category, or tags.
• Visibility – Switch between public and private.
• View findings – See the full security report, score breakdown, and vulnerability details.
• Version history – Browse all analyzed versions and their scores.

All actions are recorded in the organization’s Audit Log, including who created or rescanned each MCP.

For detailed information on managing MCPs, see Managing Your MCPs.

Organization Plans

Organizations have their own plan, separate from individual user plans. The plan determines quotas and available features.

Manage your organization’s plan from Organizations > Your Org > Settings > Billing.

Audit Log

Every action within the organization is tracked in the audit log. Owners and Admins can view it from Organizations > Your Org > Audit Log.

Tracked events include:

• MCP created, rescanned, or deleted
• Member invited, role changed, or removed
• Settings or plan changes
• Visibility changes on MCPs

Next Steps

• Creating an MCP – Detailed guide on the MCP publishing flow (identical for personal and organization MCPs).
• Managing Your MCPs – Monitor scores, trigger rescans, and respond to alerts.
• GRC Integration – Connect organization security data to your GRC platform (Enterprise plan).