Skip to main content

Overview

Projects organize users and configurations. Each project has an assigned MCP configuration that defines available servers, and users who can access those servers through project-specific API keys.

Project Management

List Projects

List all projects in the system.

Create Project

Create a new project.
string
required
Unique name for the project

Get Project

Retrieve detailed information about a project.
string
Project name
string
Project UUID

Remove Project

Delete a project (must not have active API keys).
Delete all API keys for the project before removing it.

Configuration Assignment

Assign Configuration

Assign an MCP configuration to a project.
string
required
Project name or ID
string
required
Configuration name or ID to assign

Unassign Configuration

Remove the configuration assignment from a project.

Get Project Configuration

Retrieve the configuration assigned to a project.

User Management

List Project Users

List all users in a project.

Add User to Project

Add an existing user to a project.
string
required
Project name or ID
string
User email address
string
User UUID
The user must already exist in the system. Create the user first with secure-mcp-gateway user create.

Remove User from Project

Remove a user from a project.
This does not delete the user’s API keys for this project. Delete them separately if needed.

Remove All Users

Remove all users from a project.

Import/Export

Export Project

Export project with all related data to a JSON file.
string
required
Path to output JSON file
Export file structure:

Search Projects

Search for projects by name or user email.
string
required
Search term to match against project names and user emails

Best Practices

  • Separate environments: Create distinct projects for dev, staging, and production
  • Team-based projects: Organize by team or department
  • Purpose-based naming: Use clear, descriptive project names
  • Documentation: Maintain project purpose and ownership records
  • Environment-specific configs: Assign appropriate configs to each project
  • Testing before production: Test config changes in dev projects first
  • Regular reviews: Periodically review project configurations
  • Change tracking: Document configuration changes
  • Principle of least privilege: Only add users who need access
  • Regular audits: Review project membership periodically
  • Offboarding: Remove users when they leave teams
  • Role separation: Use different projects for different access levels
  • One key per user per project: Generate individual keys
  • Regular rotation: Rotate keys periodically
  • Monitor usage: Track API key usage patterns
  • Quick revocation: Be prepared to revoke compromised keys

Common Workflows

Create New Project with Users

Migrate Project to New Configuration

Team Offboarding

Bulk User Addition

Troubleshooting

Error: “Project has X active API keys”Solution:
Error: “User is already in project”Solution: This is expected behavior. The user doesn’t need to be added again.
Error: “Config not found”Solution: