Aep runs on your own machine — the client starts it, so there is no endpoint to ping. 106 installs a week from npm. Last commit 30 Aug 2026.
Full-CRUD server for AEP, Journey Optimizer and CJA. 61 tools from one OAuth credential.
We read the source, 5 d ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
# setup-node's `registry-url` writes an .npmrc containing an auth-token
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check Aep every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add aep -e 'AEP_CLIENT_ID=<AEP_CLIENT_ID>' -e 'AEP_CLIENT_SECRET=<AEP_CLIENT_SECRET>' -e 'AEP_ORG_ID=<AEP_ORG_ID>' -- npx -y @focusgts/aep-mcp-server
{
"mcpServers": {
"aep": {
"command": "npx",
"args": [
"-y",
"@focusgts/aep-mcp-server"
],
"env": {
"AEP_CLIENT_ID": "<AEP_CLIENT_ID>",
"AEP_CLIENT_SECRET": "<AEP_CLIENT_SECRET>",
"AEP_ORG_ID": "<AEP_ORG_ID>"
}
}
}
}
[mcp_servers.aep]
command = "npx"
args = ["-y", "@focusgts/aep-mcp-server"]
env = { AEP_CLIENT_ID = "<AEP_CLIENT_ID>", AEP_CLIENT_SECRET = "<AEP_CLIENT_SECRET>", AEP_ORG_ID = "<AEP_ORG_ID>" }
{
"mcpServers": {
"aep": {
"command": "npx",
"args": [
"-y",
"@focusgts/aep-mcp-server"
],
"env": {
"AEP_CLIENT_ID": "<AEP_CLIENT_ID>",
"AEP_CLIENT_SECRET": "<AEP_CLIENT_SECRET>",
"AEP_ORG_ID": "<AEP_ORG_ID>"
}
}
}
}
{
"servers": {
"aep": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@focusgts/aep-mcp-server"
],
"env": {
"AEP_CLIENT_ID": "<AEP_CLIENT_ID>",
"AEP_CLIENT_SECRET": "<AEP_CLIENT_SECRET>",
"AEP_ORG_ID": "<AEP_ORG_ID>"
}
}
}
}
Put your own values in place of
<AEP_CLIENT_ID> (Adobe I/O client ID from an OAuth Server-to-Server credential in the Adobe Developer Console), <AEP_CLIENT_SECRET> (Adobe I/O client secret paired with AEP_CLIENT_ID), <AEP_ORG_ID> (Adobe IMS organization ID, in the form xxxxxxxxx@AdobeOrg).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
AEP_SANDBOX_NAME (AEP sandbox to scope every call to. Defaults to 'prod'. Use a development sandbox to enable write operations), AEP_MODE (Write posture: 'read-only' (no mutation anywhere), 'safe' (default — writes only in sandboxes Adobe classifies as development), or 'production' (writes anywhere). Reads are never restricted), LOG_LEVEL (Pino log level. Logs go to stderr; stdout is reserved for the MCP JSON-RPC stream).
MCP server for 1Password service accounts — tools and resources for vaults and credentials
Secure Open Finance Brasil MCP server with typed tools and a credential-free mock mode
Encrypted credential vault: LLM, service & OAuth keys. 21-tool MCP server for your AI agent.
Remote MCP for 1,500+ APIs. Vault-managed credentials; OAuth or API key. Search, load, and execute.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
SQLite MCP server with 73 tools for JSONB, full-text search, geospatial, and analytics.
52 MCP tools for AI social media: create, distribute, analyze, and optimize content.
Google OAuth Credential Service
Answers built from our own checks of this server.