Overview

Edgee MCP Server implements the Model Context Protocol (MCP) adapter for Edgee Cloud, exposing administration operations for organizations, projects, components, and users as tools a model-driven agent can call. It is built in TypeScript and provides a type-safe, predictable interface for programmatic administration tasks such as creating projects, managing component versions, issuing API tokens, and inviting users.

This server is useful when you want to integrate Edgee administration into automated workflows, chat assistants, or other tooling that uses MCP to extend model capabilities. Install it locally or run via npx to let agents perform CRUD operations and retrieve metadata (project counters, domains, component lists, presigned upload URLs) without building a custom API wrapper.

Features

Organization CRUD (create, read, update, delete) and membership listing
Project CRUD, domain management, project counters/statistics, and component listing
Component management: create components, publish versions, list public/organization components
User administration: get current user, manage invitations, and API tokens
Presigned upload URL generation for component artifacts
Comprehensive error responses and TypeScript-based type safety
Usable as an MCP server with tools exposed for model-driven clients

Installation / Configuration

Install and run via NPX (recommended), global install, or as a local dependency.

Using NPX (no install required):

npx @edgee/mcp-server-edgee

Global install:

npm install -g @edgee/mcp-server-edgee
mcp-server-edgee

Local install (project dependency):

npm install @edgee/mcp-server-edgee
npx @edgee/mcp-server-edgee

Configure access via an Edgee Personal Access Token:

Create a token in Edgee: Account Settings → API Tokens
Copy the generated token and set it in your environment:

export EDGEE_TOKEN="sk_XXXXXXXXXXXX"
# Windows (PowerShell)
$env:EDGEE_TOKEN = "sk_XXXXXXXXXXXX"

Example configuration for Claude Desktop (add to claude_desktop_config.json):

{
  "mcpServers": {
    "edgee": {
      "command": "npx",
      "args": ["-y", "@edgee/mcp-server-edgee"],
      "env": {
        "EDGEE_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Available Tools

The MCP server exposes many tools (grouped below). Each tool name corresponds to a callable tool in the MCP toolset.

Organization Tools

edgee-listOrganizations — list organizations (with optional filters)
edgee-getMyOrganization — fetch your personal organization
edgee-getOrganization — retrieve organization by ID
edgee-createOrganization — create a new organization
edgee-updateOrganization — update organization properties
edgee-deleteOrganization — remove an organization
edgee-listOrganizationUsers — list members of an organization

Project Tools

edgee-listProjects — list projects with optional filters
edgee-getProject — get project by ID
edgee-createProject — create a project (assign to organization)
edgee-updateProject — update project details
edgee-deleteProject — delete a project
edgee-getProjectCounters — fetch project statistics/counters
edgee-listProjectDomains — list domains for a project
edgee-createProjectDomain — add a domain to a project
edgee-listProjectComponents — list components associated with a project

Component Tools

edgee-listPublicComponents — list public components
edgee-listOrganizationComponents — list components belonging to an organization
edgee-getComponentByUuid — fetch component by UUID
edgee-getComponentBySlug — fetch component by slug
edgee-createComponent — create a component (metadata)
edgee-createComponentVersion — publish a new component version (artifact upload via presigned URL)

User Tools

edgee-getMe — get the current authenticated user
edgee-getUser — fetch user by ID
edgee-listInvitations — list pending invitations
edgee-createInvitation — invite a user to an organization
edgee-deleteInvitation — revoke an invitation
edgee-listApiTokens — list API tokens
edgee-createApiToken — create an API token
edgee-deleteApiToken — delete an API token
edgee-getUploadPresignedUrl — get presigned URL for uploads

Use Cases (concrete examples)

List all organizations accessible to the token:

Use tool: edgee-listOrganizations
Typical agent flow: call tool → receives JSON list of organizations → parse and display

Create a new project for an organization:

Use tool: edgee-createProject
Parameters: organization_id, slug, title, description
Example payload (MCP tool call):

{
  "organization_id": "org_123456",
  "slug": "my-new-project",
  "title": "My New Project",
  "description": "Project for testing component publishing"
}

Publish a component version:

Steps:
1. Call edgee-createComponentVersion with metadata to obtain a presigned URL
2. Upload artifact (e.g., tarball) to the presigned URL using curl or an SDK
3. Confirm completion via the tool response
Example: get presigned URL:

{ "component_uuid": "cmp_abc123", "version": "1.0.0", "file_name": "component.tgz" }

Invite a teammate:

Use edgee-createInvitation with organization_id, email, and role (“member” or “admin”)

Development

Clone and build from source:

git clone https://github.com/edgee-cloud/mcp-server-edgee.git
cd mcp-server-edgee
npm install
npm run build

License: Apache-2.0

Notes & Troubleshooting

Ensure EDGEE_TOKEN has sufficient scope/validity for operations you perform.
The server returns structured error messages for common failure modes (authentication, validation, not found). Check tool responses for error details before retrying.
Because this server exposes administrative operations, run it with secure token handling and restrict access in shared environments.

Edgee MCP Server — Organizations, Projects, Components, Users