Organization Accounts

Organization accounts let teams share catalogs, manage credentials together, and control access across members. When your work involves multiple people, an organization keeps everything organized.

What Organizations Are

An organization is a shared account that:

• Owns resources — Catalogs, APIs, and credentials belong to the org
• Has members — Team members with different roles
• Provides a namespace — https://mcp.toolcog.com/{org-handle}/...

Personal accounts are for individual use. Organizations are for teams.

When to Create an Organization

Create an organization when:

• Multiple people need to manage catalogs
• Shared credentials are needed across team members
• Centralized control is important for security
• Team projects require clear ownership

Stick with a personal account when:

• You’re working alone
• Resources don’t need to be shared
• You’re just experimenting

Creating an Organization

Step 1: Navigate to New Organization

1. Sign in to toolcog.com
2. Click Create in the header
3. Select Organization

Step 2: Choose a Handle

Enter a handle for your organization:

• Lowercase letters, numbers, and hyphens
• Will appear in MCP URLs: https://mcp.toolcog.com/{handle}/...
• Can’t be changed after creation

Examples: acme, engineering-team, product-co

Step 3: Set Organization Name

Enter a display name:

• Can include spaces and special characters
• Shown in the UI and notifications
• Can be changed later

Step 4: Create

Click Create Organization. You’re now the owner.

Organization Ownership

The organization owner can:

• Manage all settings
• Invite and remove members
• Transfer ownership
• Delete the organization

An organization always has exactly one owner. Ownership can be transferred to another member.

Organization Resources

Resources created under an organization belong to the organization, not individuals:

Catalogs

Catalogs owned by the org:

• Available at https://mcp.toolcog.com/{org}/{catalog}
• Managed by org members with appropriate roles
• Persist if individual members leave

APIs

Uploaded APIs belong to the org:

• Can be included in org catalogs
• Managed by org members
• Credentials are separate from API ownership

Credentials

Organization credentials are shared:

• Stored in the org’s vault
• Accessible by authorized members
• Not tied to individual accounts

Organization Settings

Access settings from your organization page:

General

• Change display name
• Update description
• Add organization logo

Members

• View all members
• Invite new members
• Change roles
• Remove members

Billing

• View current plan
• Upgrade or change plans
• Update payment method
• View invoices

Security

• View audit logs
• Configure SSO (enterprise)
• Manage API tokens

Personal vs. Organization Accounts

Best Practices

Use Org Accounts for Teams

Even for small teams, organization accounts provide:

• Clear resource ownership
• Easy member onboarding/offboarding
• Shared credential management

Keep Personal for Personal

Use your personal account for:

• Learning and experimentation
• Personal projects
• Resources you don’t need to share

Plan Your Handle

Organization handles can’t be changed. Choose one that:

• Represents your team/company
• Is memorable and professional
• Works in URLs

Next Steps

• Team Management — Invite and manage members
• Shared Resources — Share catalogs and credentials