edgee-createApiToken
Create a new API token.
LABSCO SUMMARY
Proxy settings versioned as revisions rather than overwritten is the design choice that makes this safe to automate against.
Proxy configuration is exactly the kind of object where a bad write takes traffic down and the previous state is what you urgently need. Keeping revisions means a change is recoverable by pointing back rather than by remembering what was there. Per-component counters alongside the incoming events feed is the other useful pairing — one tells you what arrived, the other what each component did with it, and edge debugging usually needs both. This is a large administrative surface with real deletion in it, so what the token is allowed to do matters more than usual.
What it is
A full administrative client for the Edgee edge platform, structured the way the platform is: organisations containing projects, projects carrying domains, proxy settings and components, and telemetry hanging off both.
What you get
- Organisations with complete lifecycle plus user management — list, update and remove users within one.
- Projects with the same completeness, and getProjectCounters for the statistics on one.
- Domains as their own objects under a project: list, create, update, delete and fetch individually.
- Proxy settings kept as revisions rather than a single mutable blob — listProjectProxySettings returns the revision history, and updates target a revision.
- Components with their own lifecycle and per-component counters, so an edge component's traffic is attributable.
- getIncomingDataCollectionEvents returns what is actually arriving at the project, which is the question behind most edge debugging.
Requirements
EDGEE_TOKEN. The surface includes deletion of organisations, projects, domains and components, so the token's scope is what bounds an agent here.
Setup effort
One command plus a key — npx @edgee/mcp-server-edgee, then supply credentials
USE CASES
01
Standing up a project
Create it under the organisation, attach its domain, and add the components it needs.
02
Changing proxy behaviour without losing the way back
Read the revision history first, then create or update settings against a revision, so the previous state stays reachable.
03
Working out what is actually arriving
Read the incoming data collection events alongside the per-component counters, so what came in and what handled it are both visible.
04
Managing who has access
List an organisation's users, adjust one, and remove those who should not be there.
05
Auditing what exists
List the organisations, their projects, and each project's domains and components before changing anything.
55 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
edgee-createComponent
Create a new component.
edgee-createComponentVersion
Create a new component version.
edgee-createComponentVersionBySlug
Create a new component version by slug.
edgee-createInvitation
Create a new invitation.
edgee-createOrganization
Create a new Organization.
edgee-createProject
Create a new Project.
edgee-createProjectComponent
Create a new component for a project.
edgee-createProjectDomain
Create a new domain for a project.
edgee-createProjectProxySettings
Create new proxy settings for a project.
edgee-deleteApiToken
Delete an API token.
edgee-deleteComponentBySlug
Delete a component by slug.
edgee-deleteComponentByUuid
Delete a component by UUID.
edgee-deleteInvitation
Delete an invitation.
edgee-deleteOrganization
Delete an existing Organization.
edgee-deleteOrganizationUser
Delete a user from an organization.
edgee-deleteProject
Delete an existing Project.
edgee-deleteProjectComponent
Delete a component from a project.
edgee-deleteProjectDomain
Delete a domain from a project.
edgee-getApiToken
Get an API token by ID.
edgee-getComponentBySlug
Get a component by slug.
edgee-getComponentByUuid
Get a component by UUID.
edgee-getIncomingDataCollectionEvents
Get incoming data collection events for a project.
edgee-getInvitation
Get an invitation by ID.
edgee-getMe
Get the current user.
edgee-getMyOrganization
Retrieve your personal organization.
edgee-getOrganization
Retrieve an Organization by ID.
edgee-getOutgoingDataCollectionEvents
Get outgoing data collection events for a project.
edgee-getProject
Retrieve a Project by ID.
edgee-getProjectComponent
Get a component for a project.
edgee-getProjectComponentCounters
Get counters for a project component.
edgee-getProjectCounters
Get statistics for a project.
edgee-getProjectDomain
Get a domain for a project.
edgee-getUploadPresignedUrl
Get a presigned URL for uploading files.
edgee-getUser
Get a user by ID.
edgee-listApiTokens
List all API tokens.
edgee-listInvitations
List all invitations.
edgee-listOrganizationComponents
List all components for an organization.
edgee-listOrganizations
Returns a list of your Organizations. The Organizations are returned sorted by creation date, with the most recent Organizations appearing first.
edgee-listOrganizationUsers
List all users of an organization.
edgee-listProjectComponents
List all components for a project.
edgee-listProjectDomains
List all domains for a project.
edgee-listProjectProxySettings
List all proxy settings revisions for a project.
edgee-listProjects
Returns a list of your Projects. The Projects are returned sorted by creation date, with the most recent Projects appearing first.
edgee-listPublicComponents
List all public components.
edgee-updateComponentBySlug
Update a component by slug.
edgee-updateComponentByUuid
Update a component by UUID.
edgee-updateComponentVersionBySlug
Update a component version by slug.
edgee-updateOrganization
Update an existing Organization.
edgee-updateOrganizationUser
Update a user in an organization.
edgee-updateProject
Update an existing Project.
edgee-updateProjectComponent
Update a component for a project.
edgee-updateProjectDomain
Update a domain for a project.
edgee-updateProjectProxySettings
Update proxy settings for a project by revision.
edgee-updateUser
Update a user by ID.
BEFORE YOU INSTALL
What to know first
Tools you get
55 tools when we connected. The documentation lists thirty-one; the proxy-settings tools, data-collection event feeds, several update and delete tools and edgee-updateUser are undocumented. Many tools create, update or delete organizations, projects, domains, users and API tokens.
Requires
- npx on PATH
- EDGEE_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Moderate Standing cost
Rated by the size of the 55 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @edgee/mcp-server-edgeeMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"edgee": {
"command": "npx",
"args": [
"-y",
"@edgee/mcp-server-edgee"
],
"env": {
"EDGEE_TOKEN": "<YOUR_TOKEN>"
}
}
}
}
