Reason and perform tasks using MCP. Use state of the art LLMs in your development workflows.
Setup
Choose your client, copy the config, then fill in any required environment variables.
claude mcp add task --env ENV_FILE='<ENV_FILE>' -- npx -y @just-every/mcp-task~/.codex/config.toml
[mcp_servers.task]
command = "npx"
args = ["-y", "@just-every/mcp-task"]
env = { ENV_FILE = "<ENV_FILE>" }
# codex mcp add task --env ENV_FILE='<ENV_FILE>' -- npx -y @just-every/mcp-task~/.cursor/mcp.json
{
"mcpServers": {
"task": {
"command": "npx",
"args": [
"-y",
"@just-every/mcp-task"
],
"env": {
"ENV_FILE": "<ENV_FILE>"
}
}
}
}.vscode/mcp.json
{
"servers": {
"task": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@just-every/mcp-task"
],
"env": {
"ENV_FILE": "<ENV_FILE>"
}
}
}
}~/.gemini/settings.json
{
"mcpServers": {
"task": {
"command": "npx",
"args": [
"-y",
"@just-every/mcp-task"
],
"env": {
"ENV_FILE": "<ENV_FILE>"
}
}
}
}claude_desktop_config.json
{
"mcpServers": {
"task": {
"command": "npx",
"args": [
"-y",
"@just-every/mcp-task"
],
"env": {
"ENV_FILE": "<ENV_FILE>"
}
}
}
}.trae/mcp.json
{
"mcpServers": {
"task": {
"command": "npx",
"args": [
"-y",
"@just-every/mcp-task"
],
"env": {
"ENV_FILE": "<ENV_FILE>"
}
}
}
}Environment variables
ENV_FILE
Replace the placeholders with your own credentials and keep them out of version control.