MCP Server do Ekyte para Codex: cria e atualiza tarefas/projetos, lista workspaces/usuarios/fases e gerencia apontamentos de horas via API interna do Ekyte.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"ekyte-mcp-server": {
"args": [
"-y",
"npm"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Servidor MCP (Model Context Protocol) para conectar o Codex ao Ekyte e operar tarefas, projetos, fases, usuarios, workspaces e apontamentos de horas por tools.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools
Read, write, and manage files on the local filesystem
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Manage Supabase projects — databases, auth, storage, and edge functions
MCP Security Weekly
Get CVE alerts and security updates for Ekyte_mcp_server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Servidor MCP (Model Context Protocol) para conectar o Codex ao Ekyte e operar tarefas, projetos, fases, usuarios, workspaces e apontamentos de horas por tools.
Descricão sugerida para o GitHub:
MCP Server do Ekyte para Codex: cria e atualiza tarefas/projetos, lista workspaces/usuarios/fases e gerencia apontamentos de horas via API interna do Ekyte.
stdio para uso direto no Codex CLI./mcp para deploy com Docker./health.codex/skills/ekyte.PRD-INSTALAcão-MCP-EKYTE-CODEX.md.https://app.ekyte.com.EKYTE_BEARER_TOKEN: JWT Bearer copiado do header Authorization.EKYTE_COMPANY_ID: ID numerico da empresa no caminho /api/companies/XXXX/....Clone o repositorio:
git clone https://github.com/matheusbernardopro-source/ekyte_mcp_server.git
cd ekyte_mcp_server
Instale as dependencias e gere o build:
npm install
npm run build
Crie o .env a partir do exemplo:
cp .env.example .env
Preencha as variaveis obrigatorias:
EKYTE_BEARER_TOKEN=seu_jwt
EKYTE_COMPANY_ID=1234
TRANSPORT=stdio
PORT=3000
O caminho recomendado e pedir para o Codex executar o PRD:
Executa este PRD de instalacão: @PRD-INSTALAcão-MCP-EKYTE-CODEX.md
O PRD cobre instalacão local, instalacão remota, registro da MCP e copia da skill.
codex mcp add ekyte --env EKYTE_BEARER_TOKEN=SEU_JWT --env EKYTE_COMPANY_ID=SEU_COMPANY_ID --env TRANSPORT=stdio -- node /CAMINHO/ABSOLUTO/ekyte_mcp_server/dist/index.js
codex mcp add ekyte --url https://SEU-SERVIDOR.com/mcp
Crie ou atualize ./.codex/config.toml:
[mcp_servers.ekyte]
command = "node"
args = ["/CAMINHO/ABSOLUTO/ekyte_mcp_server/dist/index.js"]
[mcp_servers.ekyte.env]
EKYTE_BEARER_TOKEN = "SEU_JWT"
EKYTE_COMPANY_ID = "SEU_COMPANY_ID"
TRANSPORT = "stdio"
Para servidor remoto:
[mcp_servers.ekyte]
url = "https://SEU-SERVIDOR.com/mcp"
Valide:
codex mcp list
codex mcp get ekyte
A skill ensina o Codex a operar a MCP com fluxo seguro: listar IDs antes de criar, confirmar operacoes sensiveis e usar os formatos corretos de data, hora e UUID.
Arquivos:
codex/skills/ekyte/SKILL.mdcodex/skills/ekyte/reference.mdInstalacão global no Windows:
New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\.codex\skills" | Out-Null
Copy-Item -Recurse codex\skills\ekyte "$env:USERPROFILE\.codex\skills\"
Instalacão global no Linux/macOS:
mkdir -p ~/.codex/skills
cp -r codex/skills/ekyte ~/.codex/skills/
Build da imagem:
docker build -t ekyte-mcp-server .
Execucão:
docker run -d --name ekyte-mcp-server \
-p 3000:3000 \
-e EKYTE_BEARER_TOKEN=SEU_JWT \
-e EKYTE_COMPANY_ID=SEU_COMPANY_ID \
-e TRANSPORT=http \
-e PORT=3000 \
ekyte-mcp-server
Valide:
curl http://localhost:3000/health
Endpoint MCP remoto:
https://SEU-SERVIDOR.com/mcp
Leitura:
ekyte_list_workspacesekyte_list_usersekyte_list_task_typesekyte_list_phasesekyte_list_tasksekyte_get_taskekyte_list_task_flow_phasesekyte_list_projectsekyte_list_project_templatesekyte_list_project_tasksekyte_list_time_entriesEscrita:
ekyte_create_taskekyte_update_taskekyte_update_phase