Organizations

Organizations are the top-level containers for your team and all resources in MCP Functions. Understanding how organizations work is essential for managing your team, billing, and resources effectively.

What are Organizations?

An organization represents your company, team, or project on the MCP Functions platform. Think of it as your account or workspace - it's the highest level of organization in the platform hierarchy. Everything you create - workspaces, MCP servers, and tools - exists within an organization.

An organization contains and manages:

• Team members - All the people who have access to your organization, each with specific roles that determine what they can do

• Multiple workspaces - Isolated environments for different projects, teams, or environments (like development and production)

• Billing and subscription information - Your subscription plan, payment method, and billing history are all managed at the organization level

• Usage statistics and analytics - You can see how many tools you've created, how many API calls you've made, and other usage metrics across your entire organization

• Organization-wide settings - Security policies, integration settings, and other configurations that apply to everything in the organization

When to Create Multiple Organizations

Most users will only need one organization. However, you might create multiple organizations if:

• You're building tools for completely separate companies or business units that need to be kept completely separate

• You need separate billing for different projects or clients

• You want completely isolated teams with no possibility of cross-access

• You're an agency building tools for multiple clients and want to keep their resources completely separate

For most use cases, using workspaces within a single organization is sufficient and easier to manage.

Creating Organizations

Creating an organization is one of the first things you'll do when you sign up for MCP Functions. Here's a detailed walkthrough of the process:

The Creation Process

• Navigate to the Organizations page - When you first log in, you'll be prompted to create an organization. If you already have organizations, you can create a new one from the dashboard by clicking "Create Organization" or navigating to the Organizations section.

• Click "Create Organization" - This opens a form where you'll enter your organization details.

• Enter organization details - You'll need to provide:

• **Name** - This is the display name for your organization. It can be your company name, team name, or anything that identifies this organization. Examples: "Acme Corporation", "Engineering Team", or "My Tools". This name can be changed later if needed, so don't worry too much about getting it perfect. - **Slug** - This is a URL-friendly identifier for your organization. It's used in URLs and API endpoints. For example, if your organization name is "Acme Corporation", the slug might be "acme-corp". The system will suggest a slug based on your name, but you can customize it. **Important:** Once set, the slug cannot be changed, so choose carefully. It should be:

• Lowercase letters, numbers, and hyphens only - Unique (no two organizations can have the same slug) - Descriptive and memorable - Something you'll be comfortable using in URLs

- **Plan** - You'll need to select a subscription plan. Plans typically include:

• **Free/Trial** - Limited features, good for testing and learning the platform. Perfect for getting started and exploring what MCP Functions can do. - **Developer** - Full features for individuals and small teams. Great for personal projects or small startups. - **Pro** - Enhanced features, higher limits, and priority support. Ideal for growing businesses. - **Enterprise** - Advanced features, custom configurations, dedicated support, and SLA guarantees. For large organizations with specific requirements. You can start with a free trial or basic plan and upgrade later as your needs grow. Most plans allow you to upgrade or downgrade at any time.

- **Save and start adding workspaces** - Once you've entered all the details and saved, your organization is created. You'll be taken to the organization dashboard where you can start creating workspaces and building tools. ### What Happens After Creation

After creating your organization, you'll be taken to the organization dashboard. This is your main workspace where you can:

• See an overview of all your resources (workspaces, MCP servers, tools)

• Access organization settings

• Manage team members

• View billing and subscription information

• See usage statistics and analytics

• Create your first workspace

Understanding Organization Members

Team collaboration is one of the powerful features of MCP Functions. You can invite team members to your organization so they can create, use, and manage tools together. The platform uses a role-based access control system to manage what each team member can do.

The Three Role Levels

Each team member is assigned a role that determines their permissions:

Owner

This is the highest level of access. Owners have full control over the organization and can:

• Manage all resources (workspaces, MCP servers, tools)

• Invite and remove team members, including other owners

• Change organization settings

• Manage billing and subscriptions

• Delete the organization

• Transfer ownership to another member

There's typically at least one owner per organization (usually the person who created it). For small teams, you might have just one owner. For larger organizations, you might have multiple owners to ensure there's always someone who can manage critical settings.

Admin

Admins have significant permissions but can't manage billing or delete the organization. They can:

• Create and manage workspaces, MCP servers, and tools

• Invite and remove team members (but not other owners)

• Change most organization settings

• View organization usage and statistics

• Manage workspace access and permissions

Admins are great for team leads or senior members who need to manage resources but shouldn't have full owner access. They can handle day-to-day management while owners handle billing and critical decisions.

Member

Members have the most limited access. They can:

• Create and use tools

• View workspaces, MCP servers, and tools they have access to

• Edit tools they've created (or tools they've been given permission to edit)

• Test and deploy tools

Members cannot invite other team members, change organization settings, manage billing, or delete resources they didn't create. This role is perfect for team members who just need to use and create tools without administrative responsibilities.

Inviting Team Members

To invite someone to your organization:

• Go to the organization settings and navigate to the "Team" or "Members" section

• Click "Invite Member"

• Enter their email address

• Select their role (Owner, Admin, or Member)

• Send the invitation

The invited person will receive an email with a link to join your organization. When they click it, they'll be prompted to create an account (if they don't have one) or log in, and then they'll be added to your organization.

Best Practices for Team Management

• Start with minimal permissions - Give new team members the Member role initially. You can always promote them to Admin or Owner later if needed.

• Use workspaces for access control - If you have sensitive projects, create separate workspaces and only give access to team members who need it.

• Regularly review team members - Periodically check who has access to your organization and remove people who no longer need it.

• Document roles and responsibilities - Make sure team members understand what their role allows them to do.

• Have multiple owners - For important organizations, consider having at least two owners to ensure there's always someone who can manage critical settings.

Organization Settings and Configuration

The organization settings allow you to configure how your organization works. These settings apply to everything in your organization and affect all team members.

Billing and Subscription Management

At the organization level, you can:

• View your current subscription plan

• Upgrade or downgrade your plan

• Manage payment methods and billing information

• View billing history and invoices

• Set up billing alerts and notifications

Billing is tied to the organization, not individual users. This means one person (typically an owner) manages billing for the entire organization, and all usage is billed together.

Usage Limits and Quotas

Depending on your subscription plan, you may have limits on:

• Number of workspaces you can create

• Number of MCP servers per workspace

• Number of tools per MCP server

• API calls per month

• Execution time limits

• Storage for secrets and configuration

You can view your current usage and limits in the organization settings. If you're approaching a limit, you'll receive notifications, and you can upgrade your plan if needed.

Security Policies

Organization-level security settings include:

• Password policies (if applicable)

• Multi-factor authentication requirements

• IP allowlisting (for Enterprise plans)

• Session timeout settings

• Audit logging preferences

These settings help ensure that your organization's resources are secure and that you can meet compliance requirements.

Integration Settings

You can configure integrations at the organization level, such as:

• Single Sign-On (SSO) configuration

• Webhook endpoints for notifications

• API access settings

• Third-party service integrations

Organization Analytics and Usage

The organization dashboard provides insights into how your organization is using MCP Functions:

• Tool creation statistics - See how many tools you've created over time

• API usage metrics - Track how many API calls you're making

• Team activity - See which team members are most active

• Workspace usage - Understand which workspaces are being used most

• Cost tracking - Monitor your spending and usage patterns

These analytics help you understand how your team is using the platform and can inform decisions about scaling, optimization, and resource allocation.

Best Practices for Organizations

• Choose your slug carefully - Remember, it can't be changed later. Pick something professional and memorable.

• Start with the right plan - You can always upgrade, but starting with a plan that matches your needs helps you avoid surprises.

• Set up billing alerts - Configure notifications so you know when you're approaching usage limits or billing thresholds.

• Regularly review team access - Remove team members who no longer need access and update roles as people's responsibilities change.

• Use workspaces for organization - Don't try to put everything in one workspace. Use multiple workspaces to organize by project, team, or environment.

• Document your structure - Keep notes on how you've organized your organization, workspaces, and resources so team members can understand the structure.